tag:blogger.com,1999:blog-11096258.post114424015135342014..comments2024-03-26T09:29:25.252+01:00Comments on InfoWorker Solutions: VSMDI file - The weak spot of the VSTS test systemKjell-Sverre Jerijærvihttp://www.blogger.com/profile/13654217591841196465noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-11096258.post-6704836037991085302009-07-20T20:36:32.725+02:002009-07-20T20:36:32.725+02:00I think I have found a simple solution to this pro...I think I have found a simple solution to this problem.<br /><br />Do NOT put the .vsmdi file into source control.<br /><br />In my tests, anyway, it is rebuilt from stratch whenever I RUN the Unit Tests.<br /><br />-Jesse ChisholmUnknownhttps://www.blogger.com/profile/18065880067953920724noreply@blogger.comtag:blogger.com,1999:blog-11096258.post-15829151710268973342008-03-26T08:39:00.000+01:002008-03-26T08:39:00.000+01:00Thank you!We have been having a lot of problems wi...Thank you!<BR/><BR/>We have been having a lot of problems with those files. I am hoping this will work.<BR/><BR/>http://www.marcusoft.net/2008/03/how-to-get-rid-of-multiple-vsmdi-files.htmlAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-11096258.post-53275810652014663382007-04-15T22:32:00.000+02:002007-04-15T22:32:00.000+02:00Here is a work-around that seems to work - 1. Mak...Here is a work-around that seems to work - <BR/><BR/>1. Make sure Visual Studio is NOT set up to load the last-used solution file automatically (Tools -> Options, open Environment->Startup and make sure it does not say 'At startup: Load last loaded Solution'.<BR/><BR/>2. When you open a solution, make sure the Test View and Test Results windows are CLOSED. It seems that having these windows open when opening a solution causes the auto-checkout to occur.<BR/><BR/>3. Lastly, when you get the latest version of a solution, again make sure the Test View and Test Results windows are CLOSED. Same deal as above.paul [silentsanta]https://www.blogger.com/profile/09932209053681224867noreply@blogger.comtag:blogger.com,1999:blog-11096258.post-1159987212052586962006-10-04T20:40:00.000+02:002006-10-04T20:40:00.000+02:00Same here. We have several townsend test cases and...Same here. We have several townsend test cases and pretty large test lists hierachy and this is really frustrating. I've also posted the issue in the VSTF forum, but I have not seen a workaround or best practice so far... Thanks for the tip.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-11096258.post-1157640538955745452006-09-07T16:48:00.000+02:002006-09-07T16:48:00.000+02:00So we're not the only ones! Why aren't more folks ...So we're not the only ones! Why aren't more folks having problems with this? Perhaps they're just not complaining about it? I'd be curious if anyone has a workaround. I've posted to the MSDN Forums about this, so we'll see what happens.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-11096258.post-1149276881638642072006-06-02T21:34:00.000+02:002006-06-02T21:34:00.000+02:00Yes, we are experiencing this too. Our SCC provide...Yes, we are experiencing this too. Our SCC provider (PVCS, ugh!) does not allow multiple checkouts, so somehow we have been getting additional VSMDI files included in the solution. It would be nice to not have the option of having a local, non-source-controlled VSMDI file.Anonymousnoreply@blogger.com