Specify a default solution when debugging with the experimental instance - visual-studio-2012

When working with Visual Studio Extensions and debugging using the experimental instance, is it possible to have the experimental instance automatically load a solution?
I did not see options, but may have been looking in the wrong place

Just right click on your project in Solution Explorer and hit properties. Debug tab. You'll see "command line arguments" as a box, which should contain "/rootsuffix Exp". These arguments are what are used to launch devenv.exe (the Visual Studio process). If you just add the full path to your solution after what is already there (quote if necessary), that should work just fine. It's really no different than doing devenv.exe from the command line.

Related

Extend Visual Studio functionality for Installshield ISPROJ Project type

InstallShield must be the crappiest "industry standard" application in existence, for reasons too numerous to enumerate here. However, one of those deficiencies is something I'd like to be able to fix, and with my first foray into writing an extension for Visual Studio (currently using 2015 version).
InstallShield has created a .isproj type, to allow integration with Visual Studio. This allows a developer to create an installer that references the output of a project as the files to include in the installer (rather than having to manually select individual files to include). This works well enough as long as the .isproj is being built in Visual Studio, and in a solution that references the project for which you need the output.
However, I also have an automated build for my installer projects, that we run on a build server using MSBuild. When attempting to build this way, we were getting completely opaque error messages indicating that the project output references above couldn't be resolved.
As with all InstallShield errors, Googling for answers turned up nothing except for multitudes of other people having the same problem. So I decided to dig into the plain text of the .isproj to see what I could find.
As it turns out, the .isproj type is a just a regular MSBuild script, and it even has lines commented out that explain options that can be added to the project; one of those things that can be added is an ItemGroup containing ProjectReference nodes. Manually adding the nodes helped solve the problem. Command-line build now works.
However, I am dissatisfied with a) having to manually type this stuff in, b) having no visual representation of what projects are being referenced, and c) not finding out about a problem until the build fails. So, I would like to be able to extend Visual Studio to help me with this. Here's what I'd like to do:
1) Add a "References" node to the project in Solution Explorer that acts like the References node for any normal .csproj.
2) Restrict the available References to other projects in the the current solution.
3) Visually represent a project with missing references (e.g. by underlining the project name with a colored squiggly, as with errors/warnings), and potentially failing the build if missing (depending on whether I want to treat it as an error or a warning; TBD).
To these ends, I've downloaded MPF for Projects - Visual Studio 2013, which provides an SDK for creating a new project type.
However, before digging too deeply, I need to know if it's even possible to EXTEND an existing project type, as described above, as I obviously don't have InstallShield source code. Also, any links or guidance as to a starting point for doing so would be greatly appreciated.

Eclipse shortcuts in Resharper

I just started with Visual Studio + Resharper, coming from Java development with Eclipse. I can navigate eclipse pretty quickly, because I memorized all the shortcuts I need. Now it seems like Resharper knows all what eclipse can do (probably even more), but its mapped to different keys, and i really don't feel like learning a new set of shortcuts for the same stuff.
So my question:
Where is Resharpers shortcut configuration file (if there is any)? I saw a bunch of .xml files in it's bin directory, but I'm not sure it's the right place to look. Couldn't find anything in the docs, only how to change the shortcuts from VS one-by-one.
Is there an eclipse preset? I found this on github, but there is absolutely no explanation, on what to do with it, and in the file name it states, it's for r# 5.0 and i have 8.1 (not sure if there is any difference in the configuration part).
I found this file using Google Search: https://github.com/chrismo/jetbrains.keymaps/blob/master/resharper.5.0.eclipse.shortcuts.vs2010.vssettings
You can download it and use Visual Studio's Tools -> Import and Export Settings ... command to import it.
Resharper comes with only two default keyboard schemes, 'Visual Studio' or 'IntelliJ IDEA' (see here). Choose one that you are most happy with (under Resharper->Options...->Environment->Keyboard & Menus) and change any shortcuts in Visual Studio (under Tools->Options...->Environment->Keyboard) to match the ones in Eclipse. It may be easier just to re-learn one of the default schemes though.

Visual Studio 2013 Edit and Continue not working

With VS2013 Pro I am not able to use "Edit and Continue" when debugging an MFC program. I created a new MFC project to test.
OS is Windows 7 64-bit and I'm running Visual Studio 2013 12.0.30110.00 Update1.
Under Tools->Options->Debugging->Edit and Continue I have Enable Edit and Continue checked. I have unchecked it and checked it, but whenever I modify the code while debugging I get the following message:
The source file has changed. It no longer matches the version of the file used to build the application being debugged.
Basically I haven't changed any settings except for the tab sizes and I've set the keyboard mapping scheme to VC6.
What setting am I missing to enable edit and continue?
Edit and Continue is disabled for native code by default. To enable:
On the Tools menu, click Options.
In the Options dialog box, open the Debugging node, and select the Edit and Continue category.
In the Native-only options group, select Enable native Edit and Continue
Edit:
Steps to test native Edit and Continue is working:
Start VS 2013
Create a new MFC project:
FILE->New Project->MFC Application->OK.
Select Finish on the MFC Application Wizard.
Build and start debugging:
BUILD->Build Solution
DEBUG->Start Debugging
Break into the program:
DEBUG->Break all
Make a code change:
Open OutputWnd.cpp and find COutputWnd::OnSize (Line 80)
Insert this line at the start of the function: cx = cx / 2;
Continue execution:
DEBUG->Continue
Resize the application window to see the effect of the code change on the Output pane at the bottom. Its width should be half the required size.
Edit and continue is also a Setting for each project.
It must be set in the compiler options under C++ -> General -> Debug Information Format: "Program Database for Edit And Continue (/ZI)"
Also the linker settings must be changed. The linker has to use incremental linking. Linker -> General -> Enable Incremental Linking = Yes or (for VC 2012 users) C++ -> All Options -> Enable Function-Level Linking = Yes (/Gy)
For more information read the MSDN.
The last hint helped, but we had to
set "Image Has Safe exception handlers" = NO(/SAFESEH:NO)
in all projects of our solution!
I did all steps described above, but nothing helps (thanks all for it).
My solution was:
Project -> Properties -> Linker -> Advanced:
set
"Image Has Safe exception handlers" = NO(/SAFESEH:NO)
Apply, Ok, and Rebuild project.
Hope it helps.
For what it's worth I've been pulling my hair out on this one as well. I finally got edit and continue working by changing the following setting:
Project > Properties > Linker > All Options > "image has safe exception handlers".
It was set to No (/SAFESEH:NO). I went in and deleted it. I didn't set it to YES, or NO. I simply kept it blank. I would love to know what it means to be blank. But edit and continue is now working for me. Maybe it will help for you.
A project with a "Release Configuration" will disable Edit and Continue.
To change this
Open "Configuration Manager"
Change Configuration for the project from Release to Debug
Rebuild and debug project
Edit and Continue will also not work if your project's Platform Toolset is set to Visual Studio 2012 (v110), instead of the usual Visual Studio 2013 (v120).
This setting is in Project > Configuration Properties > General > Platform Toolset.
The solution of this problem is on the Microsoft Documentation...
If IntelliTrace is enabled and you collect both IntelliTrace events and call information, Edit and Continue is disabled.
On Visual studios' menu go on Tools>>options - Select "IntelliTrace" tab and let IntelliTrace events only checked.. Save, restart the visual studio and.......
Your Edit and Continue will work again!

Syntax highlight fail on Classes in Visual Studio 2012

I recently installed Visual Studio on a laptop and the syntax highlight fails to change Classes colors.
I tried exporting and importing the full, complete set of settings and it is still looking like that.
EDIT
I tried those websites with schemes and decided to try one, the Humane scheme, and this is how the sample code looks in my laptop after installing those settings:
However, this is how it is supposed to look:
Note the lack of highlight in class names.
What could it be causing this?
I'm starting to think that's another setting at another place which causes this.
Finally, it worked by resetting user data, running this from the Visual Studio Command Prompt
devenv /Resetuserdata
Found the hint here:
https://stackoverflow.com/a/11988265/1213246
Changin syntax highlight could be done through the menu Tools - Options - Environment - Font & Colors. It's a try and test approach that is not much improved from earlier versions of Visual Studio.
Fortunately, today there are entire sites with themes that simply need to be choosen and installed
I suggest you to visit http://studiostyl.es/ where you can find thousands themes or, for more generic go to http://www.hanselman.com/blog/VisualStudioProgrammerThemesGallery.aspx

Ctrl + Dot (ShowSmartTag) not working in Visual Studio 2012

I'm now using the Visual Studio 2012, and now the keyboard shortcut for "ShowSmartTag", Ctrl + ., is not working. I googled a bit found someone said that CodeRush's Quick Nav shortcut is the same, so I disabled that command in CodeRush, but still I can not fix this. I also tried to disable all those suspicious extensions, but still no success. Any idea?
All keyboard shortcuts can be viewed from Tools > Options > Environment > Keyboard. What does your View.ShowSmartTag command say about current shortcuts?
If you try to assign CTRL + . to anything, it will tell you if the shortcut is used by something else...
In my case it was Web Essentials that caused this issue. I disabled it, and now all works well.
It's CodeRush that caused the issue and I uninstalled it, then SmartTag works again. My guess is that CodeRush replaced VS2012's built-in SmartTag entirely.
On my PC the problem occurs mostly when renaming a method or a parameter ...
To analyze this I have started a first VS 2012 instance without starting to edit the source code.
Then I have started a second instance of VS 2012 which must be attached to the first VS instance:
Debug->Attach to Process
Look for devenv.exe, Title = title of the VS main window
Select Managed and Native Code
Attach
Enable Break when exception occurs:
Debug->Exceptions
Enable C++ Exceptions, Common Language Runtime Exceptions
OK
Now as I started to edit a parameter name in the first VS instance, an error was thrown and the debugger in the second instance showed me an error in an memory Profiler Add-In.
After I have uninstalled the Add-in, the ShowSmartTag called by the keyboard works fine again.
I have the same problem with Ctrl + ., and I try this hotkey in anywhere of Visual Studio, but it is useless. My notebook is ThinkPad T430 made in Vietnam; I think this is an issue by the keyboard standard.
Maybe you should set another hotkey for "ShowSmartTag". For example, I removed the "NavigateTo" and added the Ctrl + + to "ShowSmartTag".

Resources