Hello There,
I am using SourceGear Vault Version 3.5.1 and Visual Studio 2005 Pro, ASP .Net 2.0 and C#. My boss has put the WebSite project in the Vault Server, he opens it and works fine with it on his computer. On my computer, the first time I opened it (Open From Source Control) everything works fine and the website was matched to Vault. But, all the other times the website opens but it isn´t matched to Vault. How can I solve this problem?
Thanks in Advanced,
CLA.
WebSite doesn't bind to Vault
Moderator: SourceGear
Hello,
I mean that the project opens perfectly (the contents of the files match. I don´t understand what you mean when you say "layout of the project", but I will answer with a guess: the solution tree is ok, all the folders and files are in there right places.), but the padlocks don't appear beside the files. It´s like I was opening a project that isn´t on the Vault Server.
Thanks,
CLA
I mean that the project opens perfectly (the contents of the files match. I don´t understand what you mean when you say "layout of the project", but I will answer with a guess: the solution tree is ok, all the folders and files are in there right places.), but the padlocks don't appear beside the files. It´s like I was opening a project that isn´t on the Vault Server.
Thanks,
CLA
Beth wrote:Do you mean that the contents of the files don't match or that the layout of the project doesn't match? I need to know what exactly doesn't match.
Ok, got it. Something isn't quite right with your bindings.
In order to find out what's going on, I need to know:
1) How your boss is adding the website to Vault, and
2) How you are opening the website.
VS 2005 treats websites differently. They do actually have an .sln, but it places the .sln in a different location that may have nothing to do with the website. If your boss added the website as a website (versus adding as a solution), then you would open it as a website. If it was added as a solution, then you must open it as a solution. This article explains how to open websites in VS 2005: Open Websites.
(Note for other users: If you are using Vault 4.x, my explanation would be the same if you set your client to VS 2003 compatible client. It's a little different with the VS 2005 client.)
In order to find out what's going on, I need to know:
1) How your boss is adding the website to Vault, and
2) How you are opening the website.
VS 2005 treats websites differently. They do actually have an .sln, but it places the .sln in a different location that may have nothing to do with the website. If your boss added the website as a website (versus adding as a solution), then you would open it as a website. If it was added as a solution, then you must open it as a solution. This article explains how to open websites in VS 2005: Open Websites.
(Note for other users: If you are using Vault 4.x, my explanation would be the same if you set your client to VS 2003 compatible client. It's a little different with the VS 2005 client.)
Hello Beth,
I did it as you explained... My boss added the website as Solution so I opened it as a solution and everything works fine. So, I think it isn't necessary to tell you more details.
Thank you very much,
CLA.
I did it as you explained... My boss added the website as Solution so I opened it as a solution and everything works fine. So, I think it isn't necessary to tell you more details.
Thank you very much,
CLA.
Beth wrote:Ok, got it. Something isn't quite right with your bindings.
In order to find out what's going on, I need to know:
1) How your boss is adding the website to Vault, and
2) How you are opening the website.
VS 2005 treats websites differently. They do actually have an .sln, but it places the .sln in a different location that may have nothing to do with the website. If your boss added the website as a website (versus adding as a solution), then you would open it as a website. If it was added as a solution, then you must open it as a solution. This article explains how to open websites in VS 2005: Open Websites.
(Note for other users: If you are using Vault 4.x, my explanation would be the same if you set your client to VS 2003 compatible client. It's a little different with the VS 2005 client.)