VS2010 null reference errors

[mcutter]

We upgraded to Vault 5 and VS2010 last week.
Twice today I have been unable to check in changes from VS2010, with a null reference exception.
The workaround each time was to check in with the Vault Client, which is slightly inconvenient.

[Beth]

Has the project already gone through the upgrade from the version of VS you had before to VS 2010 or was this project created in VS 2010?

If the project was upgraded, which version did you upgrade from?

Are you using the Vault Enhanced Client or the Vault Classic Client? Did you switch which client you were using as well, or were you using the same client before?

[mcutter]

Project has already been upgraded from VS2008 to VS2010, using Vault Enhanced Client for both.
This happened several more times and then I discovered that all of the projects had gone offline.
So I restarted VS2010 and they are all back online.
Other developers are connected to the same repository and have not had any probs.
Strange behavior.

[Beth]

If Vault isn't accessible while you are working on your project, I think it can go offline. It's not always readily apparent. If your solution is going offline regularly, then we might need to discuss why that is.