XSD Files with SourceVault

Mad Eddie · Post by **Mad Eddie** » Wed Aug 17, 2005 10:00 am

I have been trying to create a typed dataset in VB.NET 2003 but keep running in to problems. It seems that VB handles the XSD file differently to the normal VB Project Files. I Am developing a project with 4 other porgrammers and the XSD file is only being edited by myself however the other programmers do not get these updates. Sometimes Vault will ask to check out the whole Solution and when it does it removes all links to the XSD file which means recoding again. If I do not allow Vault to do this update I can continue to work though obviously the other programmers do not get this latest version.

Is anything known on this problem and/or a fix?

dan · Post by **dan** » Wed Aug 17, 2005 1:20 pm

XSD files do appear to be messed up in VB. Not sure if it is a Visual Studio problem or a Vault problem. We'll try it with VSS as the SCC provider, which will determine where the issue is.

Post by **Tonya** » Wed Aug 17, 2005 2:32 pm

I have been able to reproduce this problem, however it is very random. The problem exists in both Vault and VSS so I am assuming it is an issue with VS.Net. We will be checking further into this problem.

Tonya Nunn
SourceGear Support

Mad Eddie · Post by **Mad Eddie** » Thu Aug 18, 2005 1:33 am

many thanks for the quick response.

Do you know of a way to ease or avoid the problem before a fix ?

Post by **Tonya** » Thu Aug 18, 2005 8:48 am

Sometimes Vault will ask to check out the whole Solution and when it does it removes all links to the XSD file which means recoding again.

When the entire solution gets checked out, does a dialog appear stating that the files should be removed from source code control?

Do you see a pattern when you are prompted to check out the entire solution?

When the other users perform a "get latest" and it doesn't work correctly, does the problem only happen when the entire solution has been checked out by you?

The problems that I run into with the .xsd files are so random that I am having trouble trying to discover a temporary fix.

Tonya Nunn
SourceGear Support

Mad Eddie · Post by **Mad Eddie** » Fri Aug 19, 2005 1:48 am

When the entire solution gets checked out, does a dialog appear stating that the files should be removed from source code control?

not for me, mine says runs as normal when you close the xsd file, it then checks out the whole project. After that .NET says that the XSD file has changed outside of the editor and would I like to reload it. Saying No to this is usually best but in no way guarentee's the integrity.

Do you see a pattern when you are prompted to check out the entire solution?

Afraid not, although generally saying No to any kinda of reloading and/or checking out just ends up delaying the inevitable corruption.

When the other users perform a "get latest" and it doesn't work correctly, does the problem only happen when the entire solution has been checked out by you?

I guess so because Vault automatically checks out the project to me whenever I change the XSD

The "solution" I have found is just to exclude it from Vault this stops any corruption and all the problems....however....I dont know what will happen when I finalise the project so its not ideal.

Mad Eddie · Post by **Mad Eddie** » Fri Aug 19, 2005 5:50 am

Scratch that...just lost it all again...

it asked to check out the project again and even though I had set the xsd file to be excluded from Vault it removed it. I am guessing that for whatever reason VB is removing it when it changes the project file.....nightmare

Post by **Tonya** » Mon Aug 22, 2005 10:18 am

Thanks for letting me know this. I was able to reproduce the problem here. I think it's related to the fact that there are three files associated with Data Set file types and I don't think that Vault is excluding all of them from source code control. I have also logged this as a bug.

Are you loosing all of your changes when the project files are being checked out? What exactly do you lose?

Tonya Nunn
SourceGear Support

Post by **Tonya** » Mon Aug 22, 2005 10:52 am

I should have clarified this in my previous posting but this bug is also reproduceable using Visual SourceSafe. It is very likely that it's a bug from within VS.Net and that we may not be able to do anything about.

Tonya Nunn
SourceGear Support

Mad Eddie · Post by **Mad Eddie** » Tue Aug 23, 2005 4:38 am

When the XSD file is created I use it as a typed dataset....I then databind it to numerous textboxes etc on forms. When the XSD file is lost/removed it takes with it all those bindings and also leaves some references within the form which need to be manually found and removed.

I currently check out the entire project and then check back in everything I don't need. It seems that as long as you have the vbproj file checked out everything is ok

*touches wood*