VMWare VMDebugger “unable to detect current startup project”

 

I spent many small packets of time trying to find a solution to this problem over about two months.  Luckily, I stumbled across an answer that actually worked for me.

Problem: Visual Studio 2008 with VMWare VMDebugger integration does not work.  When I try to launch debugging in a VM, I get a message that says “Unable to detect current startup project”.

Solution:  Remove any installer projects that are in the solution.

Source: Read MartinMoesby comment here.

SnippetCompiler is great, but…

…we don’t have to use it for quick compilable chunks of .NET goodness.  As detailed on marlongrech.wordpress.com, we can use TestDriven.Net to run small parts of code in the Visual Studio.NET debugger.

The code is not required to be a test case for use in a unit testing framework.  It can be an arbitrary method that just does some processing.  The key to using this technique, is to make sure you set a breakpoint.  That way you can manipulate parameters and actually get feedback about what the method is doing when it executes.

This is yet another reason we should buy TestDriven.Net.  It can pay for itself within a day or two.

In addition to SnippetCompiler and TestDriven.Net, Powershell is very useful for this kind of snippet testing as well.  But I’ll have to defer that post for another time.

An exciting new release making headlines everywhere!

Curtis Mitchell is blogging now! Let the people rejoice!

Oh yeah…and in an apparent attempt to steal my thunder, Microsoft (Macrocompetitor) announced that they are releasing the .NET Framework source via a shared license for debugging purposes. This is great news, since I was just explaining to Mark that scripting languages are better for web sites (IMO) than compiled languages because you can follow each line of executed code.

Microsoft must have a psychic friend on speed dial. This is a big step in the right direction for them. Checkout the announcement from Scott.