When debugging a website in asp.net I received the following error within Visual Studio 2005:

Unable to start debugging on the web server. The server committed a protocol violation. Section=ResponseStatusLine

It turns out that Skype tries to use port 80 to receive incoming connections, which means that IIS can't use port 80. In Skype, go to Tools > Options > Connection and remove the tick in use port 80 and 443 as alternatives for incoming connections. You need to exit skype and restart it for the changes to take effect. Don't forget to start the IIS website too. [tags]visual studio, asp.net, skype[/tags]

VMware Workstation 6 beta has been released. The three things that excite me most are:

1. Vista host support
2. Multiple monitor support
3. IDE integration

I've just installed Vista as my main dev environment, and although I managed to get VMware Workstation 5 working under Vista RC-1, the performance was sluggish at best, and took ages to start up (this was noted in the VMware forums). Multiple monitor support is also great, as that is mainly what has prevented me from using VMware as a regular machine, rather than an occasional testing platform. Now that it supports multiple monitors, I feel like I can use it properly (and I will have to if I'm going to do any maintenance programming with Visual Studio 2003 (.net 1.1 apps) as VS2003 is only supported on XP, not Vista). That brings me to the final thing that excites me - Visual Studio IDE Integration. From what I've read, it means that I can run a app from within visual studio on my host machine, and it will execute within the VMware hosted environment. Sounds great, except for the following error when starting Visual Studio 2005 after installing vm ware 6 beta (ok, it is beta!)

An error has occurred while trying to access the log file. Logging may not function properly.

Anyway, it's do do with the visual studio plugin, You need to end proccess on devenv.exe in task manager, and restart Visual Studio whilst holding the Left-Ctrl+Shift. This starts it without the add-ins. Next, go to Tools > Add-in Manager... and remove the Start tick in VMDebugger. That should get visual studio working (albeit without the integrated vm debugging, I guess I'll have to wait for that one). BUT it turns out that on my system for some reason, it ignores the "start" tick, as soon as you close the add-in manager. To hack it, use regedit to go to HKEY_LOCAL_MACHINE\Software\Microsoft \VisualStudio\8.0\Addins\VMDebugger.Connect and set LoadBehaviour Dword value to 0 (instead of 1). Now that works fine. [tags]vmware, visual studio, vista[/tags]