"Operation is invalid for the current state of the object."
Removing the web project from the solution doesn't immediately resolve the problem but by cleaning, rebuilding, and opening the solution from scratch unit tests will work again with only the class library.
Any suggestions?
Good luck with it and keep us all posted!
1: Create Class lib.
2: add test project
3: File/New/Web Site (leave as Filesystem, VB, ASP.Net)
Also
1: File/new/Web Site (leave as Filesystem, VB, ASP.Net)
2: add class library
3: add test project
Here are the exact steps I take to duplicate the issue:
1) Start VS 2005
2) File->New->Project->Visual Basic Class Library (check Add solution to source control)
[Source Control is SourceGear Vault 3.01]
3) Add a local variable and public property to class1.vb of type String
4) Right-Click Class->Create Unit Tests->New Visual Basic Test Project
5) Test->Windows->Test Manager->Run All Tests (works as expected)
6) Solution->Add->New Web Site
[Visual Basic, ASP.NET, File System]
7) Test->Windows->Test manager->Run All Tests (error diaglog box)
ERROR DIALOG: Operation is not valid due to the current state of the object.
A workaround (albeit not great) is to delete the .suo file in the solution directory.
I had a similar problem, running 2005 RC
I had a solution, with a
It worked fine for days, then all at once it seemed to throw that exception when I tried to run tests.
I rebuilt the solution, and that didn't fix it.
I closed the solution, removed the .suo file, and that fixed it.
Then I rebuilt, and the compiler found a syntax error it had missed before.
I fixed the error, rebuilt, and tests run fine.
Just made a discovery, Opening the design view in your aspx page, will cause the error. Close your aspx page, not sure how to close the design view. The error will not occur. Maybe there running on the same localhost, don't know. I noticed the error only shows up after i added coded, then realized it was only when i added code in the design view of my default.aspx page.
The unit test runs on some localhost port, there must be something in common with the design view running and the unittest running.
If this fails, then deletion of the sou file or just turning off VS2005 or the project will provide a temporary solution.
