|
|
Rank: Member
Joined: 10/5/2008
Posts: 10
Location: Virginia, USA
|
If this is a repost I apologize, I submitted this before and was kicked out to the support help page...guess when your session expires they just abandon you...
So we're all on the same page; this solution that now has a problem has been working fine for months. No other changes were made to the solution when this issue cropped up other than adding new unit tests and code (no other new projects were added).
In our solution, we using MSTest (the testing tool that comes with Visual Studio) and our test editor has several test lists for organizing those tests.
On the day we re-opened Visual Studio after adding our existing UModel project to the solution we started getting this weird error whenever we opened the test list from Visual Studio: "The parameter cannot be null or empty. Parameter name: filename" and we get a duplicate VSMDI file (the file that holds the test lists) created.
Now I know this sounds like a Visual Studio MSTest bug (and given how many things were broke in 2008 that worked in 2005, I don't blame anyone who thinks that), but the fact that this showed up right after adding UModel to the solution has got me wondering if there's some sort of hook UModel has made into the IDE that has caused this.
So I removed the UModel project from the solution and the problem went away.
I tried to recreate in another solution and had no problems of course, so I'm just simply asking has anyone ever had some sort of weird IDE bug after adding an existing UModel project? Like I said, I'm willing to bet it's Visual Studio; but I got to ask to satisfy my curiosity.
Thanks much!
|
|
Rank: Advanced Member
Joined: 9/28/2005
Posts: 371
Location: Vienna
|
Hi boo!
We are not aware of any problems in that direction.
Additionally we have made some tests now with MSTest + UModel projectfiles and could not detect any problems.
Maybe you can send a (small) sample to our support center that we can reproduce your curiosity?
|
|
Rank: Newbie
Joined: 9/17/2009
Posts: 4
Location: Eagan, MN
|
I can confirm that this is indeed a bug that is somehow tied to UModel.
In our case we migrated a class library project and it's associated unit test and UModel project into a separate dedicated solution.
Upon doing so our unit test lists disappeared from the list editor window though the associated vsmdi files remained. I attempted to recreate them. Upon clicking "ok" to create the test list I would receive the same "The parameter cannot be null or empty. Parameter name: filename" alert dialog. The vsmdi file would be created and the test list was added to the editor window where it could be worked with. Opening and closing the solution however, would result in the test list editor losing the test lists. Repeating the process yielded the same results.
By removing the UModel project I was able to successfully recreate the test lists without incident. I then added the UModel project back into the solution. Creating subsequent test lists also worked without incident.
System:
* Vista SP2
* Visual Studio Team System 2008 v9.0.30729.4108
* .NET v3.5 SP1
|
|
Rank: Advanced Member
Joined: 9/28/2005
Posts: 371
Location: Vienna
|
Hello Dion!
What do you mean with Quote:In our case we migrated a class library project and it's associated unit test and UModel project into a separate dedicated solution. ?
Did you remove those projects from one solution, create a new, empty second solution and used "Add|Existing Project..." to add those projects?
Quote:I attempted to recreate them. Upon clicking "ok" to create the test
How did you try to recreate them?
I played around with Test Lists and got no problem. Maybe you can send a short sample to our support center, that we can reproduce it?
PS: When I understand correctly, now everything is working for you again!?
|
|
Rank: Newbie
Joined: 9/17/2009
Posts: 4
Location: Eagan, MN
|
Quote:Did you remove those projects from one solution, create a new, empty second solution and used "Add|Existing Project..." to add those projects?
Yes.
Quote:How did you try to recreate them?
There (thankfully) weren't many tests nor test lists so I did this manually through the VS Test List Editor. I recreated them by right clicking on the "Lists of Tests" item in the Test List Editor and selecting "New Test List..." from the context menu.
Quote:Maybe you can send a short sample to our support center, that we can reproduce it?
I regret that I did not preserve the project/solution files from when things were in their malfunctioning state. I can state that there was nothing unusual or special about the projects/solutions/test lists. Everything was quite ordinary. The new solution consisted of one .NET v2.0 library project, one .NET v3.5 Visual Studio unit test project, one UModel 2009 project. The original and the new Visual Studio solutions reside in different locations on the file system. The project names remained the same. UModel did not appear to have any problems updating the model to reflect the file system changes.
Quote:PS: When I understand correctly, now everything is working for you again!?
Correct. By removing the UModel project whatever the problem was, it was allowed to be reset/corrected so that test lists could be created and saved without problem. Adding the UModel project back into the solution did not alter the correct functioning of Test List Editor.
|
|
Rank: Advanced Member
Joined: 9/28/2005
Posts: 371
Location: Vienna
|
Hi Dion!
Once you have this problem again, please send us the project that we can look into this and fix it or try to find a workaround if the problem is MSTest related.
As I wrote above, we also tested with test lists but could not find any problem.
Sorry for the inconvenience.
|
|
Rank: Advanced Member
Joined: 9/28/2005
Posts: 371
Location: Vienna
|
just for info:
we found and fixed a possible problem when adding project items to a solution in VS.NET.
Maybe also your problem is fixed with this - anyway a sample to reproduce yours would be helpful to be sure.
Thanks and sorry for the inconvenience.
|
|
|
guest |
