Assertion Failed exception

tommyg · Post by **tommyg** » Mon Aug 20, 2007 8:16 pm

When attempting to add a new website solution to the Vault, we are getting the following message;

SourceGearLLC.VaultVsipClient.VsipUtility+AssertionFailedException

This happens immediately you right-mouse on the solution and select 'Add Solution to Vault' and then log into the Vault.

We are currently using Vault 4.0.4, with the VS2005 Client.

We have a number of solutions this is happening with, does anybody have any ideas what this might be caused by?

Cheers
Tom

tommyg · Post by **tommyg** » Mon Aug 20, 2007 10:36 pm

Further to this,

I have found that if the Solution (.sln) file is saved into a folder that is not the same as the website, then I do not get the Assertion Failure message, however as soon as I save the solution in the same folder as the website, then the error returns.

Hope this helps

Tom

ian_sg · Post by **ian_sg** » Tue Aug 21, 2007 6:53 am

Tommy,

This is a known issue when a solution contains a web site and the solution file is in the web site's folder on disk. The reason this happens is that Visual Studio writes a strange path for the web site in this scenario, using three dots in the path. The only workaround at this time is to not have the solution organized this way or to use the MSSCCI (VS2003-compatible) client for these solutions.

tommyg · Post by **tommyg** » Wed Aug 22, 2007 10:22 pm

I don't think the three dots causes the issue, as even when the solution is stored in another folder the 3 dots are still in the solution, yet there is no issue adding the solution to the vault.

in fact the only change to the .sln file is the path to the project changes from . to PROJ\

Could the issue be that the '\' is not being added to this when it is being parsed?

Regards
Tom

ian_sg · Post by **ian_sg** » Thu Aug 23, 2007 7:13 am

That could be. I was recalling from memory that when we first discovered this bug, we noticed the weird path with three dots. In either case, this is a known issue that will be fixed, and the current workarounds are in my previous post.

tommyg · Post by **tommyg** » Tue Aug 28, 2007 9:23 pm

Will this be addressed in the next release do you think of Vault? And if so, is there any timeframe on the next release?

Cheers
Tom

ian_sg · Post by **ian_sg** » Wed Aug 29, 2007 2:22 pm

It's on the list of things we hope to include in the next release, but I can't say with certainty yet.