In my Visual Studio 2013 RC project, I&#39;m getting this err msg:

&gt; &quot;*The type &#39;System.Net.Http.Formatting.MediaTypeFormatter&#39; is defined
&gt; in an assembly that is not referenced. You must add a reference to
&gt; assembly &#39;System.Net.Http.Formatting, Version=4.0.0.0,
&gt; Culture=neutral, PublicKeyToken=31bf3856ad364e35&#39;*&quot;

...on the `&quot;var response = &quot;` line of code in a Controller:

    public HttpResponseMessage PostDelivery(Delivery delivery)
    {
        delivery = repository.Add(delivery);
        var response = Request.CreateResponse&lt;Delivery&gt;(HttpStatusCode.Created, delivery);

        string uri = Url.Link(&quot;DefaultApi&quot;, new { id = delivery.Id });
        response.Headers.Location = new Uri(uri);
        return response;
    }

Searching my hard drive for the required assembly (&quot;System.Net.Http.Formatting&quot;), it shows me several locations where it exists, but they are all within existing projects, as is seen here:

![enter image description here][1]

Surely there is another location from which System.Net.Http.Formatting.dll can be referenced! But where?

UPDATE
------

Trying to follow the clue here: http://www.nuget.org/packages/System.Net.Http.Formatting

IOW, by selecting Tools &gt; Library Package Manager &gt; Package Manager Console, and entering: 

    Install-Package System.Net.Http.Formatting -Version 4.0.20710

...I see the red bulls of Pamplona (not the beverage) descending wild-eyed upon me:

![enter image description here][2]

UPDATE 2
--------

I added the System.Net.Http.Formatting.dll from here:

    C:\Users\clay\My Documents\Visual Studio 2013\Projects\MvcApplication1\MvcApplication1\bin

...and it now compiles and runs and works as expected, but that is obviously &quot;not the preferred method&quot;

  [1]: http://i.stack.imgur.com/UJlOi.png
  [2]: http://i.stack.imgur.com/P45oN.png


From where do I reference a missing assembly (System.Net.Http.Formatting)?

When I debugging in VS2013 update3, msvsmon.exe crashed when hit at a breakpoint.

It shows &quot;The debugger&#39;s worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted&quot;.

I&#39;m not using remote debug.

Is it possible to shut down the msvsmon.exe to avoid calling it when debugging ?

msvsmon.exe crashed when debugging

I&#39;m using the new Visual Studio 2013 with IISExpress for the first time (previously used ASP.net Development server on VS2010). I&#39;m running into issues trying to debug my project.

This is what I see in Chrome:


Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don&#39;t have.
Error code: ERR_SSL_PROTOCOL_ERROR

I updated my Properies -&gt; web file so that the Project Url uses a https URL now. However, after doing that, I now get a new error when launching:

The connection to localhost was interrupted.
Error code: ERR_CONNECTION_RESET

Thanks

SSL Connection / Connection Reset with IISExpress

I cannot get rid of this in my VS 2008 web project when debugging.  I&#39;ve checked that it&#39;s in debug mode on the non-web project in question and it&#39;s in Active(Debug).  Deleted all items in my .NET 2.0 temp folder in Windows.  Not sure what else to do here.

The Following Module was built either with optimizations enabled or without debug information

I want to debug a program in Visual Studio 2008. The problem is that it exits if it doesn&#39;t get arguments. This is from the main method:

    if (args == null || args.Length != 2 || args[0].ToUpper().Trim() != &quot;RM&quot;) 
    {
        Console.WriteLine(&quot;RM must be executed by the RSM.&quot;);
        Console.WriteLine(&quot;Press any key to exit program...&quot;);
        Console.Read();
        Environment.Exit(-1);
    }

I don&#39;t want to comment it out and and then back in when compiling. How can I start the program with arguments when debugging? It is set as the StartUp Project.

How do I start a program with arguments when debugging?

I&#39;m getting suddenly a strange error while debugging. Up to now the variable in the watch windows has been shown correctly. Now I am getting always the error message in the watch windows:

&gt; The function evaluation requires all threads to run

I am not able to check any variable anymore. I am not explicit working with threads. What can I do to get it working again?

I disabled already as mentioned in some forums the function: &quot;Enable property Evaluation and other implicit function Calls&quot; in the option window of the debugger. But without success, then I am getting the error: 

&gt; Error Implicit Function evaluation disabled by the user

Visual Studio during Debugging: The function evaluation requires all threads to run

Few days ago I moved my solution to MSVS 2013. It works fine except one thing: when I trying to debug code of my WCF service it works, but when I want to watch state of any variable it says:  &quot;Internal error in the expression evaluator&quot;. Add watch function works normal on client side, but in service code it broken. I&#39;m trying to debug my own WCF service running on the localhost. Could you help me, how to repair this?

![enter image description here][1]

Here MSVS info:
Microsoft Visual Studio Professional 2013
Version 12.0.30110.00 Update 1
Microsoft .NET Framework
Version 4.5.51641
OS: Windows 8.1


  [1]: http://i.stack.imgur.com/WBdQg.png

Get &quot;Internal error in the expression evaluator&quot; on &quot;Add watch&quot; function when trying to debug WCF service code (MSVS 2013)

I am running Visual Studio 2010 (as Admin), IIS 7 on Windows 7 x64.
I am able to run the ASP.NET web site in IIS 7 without debugging just fine, but when I press F5 to debug it, I get:

&gt; Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging.

Unfortunately the help link is not helping me much and leads down a heck of a large tree of things.

I checked the following:

* Security requirements — I don&#39;t recall having to do anything special before. The worker process in IIS7 is w3wp.exe. It says that if it&#39;s running as ASPNET or NETWORK SERVICE I must have Administrator privileges to debug it. How do I find out if I need to change something here?

* Web site Property Pages &gt; Start Options &gt; Debuggers &gt; ASP.NET is checked.
  Use custom server is set to the URL of the site (which works fine without debugging).

* Debugging is enabled in `web.config`.

* Application is using ASP.NET 3.5 (I want to move to 4.0 eventually but I have some migration to deal with).

* Application pool: Classing .NET AppPool (also tried DefaultAppPool).

Any ideas where I can check next?

Surely it shouldn&#39;t be that hard to install IIS, VS, create a web site, and start testing it?

Thanks in advance.

Unable to start debugging on the web server. Could not start ASP.NET debugging VS 2010, II7, Win 7 x64

I have a test ASP.NET MVC3 application developed in VS2012. When I start debugging the app is accessed from the host machine via the request to `http://localhost:&lt;portnumber&gt;`. But if I try to access the same application from the remote machine in the intranet via the `http://&lt;ip&gt;:&lt;portnumber&gt;` I get `HTTP error 400: Bad request. Invalid Host Name.` As far as it runs on IIS Express any server configuration is inaccessible.

Are there any ways of solving this?

Connecting to Visual Studio debugging IIS Express server over the lan

Take the following function:

    DataTable go() {
        return someTableAdapter.getSomeData();
    }

When I set a breakpoint in this function, is there a possibility to inspect the returned value? `go()` is directly coupled to a datagrid in an `.aspx` page.

The only way to inspect the returned datatable is to use a temporary variable. However, that&#39;s a bit inconvenient. Isn&#39;t there another way?


Can I find out the return value before returning while debugging in Visual Studio?

I&#39;m working with an ASP.NET MVC project that seems to be having some issues when attaching to the IIS process (w3wp.exe). I&#39;m running the solution and IIS 8.5 on my own local machine so I wouldn&#39;t think that this has anything to do with our network. What&#39;s strange to me is that I&#39;m able to hit the breakpoints on any other solution I debug locally.

The issue I&#39;m having exactly is that the breakpoints turn to red, hollow circles and never get hit. Usually the fix for this is a Clean/Rebuild of the solution but this hasn&#39;t worked. I&#39;ve confirmed the code is being updated by adding &quot;throw new Exception&quot; to a page and ensuring it shows the exception. Again, this problem is only happening with this one solution. Any other solution I run the debugger with works fine. I&#39;ve also tried restarting the app pool, the website, IIS, and also my computer. 

A few of the articles I read mentioned that anti-virus programs can block a remote debugger from accessing the process. However, the entire setup is contained on my local machine so it doesn&#39;t sound like that would be the issue. It does concern me a bit though because we recently hired a new IT guy that&#39;s been making a lot of changes to everyone&#39;s machine. 

One other point to add that&#39;s unique about this web application is the binding in IIS. The binding is &quot;*&quot; in order to leverage some custom functionality related to subdomains. 

In the meantime, I&#39;ll continue to look for a solution but if anybody has any ideas what may be causing this one solution to not debug properly I&#39;d really appreciate it. 

EDIT: Found a solution that suggested deleting the ASP.NET temporary files. No luck.

Visual Studio breakpoints not being hit

### Background

I have an ASP.NET MVC application project, along with various other projects within a Visual Studio solution. The different projects use various versions of the NPoco library as follows:

* The MVC project includes a version of NPoco through NuGet.
* Some other projects include a (probably different) version of NPoco through a reference to a DLL (not the DLL provided through NuGet).
* One of the projects is the source code of a version of NPoco with some alterations made.

I&#39;m using Visual Studio 2015 Update 3 14.0.25422.01.

### Error
For some reason, when I launch this application in the debugger using the normal Start Debugging command in Visual Studio, it launches, but it also produces the following warning:

[![You are debugging a Release build of NPoco.dll. Using Just My Code with Release builds using compiler optimizations results in a degraded debugging experience (e.g. breakpoints will not be hit).][1]][1]

If I press **Continue Debugging**, everything seems to still work as usual, including breakpoints.

This problem only started happening recently.

### Question

1. Anyone know what caused the above error?
2. Do I have something misconfigured?


  [1]: http://i.stack.imgur.com/1r09x.png

Error: You are debugging a Release build of X.dll

I am trying to debug a project that has a reference to a DLL that I added, the DLL is stored in an external directory and I just added a reference. Now of course I can debug my project but the line that calls a method on my other dll I can&#39;t step into it, i.e. F12.

One way I was able to do this was to add my project (dll) as an existing project to my solution and replace the referenced dll to use the attached project rather than a file on disk.

But what a mess, I am sure there is a cleaner way?

I seem to remember if I copy some PDB files or something but i can&#39;t remember. And Do i need to open 2 copies of visual studio, 1 for my main project and 1 for my referenced DLL??



Visual Studio: Debugging a referenced DLL, I have source in another SLN

When a debugger is attached to a .NET process, it (usually) stops when an unhandled exception is thrown.

However, this doesn&#39;t seem to work when you&#39;re in an `async` method.

The scenarios I&#39;ve tried before are listed in the following code:

    class Program
    {
        static void Main()
        {
            // Debugger stopps correctly
            Task.Run(() =&gt; SyncOp());
    
            // Debugger doesn&#39;t stop
            Task.Run(async () =&gt; SyncOp());
    
            // Debugger doesn&#39;t stop
            Task.Run((Func&lt;Task&gt;)AsyncTaskOp);
    
            // Debugger stops on &quot;Wait()&quot; with &quot;AggregateException&quot;
            Task.Run(() =&gt; AsyncTaskOp().Wait());
    
            // Throws &quot;Exceptions was unhandled by user code&quot; on &quot;await&quot;
            Task.Run(() =&gt; AsyncVoidOp());
    
            Thread.Sleep(2000);
        }
    
        static void SyncOp()
        {
            throw new Exception(&quot;Exception in sync method&quot;);
        }
    
        async static void AsyncVoidOp()
        {
            await AsyncTaskOp();
        }
    
        async static Task AsyncTaskOp()
        {
            await Task.Delay(300);
            throw new Exception(&quot;Exception in async method&quot;);
        }
    }

Am I missing something? How can I make the debugger to break/stop on the exception in `AsyncTaskOp()`?

Debugger not breaking/stopping for exceptions in async method

How do I disable messages in the debug output windows of visual studio 2012?
&gt; The thread &#39;&lt;No Name&gt;&#39; (0x2360) has exited with code 0 (0x0)

Since the count of such messages is so high they bother me and hide my custom debugging information written using `Debug.Write`. Should I highlight my custom debugging information using red instead?

Disable noise messages in debug output windows - visual studio 2012

I&#39;m not sure what I did, but all of a sudden, my **Visual Studio 2012** will not debug any tests.

If I select a test from the **Test Explorer** and tell it to run, it simply outputs this in the Test Output window:

    &gt; ------ Discover test started ------
    &gt; ========== Discover test finished: 29 found (0:00:01.3371755) ==========
    &gt; ------ Run test started ------ Process with an Id of -1 is not running.
    &gt; ========== Run test finished: 0 run (0:00:01.4711861) ==========

what the heck does that mean?! After doing this a few times, the error changed to:

    The Operation was Cancelled
which I sure didn&#39;t do.

It&#39;s doing this on every test in the list.

however, I can RUN the tests no problem, and they pass... but I cannot debug the tests.

What might I have done? I did not actively go into any settings and change anything, perhaps a stray click somewhere, but where?

Visual Studio - suddenly cannot debug tests

I have installed VS 2015 RTM (nothing else) and I&#39;m unable to debug any solution, not matter if it&#39;s an existing one or a brand new one (created with VS 2015 and compiled against .Net Framework 4.6), it only opens a new tab in VS which is called Break Mode with the following text:
The application is in break mode
Your app has entered a break state, but no code is executing that is supported by the selected debug  engine  (for e.g. only native runtime code is executing).
And if I check the Debug --&gt; Module Window:
VS2015Test.vshost.exe no symbols loaded (even if I click load symbol it does not work)
VS2015Test.exe symbols loaded

And it also doesn&#39;t show the output on the console(it&#39;s a console application that just has the following lines of code:

    class Program
    {
            static void Main(string[] args)
            {
                Console.WriteLine(&quot;TEST&quot;);
                Console.ReadKey();
            }
        }


I tried to reinstall VS 2015, restarted the computer, deleted all files in %temp%/AppData/Microsoft/Visual Studio/14, started VS in Admin Mode but nothing seems to work.

One thing which makes debugging working is this option:
Tools --&gt; Options --&gt; Debugging --&gt; Use Managed Compability Mode

^^But that can&#39;t be the solution to use an old/legacy mode.

BTW: Debugging in VS 2013 is working fine.

Any help would be appreciated.

Visual Studio 2015 RTM - Debugging not working

It&#39;s clear why stack traces are affected with Microsoft&#39;s new programming paradigm. We now have a semantic stack and a couple of physical ones (my choice of words).

What I get to see is an exception&#39;s `StackTrace` property (and in the debugger) is the physical ones, concatenated:

    private async Task CheckFooAndBar()
    {
        var log = LogManager.GetLogger(&quot;Test&quot;);
        log.Info(&quot;CheckFooAndBar&quot;);
        try
        {
            await Foo();
        }
        catch (Exception ex)
        {
            log.Info(&quot;StackTrace of last exception: &quot; + ex.StackTrace);
        }
        Console.ReadKey();
    }
    private async Task Foo()
    {
        await Task.Factory.StartNew(() =&gt; Thread.Sleep(1000));
        await Bar();
        await Task.Factory.StartNew(() =&gt; Thread.Sleep(1000));
    }
    private async Task Bar()
    {
        await Task.Factory.StartNew(() =&gt; Thread.Sleep(1000));
        throw new Exception();
        await Task.Factory.StartNew(() =&gt; Thread.Sleep(1000));
    }

This gives:

    StackTrace of last exception:    at NLogAsyncExceptionTestCase.Program.&lt;Bar&gt;d__d.MoveNext() in c:\Users\Jens\Documents\Visual Studio 2012\Projects\NLogAsyncExceptionTestCase\NLogAsyncExceptionTestCase.Console\Program.cs:line 53
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
       at NLogAsyncExceptionTestCase.Program.&lt;Foo&gt;d__8.MoveNext() in c:\Users\Jens\Documents\Visual Studio 2012\Projects\NLogAsyncExceptionTestCase\NLogAsyncExceptionTestCase.Console\Program.cs:line 44
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
       at NLogAsyncExceptionTestCase.Program.&lt;CheckFooAndBar&gt;d__0.MoveNext() in c:\Users\Jens\Documents\Visual Studio 2012\Projects\NLogAsyncExceptionTestCase\NLogAsyncExceptionTestCase.Console\Program.cs:line 30 

My question is: Is there a (convenient, standard) way to convert this to a proper backtrace in the semantic sense, such as:

    CheckFooAndBar
    Foo
    Bar

Of course there could be a mixture of awaits and inline path fragments in the stack.

I tried looking at the stack as it is with .NET 4.5 and SL5 with the async targetting pack, but not yet with WinRT. The output is from .NET 4.5.

In SL5, which is what I mainly do, the situation is more problematic: You don&#39;t get line numbers in stack traces in Silverlight (even with elevated privileges), which makes the need for context more important.

Stack traces with async/await

After using VS2015 snapshot and profiling tools, I can&#39;t seem to get the diagnostics tools to work again. Every project, even new ones just say the following 

&gt; The Diagnostic Tools window does not support the current debugging
&gt; configuration.

[![enter image description here][1]][1]


Tried creating new and different type projects, running as administrator, deleting program data, app data, repairing and re-installing from uninstall.


Anyone experienced this?, shame as they&#39;ve improved this tool a lot in this version.

  [1]: http://i.stack.imgur.com/iu3e5.png

Visual Studio 2015 diagnostics tool does not support current debugging configuration

All of a sudden, I have run into an issue where I cannot step into any code through debugging in Visual Studio. The step over works fine, but it refuses to step into (&lt;kbd&gt;F11&lt;/kbd&gt;) any of my code. This was working before, now all of a sudden it does not. 

I&#39;ve tried some things below, but I still had no success:

- Delete all bin files in every project in my solution, clean solution, re-build solution. 

- Build projects in solution indivdualy

- Restart machine

It an [ASP.NET][1] [C#][2] application consuming a [WCF][3] sevice locally. It is in debug mode. I have a breakpoint set on the page consuming the service. The breakpoint hits, but it will not step into the service code.

The ASP.NET site and the service code is all in the same solution. This all of a sudden does not work, it did work before.

How can I fix this problem?

Adding a breakpoint to the service project I get a warning:

&gt; Breakpoint will not currently be hit. No symbols have been loaded for this document.
	
I deleted all the bin folders for all the projects and re-built them one by one. They all succeeded, but still I am getting the *symbols won&#39;t load* on any breakpoint I put into any project in the solution other than the ASP.NET project where the breakpoint works. I was able to debug step into all the projects before, this is an all of a sudden thing. 

Information from the output window..

    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.DurableInstancing\v4.0_4.0.0.0__31bf3856ad364e35\System.Runtime.DurableInstancing.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml.Hosting\v4.0_4.0.0.0__31bf3856ad364e35\System.Xaml.Hosting.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\2d49cf50\14eee2cf\App_Web_jmow15fw.dll&#39;, Symbols loaded.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.WorkflowServices\v4.0_4.0.0.0__31bf3856ad364e35\System.WorkflowServices.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Web\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Discovery\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Discovery.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activities.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Routing\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Routing.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Channels\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Channels.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.
    &#39;WebDev.WebServer40.EXE&#39; (Managed (v4.0.30319)): Loaded &#39;C:\windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll&#39;, Skipped loading symbols. Module is optimized and the debugger option &#39;Just My Code&#39; is enabled.

  [1]: http://en.wikipedia.org/wiki/ASP.NET
  [2]: http://en.wikipedia.org/wiki/C_Sharp_%28programming_language%29
  [3]: http://en.wikipedia.org/wiki/Windows_Communication_Foundation


All Visual Studio-Debugging Solutions on Gang of Coders

Total of 20 Visual Studio-Debugging Solutions