I'm required to debug a .NET codes on a web application that was built using VS2003.
The web application requires authorization login to access and has its own database which located at another server.
The web application was on the production web server.
To test the fix, I need to copy out the whole solution into my local machine and I tried to compile it. And of course, as many of you have guessed it, it will not work since I need to change some connection strings or values first.
Does any of you know usually which place to look into when this happens?
Web.Config is one place, I heard. Any other areas I should look out also?
Thanks.
Loading
JohnPosted Apr 7, 2007, 10:10 PM
1. Make sure you set the project up in IIS. It needs to be its own web site, or at least a virtual directory.
2. Open the file that ends in ".webinfo". This file has the http path to the project. Make sure it is correct. It may have been a different path on the production server.
3. If you are trying to run in debug, make sure Debugging is set to true in the web.config
4. If the problem is the connection string is now pointing to the wrong database, this will not cause a build error but a run time error. To fix this, put a breakpoint somewhere in the page_load and step through until it tries to connect to the database. You should then see where the connection string is coming from.
Let me know if there is a specific error you are getting....
Mahesh ChandPosted Apr 3, 2007, 10:14 AM
MaheshPosted Apr 3, 2007, 7:50 AM