ExpectedExceptionBaseAttribute in VS2012 - unit-testing

I ran into an issue this morning after upgrading to Visual Studio 2012.
Specifically, I have a class that extends ExpectedExceptionBaseAttribute. The test passes in Visual Studio 2010 but fails in 2012.
The issue on Microsoft Connect is here which has been closed as "by design" but in my opinion, this is a bug. Whilst there is a resolution provided by Microsoft, it requires me to force the new version of MSTest into a legacy mode.
I have not included sample code here because there is a small sample project available for download on the Connect issue.
If, as they state in the comments, the new version of MSTest is leaner and more performant, then I want to use it without putting it into a legacy mode.
So the question is how do get it to work without resorting to that?

This appears to be fixed in VS2012 Update 3.

Related

Using Visual Studio 2017/2019 to run VS 2008 C++ project

I wonder if anybody has experience converting VS 2008 C++ solution to VS 2017/19 without switching to newer SDK and toolset. The solution is quite old, very large, uses 3-rd party libraries, so full conversion is out of the question. The goal is only to switch to better user interface.
Theoretically it is probably possible, although I successfully converted only very basic C++ MFC project.
Project settings in VS 2017 show only latest toolset. To make other toolsets to appear, I had to install VS 2010, and also add SDK 8.1 from VS installer (without VS 2010, this option is not available). Then select toolset v.90 and SDK 8.1 for each project in solution.
At this point, simple converted project works fine. A large legacy solution has a lots of issues. I resolved generic ones, but it looks like uphill battle. For example, C++ directories are physically different and some of the files are missing. It may be possible to eventually assign original VS 2008 directories to each project and/or copy missing files, but I have the impression of doing something illegal.
The question is, is it a valid procedure and still possible after latest updates.
Thanks==

Debugging with Resharper 9 and Visual Studio 2013

I use the newest build of Resharper (9.3) and Resharper C++ with Visual Studio 2013.
Code editing, refactoring, ... works great. But if I try to debug the code, I get a weird error:
an empty window with "Source not available. The current thread is not currently running code or the call stack could not be obtained".
which makes debugging quite difficult.
I think the problem is related to Resharper, because this problem did not occur before I installed Resharper nor does the problem occur if Resharper is disabled.
Is there a solution for this problem or another tool with similar capabilities that can be used instead?
Latest version is 9.2 and the bug should be reported to jetbrains

Building Emscripten Project with an IDE?

I've recently discovered Emscripten as a way of writing native code and running it in a web browser.
I'd like to work with an IDE for code completion and be able to customize the build process for Emscripten.
The only tool I've found to build Emscripten this way is with VS2010 which has very limited c++11 support so that's not desirable.
I thought of using VS2013 and writing a custom build script but I've never used VS so I'm unsure how to do that or if it's even possible.
What are people using to work with Emscripten?
Not sure if you are aware of this. On the requirements page, the following is stated:
Visual Studio 2010 is required! Visual Studio 2012 and Visual Studio 2013 do not correctly compile Fastcomp. This issue will be fixed (eventually) when Fastcomp is migrated to use a LLVM 3.4 or later.

Test generation in Visual Studio 2012

Visual Studio 2010 had a feature with which it was possible to generate a test method for each public method or property of a class. Even I know that the result was more or less use less, I was wondering if this feature still exists in VS2012 because I didn't find it.
This feature has been removed from VS 2012.
Try this plugin:
http://blogs.msdn.com/b/willy-peter_schaub/archive/2013/06/13/announcing-the-unit-test-generator-visual-studio-extension-beta.aspx
I miss the option to configure the structure in which it creates tests but besides that it works fine.

Is the MSTestExtensions project compatible with VS2010?

We've been using VS2008 and soon will be upgrading to VS2010. I have been using MSTestExtensions for it's database rollback feature for integration tests via MSTest. It seems the open source project has not been having much contribution in the last 2-3 years. Thus, I was curious if anyone has tried to use it with VS2010. Does it still work?
Seeing that you can download the source code to the MSTestExtensions project, it might be worth getting the source and building it in VS 2010. Since the MSTest functionality in VS 2010 has not changed that much since VS 2008 (from what I've read), I would say you have a good possibility of getting the code to build. The resulting binaries could be used for your VS 2010 development (hopefully! :)
I can now verify that the 2008 MSTestExtensions dll does indeed work with Visual Studio 2010.
The only thing is it didn't show up in the list of .net references so I had to manually browse to where it was installed. In my case that was to C:\Windows\assembly\GAC_MSIL\MSTestExtensions. Just add a reference to the version 2.0 dll (VS 2008 version) and it will work as expected.