asp.net 2.0 Deployment Problem
-
(1) I have a simple web app (just a label) developed in VS 2005 that successfully runs on a development box. (2) I have a website that successfully runs a full VS 2005 asp.net app. (3) I created a virtual directory under the full web app. (4) I published the simple web app to the virtual directory site. PROBLEM: The simple web app will not run. It tells me that "The resource can not be found". I have tried numerous things to no avail. Putting a simple html page in the directory works fine. Is there something simple I am missing?
-
(1) I have a simple web app (just a label) developed in VS 2005 that successfully runs on a development box. (2) I have a website that successfully runs a full VS 2005 asp.net app. (3) I created a virtual directory under the full web app. (4) I published the simple web app to the virtual directory site. PROBLEM: The simple web app will not run. It tells me that "The resource can not be found". I have tried numerous things to no avail. Putting a simple html page in the directory works fine. Is there something simple I am missing?
When you deploy/publish the project, do you select "use fixed naming and single page assemblies"? Cheers Al
-
When you deploy/publish the project, do you select "use fixed naming and single page assemblies"? Cheers Al
Tried it both ways - Still can't find the resource. Strange - we have done this in .Net 1.1 without a problem.
-
Tried it both ways - Still can't find the resource. Strange - we have done this in .Net 1.1 without a problem.
Please can you post the error here? Thanks Al
-
Please can you post the error here? Thanks Al
Solved the problem - only took us about 8 hours. :mad: Seems that one of the security patches issue by MS changed the way backslashes are processed in the
Home Directoryfield. There should no longer be any trailing backslashes. We checked this earlier on the virtual directory and it didn't have one. We failed to check the root directory (which did - although that application was working OK). I think Asp.Net was doing this:X:\ + \VirtualDirectory = X:\\VirtualDirectoryThis, of course, led to the resource not found error. IIS didn't have a problem with a simple HTML file so, I have to assume it only matters to the Asp.Net handler. We got rid of the backslash and now everything is happy. Thanks for the help. :-D
-
Solved the problem - only took us about 8 hours. :mad: Seems that one of the security patches issue by MS changed the way backslashes are processed in the
Home Directoryfield. There should no longer be any trailing backslashes. We checked this earlier on the virtual directory and it didn't have one. We failed to check the root directory (which did - although that application was working OK). I think Asp.Net was doing this:X:\ + \VirtualDirectory = X:\\VirtualDirectoryThis, of course, led to the resource not found error. IIS didn't have a problem with a simple HTML file so, I have to assume it only matters to the Asp.Net handler. We got rid of the backslash and now everything is happy. Thanks for the help. :-D
That's weird. Normally use the Server.MapPath in order to get the path instead of hardcoding it. Good you found it!! Cheers Al
-
That's weird. Normally use the Server.MapPath in order to get the path instead of hardcoding it. Good you found it!! Cheers Al
It wasn't in my code - It was in the IIS configuration. It was IIS's Asp.Net handler that couldn't find its own code.
-
It wasn't in my code - It was in the IIS configuration. It was IIS's Asp.Net handler that couldn't find its own code.
Hate IIS!! I have a project I have been writing for months now to managed IIS 6. I have never finish as I never had the time. Someday .... Someday ....