I don't want a new path

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

I don't want a new path

Post by Dino » Wed May 11, 2005 6:49 pm

VS.Net crashed on me, and now when I open my solution it wants to stick my website in a new folder - I don't want that, I want my existing website opened. How do I convince Vault/VS.Net not to create a new website and open it from Vault, but to use the correct one that is already sitting there?

I can open the website as a project without problem, but can't open it in a colution any more - any ideas?

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Wed May 11, 2005 6:58 pm

Have you tried doing a Bind operation from Change Source Control? That might work...

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Post by Dino » Wed May 11, 2005 7:00 pm

But I can't even open the project in my solution, because it wants to open it from Vault - and if I just open the website, it opens perfectly as it is...

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Wed May 11, 2005 7:13 pm

Try cancelling the login when it wants to open from Vault. This will make everything go into disconnected mode, but you might want that temporarily. Then try to rebind the web project separately.

If this isn't working at all, you could try a brand new Open From Source Control, and when it gets to the web project, I think VS allows you to choose an existing virtual folder.

And, if that doesn't work, you can alway remove the local virtual folder (copy it somewhere else first), have Visual Studio recreate it, and then copy your stuff back over it.

Sorry this is a pain, but we don't have a lot of control over how VS handles it...

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Post by Dino » Wed May 11, 2005 7:14 pm

It's not asking me to log in - it's asking me where I want to stick the web project!

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed May 11, 2005 7:54 pm

Try deleting your vswebcache (it's in c:\documents and settings\user\vswebcache) directory first. If that doesn't clear up your problem, delete the virtual directory in IIS and let VS.Net create a new one.

Just a couple of ideas.

Post Reply