Last post Jul 03, 2005 05:09 PM by bluekiwi
Jan 20, 2005 09:54 PM|Canada77|LINK
Jan 21, 2005 06:05 PM|bash_MS|LINK
Jan 23, 2005 09:02 PM|Canada77|LINK
May 09, 2005 11:53 AM|bluekiwi|LINK
May 10, 2005 06:54 AM|bluekiwi|LINK
May 10, 2005 07:24 AM|bluekiwi|LINK
May 11, 2005 07:07 AM|bluekiwi|LINK
Jul 02, 2005 07:39 PM|munstergb|LINK
Hey, I feel your pain! I have the same problem with a near identical install to yours.......
I've also seen all the different suggestions floating around and, to be honest, the closest seems to be your suggestion of copying files into another new project!
Did you ever try the suggestion from the MCP of changing the project directory "Properties" to "Web Sharing"?
Didn't work for me......and, to be honest, it seems an odd way to fix this problem.
The other strange thing is this:
I can define the application through inetmgr (IIS Mgr), e.g. MyApp, and then set the "local path" to the location of the ASP.NET application code.
I can then fire up IE and use the URL http://localhost/MyApp and the application runs fine?!
I also have various ASP.NET projects on my machine (from different authors) and they all load into VS fine (even without Webshare property set on directory).
I can even create new ASP.NET projects from VS with no problems......
Does anyone have any other ideas......?
Jul 02, 2005 08:23 PM|munstergb|LINK
I think I found a solution to my own question.
For each of the ASP.NET applications I was trying to open with VS.NET all of then had pre-built solution file (generated on another machine/directory structure).
There seems to be 2 files that somehow keep track of the intended location of the application on the webserver. They are:
(a) MyApp.vbproj.webinfo, and,
The first can be edited with a text editor, changing something the UNCWeb value from, say :
Then set up the application on IIS Mgr (Virtual Directory set to Application with script/exe settings), e.g. Default Web Site --- MyApp
Set the "local path" to location of asp.net application on local drive, say: C:/Somedir/Development/MyApp.
Then open the MyApp.vbproj file (and NOT the old solutions file).
Rebuild (F5) whatever .....and it works.
Got to think this is a bug in VS.....surely on opening the project it should give you an option to re-set some basic configurations and try again rather than
just giving the message:
“Visual Studio .NET cannot create the application <application>. The likeliest problem is that required components are not installed on the local Web server”....things like (i) Reset location on localhost,
(ii) check permissions, etc.
Jul 03, 2005 02:47 PM|munstergb|LINK
Jul 03, 2005 05:09 PM|bluekiwi|LINK