VS 2010 powertools installation helped to use PEX & Moles in VS 2010.
Now with VS 2012, I understand that Moles becomes enriched as Fakes but hopefully PEX is retained, please confirm.
Also, how to use PEX in 2012. What needs to be installed (like VS 2010 powertool) to get that working for 2012.
Thanks !!
As far as I know, they are waiting for a final version of Visual Studio 2012 to release a version of Pex compatible with it.
I can't understand why Microsoft doesn't make this things clear... :/
Below are the comments from http://visualstudiogallery.msdn.microsoft.com/fb5badda-4ea3-4314-a723-a1975cbdabb4
Pex for Visual Studio 2012 2 Posts | Last Post April 23, 2013
Written April 23, 2013
Flynn Hi, I am wondering: There is PEX for Visual Studio 2010, there is Code Digger for Visual Studio 2012 and portable libraries but
there
is nothing for Visual Studio 2012 and all the the other library
formats. Why is that?
Written April 23, 2013 Nikolai Tillmann Code Digger (for Portable
Class Libraries) is the first Visual Studio extension from the Pex
Team for Visual Studio 2012. Stay tuned for future extensions that
bring more aspects of the rich experience of the Pex Visual Studio
2010 Power Tools to the latest version of Visual Studio. If you are
looking for a particular Pex feature for Visual Studio 2012, drop as
an email at pexdata#microsoft.com.*
Looks like they introduced Code Digger.
From the PEX webpage:
Code Digger for Visual Studio 2012 is a lightweight version of Pex that allows you to explore public .NET methods in Portable Class Libraries directly from the code editor.
As far as I have read from Microsofts documentation PEX for Visual Studio 2012 is now an integral part called "Fakes and Moles", please look here:
http://research.microsoft.com/en-us/projects/pex/
And here:
http://msdn.microsoft.com/en-us/library/hh549175.aspx
You can continue to use PEX for test generation by opening your solution(s) in VS 2010 , even if you are normally working inside VS 2012. VS project schema is very compatible between VS 2010 and VS 2012.
You also could consider to run command line PEX from 2010 add-in. See the answer in Create NUnit test cases automatically from Pex. read more about this in Exercise 5 of Parameterized Unit Testing with Microsoft Pex
According to This Webcast
Code Digger was released so that people can see the power of PEX when used properly before they release the Visual Studio 2012 version where people pick it apart for not working with platform specific cases.
They don't speak of a release date but since Visual Studio 2013 is now RTM you'd think that it would be soon. I definitely miss PEX as it helped with Parameterized Unit Testing.
Related
I've ported my project from vs 2015 to vs 2013.
The Library i'm consuming is also built from vs 2015.
LNK1104 cannot open file 'legacy_stdio_definitions.lib'
What this error is all about?
You shouldn't need legacy_stdio_definitions.lib for programs built with Visual Studio 2013 or earlier versions. Just remove the library. The functions in this library are provided in other Visual Studio 2013 (and earlier) libraries.
Here is a description of why this library is sometimes needed for programs built with Visual Studio 2015 and later.
I was working on a project in VS 2017(trial) but now i have to work on VS 2012 instead due to company policy. The problem is that now the components in the design are errored out(Error creating control) and i can't proceed any further. Any suggestions on how to make it work in 2012?
Maybe this solution will be able to help you. Seems like a similar issue although it is for a previous version of Visual Studio.
How to downgrade from Visual Studio 2012 project to Visual Studio 2008
I have Visual Studio Professional 2017, and the project I'm using requires Common Tools for Visual C++, which I don't have installed.
However, I can't find it on the Visual Studio 2017 installer nor the Microsoft official website. Any suggestions?
Get the VS 2017 installer here. You can get the "Trial" versions of Professional or Enterprise and then upgrade them to full versions with your license key.
And get other VS installers here.
As Chuck Walbourn said, Common Tools for Visual C++ does not exist for Visual Studio 2017. The component that I was missing was Common Tools for Visual C++ 2015.
I would like to make a template for F# lib + XNA 4.0 + Xbox360 for visual studio 2012.
All I have is Visual Studio 2012 Express Edition for Web.
When I try to install the Visual Studio 2012 SDK, it stops after reporting that it requires Visual Studio 2012. The log seems to indicate it's looking for the Professional edition.
I'm not interested in buying a professional license for hobby work, and I am a bit surprised Microsoft would want to prevent hobbyists from extending their product.
I do have a professional license for Visual Studio 2010, though. If there's a way to make extensions for 2012 using 2010, that would work for me.
You can use VS2010 to develop extension compatible with VS2012.
All you have to do is to manually change vsixmanifest to make it work with newer version:
<SupportedProducts>
<VisualStudio Version="11.0">
Note however that Visual Studio Express does not support extensions, so you won't be able to install it in VS2012 Express anyway.
Does VS 2012 come with SL 5?, if it doesn't, what can I do?, I guess the tools installed for VS 2010 don't work with VS 2012.
If I don't uninstall VS 2010, will Silverlight 5 work in VS 2012 without doing anything?
According to MS SilverLight Forums.
does anyone know if Silverlight 5 Tools for Visual Studio is
compatible with visual studio 2012 rc? i haven't found a vs2012
specific version.
With this answer
Hi,
You don't need that. You can create Silverlight projects directly in
Visual Studio 2012 RC. For more Visual Studio 2012 RC compatibility
issues please refer to:
http://msdn.microsoft.com/en-us/library/hh266747(v=vs.110).aspx
Sincerely, Allen Chen Microsoft Online Community Support
Please remember to mark the replies as answers if they help and unmark
them if they provide no help.
So I assume that it's also true for the RTM release.