Unable to use CUITe in VS2012

Oct 26, 2012 at 7:42 AM

Hi,

Version: VS Ultimate 2012

 I'm unable to use CUITe in VS2012. I'm getting related to Silverlight references error.. Anybody is working on this?

Thanks,

Palani

Coordinator
Oct 26, 2012 at 8:26 AM

Hi Palani,

Other users have discussed Visual Studio 2012 support:

http://cuite.codeplex.com/discussions/398942

http://cuite.codeplex.com/discussions/393727

http://cuite.codeplex.com/discussions/390516

Nov 2, 2012 at 9:43 AM

Hi

They stopped supporting UITesting for Silverlight application in VS2012.

http://msdn.microsoft.com/en-us/library/hh506981.aspx

Coordinator
Nov 2, 2012 at 7:57 PM

Visual Studio 2012's unofficial support for Coded UI testing for Silverlight 4 and 5 applications is available using an extension:

http://visualstudiogallery.msdn.microsoft.com/28312a61-9451-451a-990c-c9929b751eb4

"This plugin supports Silverlight 4 & 5 applications hosted in Internet Explorer versions 8, 9 & 10."

Nov 8, 2012 at 4:42 PM

Hi all, I too am having problems getting this to work with VS 2012 Ultimate.  I did install the Silverlight plugin and tried to compile the source but I cannot even get the setup project to load and it is looking for the 'Microsoft.VisualStudio.TestTools.UITesting.SilverlightControls' namespace and I cannot seem to find the dll that has this namespace anywhere on my machine.  Does anyone know where this might be?

Is there source for this that will compile using VS 2012?

Thanks

 

Coordinator
Nov 10, 2012 at 4:20 PM

The latest source code is not compatible with Visual Studio 2012.

According to the last link that was posted,

"You have to add a reference to Microsoft.VisualStudio.TestTools.UITest.Extension.Silverlight in your Coded UI Test Project. This assembly can be found in %Program Files%\Common Files\Microsoft Shared\VSTT\11.0\UITestExtensionPackages".

So basically you have to replace "Microsoft.VisualStudio.TestTools.UITesting.SilverlightControls" with "Microsoft.VisualStudio.TestTools.UITest.Extension.Silverlight".

Coordinator
Jan 21, 2013 at 9:44 AM

See work item 1089.

I provided a fix as part of changeset 23703.

Thank you.