hi,

I have an ASP / C# .NET2.0 web project that I manually check into & out of VSS on to a primary development system running Visual Studio 2005 Pro. It all works fine.

But how can I check that solution out to a different machine The .sln file has hard-coded path and GUID info, so tightly bound to its host machine. No way it belongs on any other machine.

There doesn't seem to be a 'create project from source' for ASP projects...am I stuck with having to create a new ASP web project & copy my sources over

thanks for any help & have a nice holoday weekend:)

See these references about .NET 1.x and team development to see if they apply to .NET 2.0:

http://www.mztools.com/resources_net_developers.htm#SCC

yeah that thing is outdated now. Junk city.

On my own I see that maintaining a unique <project>.sln file on each dev workstation seems to work.

A database server local to a dev machine will need its own unique web.config file as well.

I tested my theories by moving a .ASP web project from one drive letter to another and it seemed to work ok, but the web.config file, despite being edited to point to a new database .MDF file (same name, different path) would not work (error message: another database by that name already exists).

I have no idea why or how, with new connection strings, the app still remembers its old connection. Why can't it just connect like I tell it to It connects to the central remote SQL server just fine, but I can't switch it to a different local .MDF even with fully qualified paths to the .MDFs.

I would be in business if I could just convince this project to forget about the old connection string that was in web.config and deal with the new one thats in there now & stop calling the database a duplicate. But, its trying too hard to be user friendly to do that.

I had some time to look further into this, & determined that ASP .NET must be maintaining some kind of database name to path state, because no matter what I did I could not get around it except by changing the name of the databases involved. And thats what I did & it worked.

I renamed the relevant .MDF files from Visual Studio 2005 Pro & editied their path properties in the tool, and also the 'AttachDBFilename' and 'Initial Catalog' data in the project's 'web.config' file. Everything else in web.config mercifully stayed the same so I didn't have to modify any application code.

So between the obvious editing required of <project>.sln files and this stuff the problem is resolved. I can now move ASP .NET SQL projects around on a given machine as required, check out, build, & run locally on any machine, & deploy to remote hosts.

me == happy camper;

thanks! :)

-mark aoki

Thanks Carl, but its resolved & we are up.

Sorry I wasn't more clear : )

-m.aoki