General ASP.NET

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Don't stop IIS-Express when stopping debugger with enabled Edit&Continue

    Currently if Edit & Continue is enabled (in VS 2013 Update 3 on x64) stopping the debugger always stops IIS-Express. See MS-Blog http://blogs.msdn.com/b/webdev/archive/2013/07/11/enable-edit-and-continue-debugging-option-is-now-on-by-default-for-new-web-applications-in-vs2013-preview.aspx

    This is very un-handy. Please don't stop IIS-Express all the time.

    69 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  IISExpress  ·  Flag idea as inappropriate…  ·  Admin →
    • Show website details in "Title" column for iisexpress.exe process when attaching the debugger in Visual Studio

      If you want to attach the debugger from Visual Studio to a web application running under IIS express, there is no way to distinguish between different iisexpress.exe processes. Currently if I have 10 iisexpress processes in the list I have to look at the PID number in the systemtray GUI for IIS Express and then find in "Available processes" list. The ASP.NET development server display "ASP.NET Development Server - Port xyz" in the title column of the available processes list. For IIS Express the website directory or url could be displayed in that same column.

      46 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        2 comments  ·  IISExpress  ·  Flag idea as inappropriate…  ·  Admin →
      • Show corrolation between request started and ended in IIS Express logs

        When working with a REST-api the log from IISExpress would be a lot more useful if you could add a corrolation id between the request start and end.

        The "request started" logs contain the request method, but the "request ended" does not, which makes it hard to tell which methods fail and succeeds.

        E.g. if you have PUT and DELETE methods for the same url the log would look exactly the same;

        IISExpress: Request ended: http://localhost:9002/api/customers/1 with HTTP status 200.0
        IISExpress: Request ended: http://localhost:9002/api/customers/1 with HTTP status 401.0

        Was it the PUT or the DELETE that failed with 401?

        Also;…

        18 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  IISExpress  ·  Flag idea as inappropriate…  ·  Admin →
        • Don't see your idea?

        Feedback and Knowledge Base