Last post Jan 20, 2009 03:18 AM by TATWORTH
Nov 19, 2008 09:21 PM|interestedin|LINK
I got a new ASP.NET project - 'Production' (VB.NET, Framework 1.1, SQL Server 2005) I will be upgrading the application with some new cool features.
I need some advise on how to set up my development environment so that I do a good job and update the finished product to the repository successfully. Here is what i did and steps I need to do
1. A) Checked the asp application from the repository into my Directory on C:/MyDocuments/Visual Studio 2003/Production/. (why here? [:(])
B) Checked the application from the repository into c:/Inetpub/wwwroot/Production.
2. Restored the sql database from the production server to a local sql server to use as a backend.
A) When I open the project from C:/MyDocuments/Visual Studio 2003/Production/ , it complains "Unable to get the project from the Web Server. Unable to open Web
project 'Production'. The file path C:/MyDocuments/Visual Studio 2003/Production/ doesn't correspond to the URL http://localhost/Production. The two need to map to the same server location. HTTP Error 404. Not Found." Do I need to deal with C:/Inetpub
directory instead so that the project's path would also be http://localhost/Production? Or do I reference an IIS virtual 'Production' directory to where I put the application from the repository in step 1, and use the local development ASP.NET server?
B) When opening from c:/Inetpub/wwwroot/Production it would also compaln that it was unable to open the project from the Web Server. I figured that the solution
was trying to connect to its original Web server . So I opened the vb project in VS 2003, not the solution, compiled it and overrode the original solution by saving the project in a new solution with same name and same location. Now I wonder what is it
that i overrode and that will need to be restored when I update the repository.
Anyway, now the solution opens well although comlaining on the way that "Refreshing the project failed. Unable to retrieve folder information from the server."
I though the app once again tried to get info from the original web server. I went to web.config and found a pointer key/value pair key="WebServerName", changed the value to "localhost". No effect [:S]
I understand that you may have questions to understand the situation better. Hope to find here some guidance from more experienced developers and participate in
a potentially interesting discussion on the options I have.
Jan 14, 2009 09:34 PM|Kumar Reddi|LINK
Simply start fresh. Delete the virtual directory in the IIS and dump your project files in the wwwroot folder, then go to IIS and turn the Production folder as an application. Now, try to open the project file (.csproj) using the VS .NET 2003. And tell
us what exactly the error message you get.
.sln and .csproj files are simply text files. You can use any text editor and try opening and see if you see anything weird in those files. They usually contain the references to all the project files..
Jan 15, 2009 08:36 AM|interestedin|LINK
Hi, It is a little too late but thank you very much any way, i am almost done with the project. Yes, the problem wwa in .sln. I deleted the one i checked out, opened the projects into a new solution and recompiled it, then it worked fine.
Jan 15, 2009 09:20 AM|Kumar Reddi|LINK
oops.. my bad.. I didnt check the date this question was posted on.. I was simply going through the Unanswered questions in that category and responded..
Jan 15, 2009 10:39 AM|interestedin|LINK
I was wondering why the post wasn't getting any response, may be my problem definition was somewhat confusing? What do you think?
thank you once again,
Jan 15, 2009 11:04 AM|Kumar Reddi|LINK
Yah. I guess most people do not bother to read.. if the post is longer than few lines.. Just like the way we skim the headlines.. And yeah.. I guess the question sounded little confusing too
Jan 15, 2009 01:55 PM|interestedin|LINK
good [Yes], thanks!
Jan 20, 2009 03:18 AM|TATWORTH|LINK
>good , thanks!
Please indicate that your question has been answered, by clickimg the "Mark As Answer" against the replies that helped you.