>Hi,
>
>Currently, my company have a web based ASP.NET written application
>using SQL Server 2000 db.
>we have our own testing and production server for testing and deploying use.
>
>Therefor, how can I configure or setup my Win 2000/2003 server to
>allow me to test my application in test/production environment with their
>own code and own database ? Some of our code are hard code to use
>some path which we are looking to change it.
>
>Anyone got any good suggestion or advise.

This is not a trivial question <g>...

Really the most important thing is to build your application in such a way that there are no hardcoded dependencies anywhere. If you're using Web paths always ResolveUrl() to figure out relative Urls and MapPath for physical paths. if that doesn't work always (and it doesn't) it's a good idea to have a configuration object/store that you use to hold a base path for your application both as Web and physical paths.

If you do this it takes care of application location independence pretty well. Beyond that is then simply configuration file setup.

For databases - invest in a good synching tool like RedGate's SqlCompare/SqlDataCompare, which are incredible time savers both for directly syncing databases as well as creating sync scripts you can ship with your applications.

Those are the most obvious things you need to deal with - beyond that there maybe assembly distribution issues, and depending on what other dependencies you have for Interop COM registrations etc. which gets to be more complicated.

One of the things I like so much about ASP.NET is the fact that deployment and duplicating a deploymnet is fairly easy compared to anything that came before it (at least on Windows!).

+++ Rick ---