Hi,
We are encountering an issue while checking-in any code file on Vault.
The error states: "Object reference not set to an instance object"
Request you to kindly provide us the solution to rectify the same.
Thanks,
Vijay
Check-in: Object reference not set to an instance object
Moderator: SourceGear
You shouldn't be bouncing between Vault and VS for check ins. Do you get the error when using Vault for the check in or when using VS?
The problem with using both for the same functions is that almost always, people end up with the working folder in Vault set differently than the working folder in Visual Studio. When using IDE integration, Visual Studio has to run the show, especially with anything that involves setting the working folder.
If you ever can't check in through VS, then rather than switching over to Vault, why it won't check in in VS should be looked at and fixed. Usually, it's a binding issue that can be resolved in just a minute or two.
Is the file you can't check in, checked out through Visual Studio? Can you check it in through Visual Studio?
The problem with using both for the same functions is that almost always, people end up with the working folder in Vault set differently than the working folder in Visual Studio. When using IDE integration, Visual Studio has to run the show, especially with anything that involves setting the working folder.
If you ever can't check in through VS, then rather than switching over to Vault, why it won't check in in VS should be looked at and fixed. Usually, it's a binding issue that can be resolved in just a minute or two.
Is the file you can't check in, checked out through Visual Studio? Can you check it in through Visual Studio?
Also, you can try clearing your Client Side Cache. You will want to keep the cachemember_workingfolderassignments, and afterwards perform a Get with the option "Do Not Overwrite/Merge Later
version.xml
An error occurred when trying to connect vault client giving error " retrieve version.xml file from the SourceGear website