24. April 2013 06:30 by Rick Glos
I’ve got a bunch of unit tests that were in an existing VS2010 project that worked great. They had an AssemblyInitialize method that dropped and recreated the database and used Microsoft.SqlServer.Smo to run scripts.
When I upgraded this solution to VS2012 the unit tests would no longer execute and I was receiving the following error:
System.IO.FileLoadException: Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.. Aborting test execution.
I can’t very well change how Microsoft.SqlServer.Smo is compiled.
Googling around I didn’t find much but eventually ran across a comment buried in StackOverflow question about hand editing the VS2012 test runner.
The solution is to open the config file at C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.executionengine.x86.exe.config and add the following:
<startup useLegacyV2RuntimeActivationPolicy="true"><supportedRuntime version="v4.0"/></startup>
Note that I had to restart VS2012 to unload the exe and reload it. You can see it running as a child process of VS2012 in Process Explorer.
Hope that helps someone else.
15. April 2013 13:13 by Rick Glos
In attempting to install some VPN software to connect to a client I received a ambiguous message from the installer.
Unable to manage networking component. Operating system corruption bay be preventing installation.
Some googling turned up a good post about Windows 7 being limited to 14 network filter drivers but is set by default to only 8 (post) along with a link to technet forums (post).
Although the post was on Cisco forums, and I was installing some SonicWALL software, I assumed SonicWALL was just a re-branding of the Cisco installer. In addition I have a number of what I think would be ‘network filter driver’ software like Windows Virtual PC’s, VirtualBox, Network Monitor, and other client VPN connection tools.
To increase the network filters to allow the software into install, modify your registry key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters and change the value from 8 to 14.
This did not require a reboot.