VS 2005 insanity

frizzo · Post by **frizzo** » Thu Feb 23, 2006 1:58 pm

I have Vault 3.1.2 integrated with Visual Studio 2005. And i am experiencing problems on almost daily basis. I don't know which product is to blame.

I have a solution, which includes several pieces:

1. Web Services project
2. BusinessLayer project
3. CommonLayer project
4. DataLayer project

Web Services project has a dependency on the BusinessLayer project.
BusinessLayer project has a dependency on the CommonLayer and DataLayer. DataLayer has a dependency on nothing.

I have the following problems with this setup.

1. Every now and then, I'll open a solution and when it loads, the Pending Checkings window shows that the DataLayer.PDB file (which sits in the BIN folder of the Web Services project, because it has an indirect reference to it) wants to be checked in.

2. If I delete all the code from the local directories and do a get latest on everything and then open the solution, it wants me to reconnect all the source control bindings. Is this the correct behavior? If not, how do I stop it.

Post by **Tonya** » Thu Feb 23, 2006 3:09 pm

I believe the problem that you're reporting is one that we are familiar with and is supposed to be resolved by Microsoft. Can you review the following link and let me know if this isn't the same issue?

http://lab.msdn.microsoft.com/productfe ... 69c79367c5

Thanks,

Tonya Nunn
SourceGear

frizzo · Post by **frizzo** » Thu Feb 23, 2006 7:48 pm

Thanks, Tonya. It is definetely similar, though not exactly the same. It could the same issue though.

Various comments mention several workarounds, but describe none of them. Are you aware of any of the workarounds? What does SourceGear recommend?

Tonya wrote:I believe the problem that you're reporting is one that we are familiar with and is supposed to be resolved by Microsoft. Can you review the following link and let me know if this isn't the same issue?

http://lab.msdn.microsoft.com/productfe ... 69c79367c5

Thanks,

Tonya Nunn
SourceGear

Post by **Tonya** » Fri Feb 24, 2006 9:48 am

You could try cloaking the bin folder in the Vault GUI client, and then restarting Visual Studio. That was a workaround that seemed to have worked for others.

We have had a lot of suggestions on workarounds to resolve this issue, it appears that some ideas work for some and not others. The following post has a complete list of suggestions:

http://support.sourcegear.com/viewtopic ... 0184#20184

Tonya