6

I am attempting to create a Coded UI Test in a Visual Studio 2010 test project.
I right click on the project, Select Add Select Coded UI Test

I then get the error warning:

The following package failed to load: C:\Users[File Path Goes Here]\Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll. Coded UI Test is now in an inconsistent state. Remove this package and restart Visual Studio to work with Coded UI Test.

Once I click OK, I can create the Coded UI Test (CUIT) but when the test is over, the test file is empty.

Does anyone know how to fix this problem? I've already deleted my settings, AND reinstalled VS 2010, all to no avail.

Thanks everyone.

Improve this question
2
  • It sounds to me like perhaps your UI Test module got corrupted? You might consider uninstalling it, closing VS, deleting all the cache (from your AppSettings as well), the re-installing. Commented Nov 5, 2011 at 7:33
  • I have reinstalled, as well as done a repair install. I have not deleted the cache though. Commented Nov 5, 2011 at 12:48

3 Answers 3

Reset to default
3

No idea about the source of the problem, but if you go to C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\ and copy the Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll file into the bin/debug directory everything works fine.

I don't know why VS assumes that the .dll is there when it's not, but that is the fix.

Improve this answer
Sign up to request clarification or add additional context in comments.

18 Comments

I now find that the above solution only works once. Does anyone else have any ideas?
Is that dll referenced from the project?
If yes, try removing the reference. Also, do you have any other Visual Studio installs to tests that?
And, well, is that problem reproduced when you create a project from scratch?
I have removed the reference, and I still get the same error - I have also created several projects from scratch and I still get the same error.
|
3

So, I'm prepared to declare this a massive bug on Microsoft's part, and closing it out.

Improve this answer

3 Comments

And if you don't have MVC 3 scaffolding installed, everything goes smoothly?
If yes, you could add this workaround to the question to clarify what to do with it.
Uninstalling the mvc scaffolding NuGet package really does fix the problem, that's all it takes. It makes absolutely no sense, but that's all it takes.
2

I was able to get past this issue by changing the 'Copy Local' property of the referenced DLL to 'true'. After this change the DLL is automatically copied into the Bin\Debug directory.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.