I installed Pex on my Windows 7 machine (Visual Studio 2010 Pex 0.94.51023.0 Power Tools (x64) - (English)). However, when I right click on a piece of code in VS2010, I don't see the "Run Pex" option. When I open another project using VS2008, it is visible. Any idea why it the option does not show up in VS2010?
Firstly, have you tried to reinstall Pex?
Otherwise, as experienced here, if Pex thinks that your project is a test project, e.g. because it references some unit testing framework or Microsoft.Pex.Framework, then Pex will only explore methods marked with the [PexMethod] attribute. Otherwise, Pex should allow the exploration of any public method. Is this possibly your problem?
Otherwise, if you are switching between VS 2008 and VS 2010, perhaps you are running into this problem.
Related
In Visual Studio 2015, when I attempt to debug a test that uses Typemock (and I use the Visual Studio Test Explorer, not Typemock's SmartRunner), on the first call to a Typemock method I get the following exception:
TypeMock.TypeMockException occurred HResult=-2146233088
Message=
*** Typemock Isolator is currently disabled. Enable using
the following:
Within Visual Studio:
Use Typemock Smart Runner
For other runners, Choose Typemock Menu and click "Integrate with Other Runners"
To run Typemock Isolator as part of an automated process you can:
run tests via TMockRunner.exe command line tool
use 'TypeMockStart' tasks for MSBuild or NAnt
I've followed the instructions and verified that:
Typemock is enabled
I already have "Enable Mocking integration" checked in the settings
Also,
The test runs properly when I choose "Run Selected Tests". I only get the exception when I choose "Debug Selected Tests"
Prior to Visual Studio 2015, I did not get this exception during debugging.
Question: What is causing this problem and how do I fix it?
The IntelliTrace functionality does not work with Typemock. Disabling IntelliTrace in the Visual Studio options (Options->IntelliTrace->General->Enable IntelliTrace) works around the issue.
See:
Typemock: Typemock Isolater is not currently enabled
Typemock: Debug Test on 64 bit machine
Typemock: On Windows 7 x64 with VS 2010
Disclaimer: I work at Typemock
This issue is fixed in Isolator 8.3 and will apply to all following versions.
Isolator 8.3 was released on 2.21.2016 and available for download at www.typemock.com.
I've created a C++ UWP Windows 10 app using Visual Studio 2015. However, I'm not able to visualize any xaml in the designer because I'm always getting a System.NullReferenceException error. How can I fix this?
That's very odd but I solved following these steps:
Close any instance of Visual Studio
Open Visual studio and create a new C# UWP empty project (name it as you like, do not matter)
Run the "useless" created project then close it as Visual Studio
Open again your previous C++ UWP project
In my case everything started working!
Switching solution platform to x86 worked for me.
I'm experiencing exactly the same problem on my primary development machine but not on another. The reason is... I think... When I installed Visual Studio 2015 on the 2nd machine, the first time I created a Universal Solution (C#) I was shown a dialog asking me to OK "elevated permissions" (custom permissions) for the VS2015 installation folder. I OK'd it and Designer works on that machine in both Blend2015 and VS2015 (community edition)
On the other machine I was never shown the dialog asking me to confirm elevated permissions and Designer does NOT work on that machine (VS2015 Enterprise). This machine also has VS2013 update 5) on it.
I am thinking that I might have to completely wipe off VS2015 and try to clean the registry of all VS2105 references AND remove the VS2015 installation directories on C:\ AND when I reinstall, create a installation directory with a different name (if I can). What a PAIN though... I'm waiting to see if MS delivers a simple solution since I'm quite positive that this whole issue boils down to a bug (feature... grrr) having to do with custom permissions that can't be changed (or added) after installation.
Would be nice is MS would confirm this...
(please note, none of this involved c++... it was all C#)
Tom
this is the dialog I was shown on the machine where Designer works]1
Installing the Windows Software Development Kit (SDK) for Windows 10 solved the issue for me. It may ask to unistall the previous version of Windows 10 RTM SDK
https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk
This is fixed in Update 1 of Visual Studio 2015
https://www.microsoft.com/en-us/download/details.aspx?id=49989
Is it possible to use FxCop for .NET 4.5 applications?
I am looking to use FxCop with the Visual Studio 2013 Professional edition.
Visual Studio 2013 Professional comes with Static Code Analysis (which is FxCop, just a fancy name for it).
In this link some information is provided:
As a developer, you can run code analysis on your project automatically or you can run it manually.
To run code analysis each time that you build a project, you select Enable Code Analysis on Build (defines CODE_ANALYSIS constant) on the project's Property Page. For more information, see How to: Enable and Disable Automatic Code Analysis for Managed Code.
To run code analysis manually on a project, on the Analyze menu, click Run Code Analysis on ProjectName. For more information, see How to: Enable and Disable Automatic Code Analysis for Managed Code.
This version runs perfectly on .NET 4.5.
FxCop 1.36 is a standalone version of Code Analysis. Microsoft no longer supports or works on the standalone version and currently only working on the integrated version that is included in Visual Studio.
There is a Uservoice going on which asks Microsoft to update the standalone FxCop version. See this link.
I made an application in Visual Studio 2012 using VB.net language.
I want to make a package or a setup so that any user whether they have visual studios or not can run my application.
I searched on internet and what I found is that there is something like statically or dynamically linking. Do these relate to my question?
Please give me a step by step method of packaging so that my application can run on Windows without needing Visual Studio or any other program to run it.
You will find it in the menu under Build -> Publish.
This will produce an executable that can be run without Visual Studio. The .NET Framework has to be installed on the computer though, but that usually is.
Hopefully this is a simple question and I have just overlooked something somewhere...
I am writing VB.NET stuff in VS2010 on Windows 7 64-bit. It seems to build by default for a 32-bit target, how to I tell it to make a 64-bit executable?
I went to the project properties -> Compiler -> Advanced, but don't see the option anywhere.
Oh, and this is VS2010 Express, to be clear.
This involves using the Configuration Manager, it's not a part of the project properties.
Go to the Build Menu, then click Configuration Manager. Under Active solution platform, click New, then add one with x64 as the platform. Use this platform to compile for x64.
It seems that you have to go to Build -> Configuration Manager and create a new solution platform from the Active Solution Platform dropdown and select x64 as the new platform. That will also change your Active Platform to x64 from x86.
Damn, but Visual Basic will never cease to surprise me! Or is this the Principle of Least Surprise, VB edition: VB will surprise you when you least expect it!