Build failing in Visual Studio 2013 Community

[aframe]

Build failing in Visual Studio 2013 Community

[Thwaitesy]

I would imaging its due to CodedUI test functionality. You can unload the desktop stuff if you dont need it and it will work happily.

[fAntel]

Hello. I have the same issue with Visual Studio 2015 Professional. But I need CodedUI. About problem. Compiler say that it cannot find Microsoft.VisualStudio.TestTools.UITest.Extension version 12.0... I don't know why Visual Studio want assemblies exactly this version.
Then I downloaded code and tried to recompile. But compiler say that it cannot find Coded UI classes and that I forgot add references. But all references was added. Only version 14 but not 12 because I use Visual Studio 2015.
Can you explain how can I recompile project or what is wrong I am doing?

[hriosm]

Hi Anton, I could not. When I could compile some part, I’d get a problem some other place. Some months ago, I read there was a problem with last Selenium version and had to use some previous version. I changed to Python + Linux without problems. Regards From: Anton Kovalyov Sent: Tuesday, September 01, 2015 2:49 PM To: AFrame/aframe Cc: HRIOS Subject: Re: [aframe] Build failing in Visual Studio 2013 Community (#13) Hello. I have the same issue with Visual Studio 2015 Professional. But I need CodedUI. About problem. Compiler say that it cannot find Microsoft.VisualStudio.TestTools.UITest.Extension version 12.0... I don't know why Visual Studio want assemblies exactly this version. Then I downloaded code and tried to recompile. But compiler say that it cannot find Coded UI classes and that I forgot add references. But all references was added. Only version 14 but not 12 because I use Visual Studio 2015. Can you explain how can I recompile project or what is wrong I am doing? — Reply to this email directly or view it on GitHub.

[Thwaitesy]

We have seen this issue before with VS 2013 Test Professional. Only certain versions of VS allow for the full functionality of CodedUI.

Our work around was this:

• Make the project be a general test project and not a "CodedUI" project - With the CodedUI projects you will notice the .csproj will pull in the references to CodedUI automatically and in the case where your version doesn't allow for CodedUI it will not load the project at all. So make it be a generic test project and you elevate this issue.
• Add a "Libs" (or something similar) folder somewhere relative to your project in the same source code repository and drop in the 3-4 .dll's required for CodedUI.
• Add a direct reference to those dll's in your test project. (Not from the public assemblies located on your pc)

That should allow the project to load on VS open, and also allow it to work when running tests as the dll's are there.

P.S - I assume this method might breach some terms and conditions with Microsoft as you are getting around their licencing restrictions. For us, we had to do it as a stop gap measure for some users that were waiting for their licences to come through.

I take no responsibility for any issues with Microsoft or anyone else that arise from using the above workaround.