Hi there

I have a DNN compiled module developed in a Visual Studio 2008 solution. Am I right in thinking that there is a bug in VS 2008 that stops VS accessing virtual directories it has created in IIS 5.1 (the version you have to use in XP SP3)? For a start, VS is really picky about recognizing virtual directories in any case - when you configure the web settings for the DNN project, choosing the 'Local IIS' options, it will only allow you to create a new virtual directory, it doesn't recognize ones already created. But then the problem gets ridiculous! When you save and reopen the project in question, VS no longer recognizes any virtual directories it previously  created, and refuses to load the project, with an error:

'The local IIS URL .... has not been configured. In order to open this project the virtual directory needs to be configured. Would you like to create the virtual directory now?'

to which if you choose Yes, it complains the VD is already mapped, which of course it is because VS previously created it! So whether you choose Yes or No, the result is the same = the project wont load. It looks like I will have to manually edit the vsproj file to remove the IISUrl attributes, just to get the project to load. And then reconfigure the VDs needed to point to the DNN module, as described here:

http://p2p.wrox.com/book-professional-dotnetnuke-module-programming-isbn-978-0-470-17116-5/73025-project-url-setting.html

but even though I followed these instructions, I still get the selfsame error that the instructions aim to address, only the error is delayed until I load the project again, as I have described above.

Does anybody know why this is happening, and how to work around it? Surely this is a bug to do with the way VS 2008 talks to IIS?
I've tried all the usual stuff, reinstalling the framework from the command line, giving permissions to the ASPNET account, etc but the way this goes wrong only after a successful save makes me conclude this is a bug, has anybody experienced similiar?

Cheers