I had the same problem on Win7. What worked for me is what @Andre suggested in the comment: Right-Click->Properties on cl.exe in your VS install directory (the exact path appears in the CMake error); Choose the Compatibility Tab; Check “Run this program as administrator” in the “Privilege Level” box.
No, there is no way of having nested comments in XAML. You could use the mc:Ignorable attribute on your root element, and any attribute or element prefixed with that value will be ignored E.g: <UserControl … mc:Ignorable=”i”> <!– Ignore Text attribute –> <TextBlock i:Text=”Hello” /> <!– Ignore entire button –> <i:Button> </i:Button> </UserControl> Note that … Read more
Go to the project menu -> properties. Select the resources tab Make sure Images is selected first. Click the arrow beside ‘add resource’ New Image (Select from Image File Types) Find the PNG
From Arian Kulp’s site, the way to change the default startup project for a solution is to edit the .sln file. You’ll see some Project and EndProject lines. The first Project listed will be the default startup project, so just move the one you want to the top.
No but you can add an external tool. Go to Tools | External Tools… and click Add Title: xUnit Test Command: xunit.console.exe (set to full path to console test runner) Arguments: $(BinDir)$(TargetName)$(TargetExt) Initial directory: $(BinDir) Click Use Output Window Click OK. This adds the xUnit Test command to the Tools menu. You can then create … Read more
You may be interested in reading this NuGet doc: Using NuGet without committing packages to source control
It is because you copied the .pdb files as well as the executables. The CLR will look for them when it generates a stack trace to try to give as much info as possible about the stack frames in the trace. The .pdb stores the source file name and line number. You are supposed to … Read more
Yes: disable Tools\Options\Text Editor\your language here\Enable single click URL navigation to turn off the ‘helpful’ feature.
There’s another similar question here on Stack Overflow, where I posted my answer with what worked for me. I can set breakpoints and start NUnit directly from Visual Studio 2010 with Debug -> Start New Instance (which I think is your goal). I set nunit.exe as the external program in project -> Properties -> Debugging … Read more