It's definitely something with VS2005 integration. Once VS2005 gets its hands on the project, Vault can no longer use the working folders (with the Ticks errors). Does the integration use the VaultGUIClient and it's config file? Or is there somewhere else I can force the integration component to use .Net 1.1?
Even if you turn SCIntegration OFF in VS, it still sees the SC files and tries to do stuff to them
stuck - Ticks out of range - High priority
Moderator: SourceGear
Both the GUI client and the IDE client use the same state files on the client. However, if you turn off or unbind the VS2005 project and just use the GUI client, the IDE client should no longer affect or use the Vault state files.
I don't believe we were ever successful in getting VS2003 to use the 1.0 framework instead of the 1.1 version, so I would doubt there is a way to get it to use 1.1 when you want 2.0. But, there may be ways to do it that I'm not aware of.
I don't believe we were ever successful in getting VS2003 to use the 1.0 framework instead of the 1.1 version, so I would doubt there is a way to get it to use 1.1 when you want 2.0. But, there may be ways to do it that I'm not aware of.
-
djMax
The binding stuff is really messy. When removing the binding, the solution file changes, seemingly in non-pleasant ways. VS also seems to really try to believe the binding is still there.
Overall, it would just be great if the VS2005 integration worked. I know it's beta, but we are trying to get ahead of the curve for our product and right now Vault is what's stopping us, not VS.
So any info on when VS2005 integration might be attempted and what we can do to help would be appreciated.
Overall, it would just be great if the VS2005 integration worked. I know it's beta, but we are trying to get ahead of the curve for our product and right now Vault is what's stopping us, not VS.
So any info on when VS2005 integration might be attempted and what we can do to help would be appreciated.