Wednesday, August 01, 2007

Vista and Visual Studio 2003 again..

After the computer-switch I had to set up Vista for devlopment with Visual Studio 2003 again, and was a bit disappointed by my last post about the topic - I hadn't written anything at all about how I actually set up IIS 7.0 to be able to debug and run .Net 1.1 applications! So here it is.. the short version:

  • Register .Net 1.1 ASP.NET by running the following program. The -i parameter tells the utility to install support for ASP.NET 1.1 under IIS: Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exeaspnet_regiis.exe -i
  • Change the application pool to one using the .Net framework 1.1 for the application you want to debug and run

I also enabled .Net development and CGI in the additional windows components the "Windows functions" control panel applet.

Vista OEM - Network Troubles

Since I'm usually sitting at my desk developing new and interesting stuff for my company, using a slow (but cool :-) old Tablet PC wasn't the best way to be an effective developer.

Last week I got myself a new PC that will sit at my desk at work. It's a fast and brand new dual core computer with loads of memory, a big harddrive and a DirectX 10-based video card. I choose Windows Vista Business, since I've been quite happy with the way Vista has been working on my Tablet PC.

The only problem came when I was about to check in some source code to subversion. TortoiseSVN complained with a message saying it couldn't move a file in the repository. The repository is located on a network share and accessed by a small group of programmers.

I searched all over to see if this was a common problem with subversion, but found nothing. Then I noticed that I couldn't rename files on the network, and started to search for similar reports on the net. At last I found this post, which helped me fix the issue.

So why the OEM troubles heading? Read the above post - the bug has to do with something missing in the OEM version of Vista.