Last post Feb 02, 2007 03:00 PM by Dan_UK
Feb 01, 2007 05:59 AM|Dan_UK|LINK
Hope somebody can help me with this, as it's driving me mad!
I've got a web solution that contains 3 web projects. The structure is such that there's the main project which is located directly in wwwroot. The other two web projects are then located in sub-folders (which are set as web-apps).
When I open the solution in VS.NET 2003, I get a timeout opening the main project located in wwwroot. If I acknowledge the error, it proceeds to load the other two projects without a problem.
Exact error is: "The Web server reported the following error when attempting to create or open the Web project located at the following location 'http://localhost'. 'The operation timed out'."
I've looked in the SLN file and the Webinfo file for the project and both point to the correct location i.e.
http://localhost/project.vbproj etc. Localhost is correct, I can browse to this.
So, I can't figure out at all why it won't open the project. And the strange thing is that, I have a number of sites and the way i've always worked is to swap them in and out of wwwroot depending on which one I want to be working on. ALL the other sites
work fine with their references to
http://localhost/projectname.vbproj. It's just this one that doesn't work. And it only doesn't work on my new machine. If I go back to my old machine the project opens fine.
Soooo ... it can't be a problem with the SLN/WebInfo/Project files that I can think of. The identical solution works fine on my other machine? It can't be an IIS/Permissions issue, as other sites open fine when I swap them into that location?
What else can it be?? I've tried clearing the VS.NET project cache, deleting SUO files and so on, but still the problem remains and all i'm able to do is sob pathetically at VS.NET and tell it that the damn file is there, just try looking harder!
Any help massively appreciated
Feb 02, 2007 03:00 PM|Dan_UK|LINK
For anyone that's interested, it turned out to be a problem with a component I was using: Rewrite.NET
I had to remove a line from the web.config and also I have to remove the DLLs from the bin before the project opens.
So I suppose i've learnt that VS.NET reads the web.config when opening a project. That a problem here could stop the project opening. And that when the project fails to open it will give you the most ambiguous error message you have ever seen to ensure that
you waste the next 96 hours of your life ... hurrah!