Keybinding conflict between VS 2017 Preview and Stable - visual-studio-2017

I have VS 2017 stable and preview installed side by side. Resharper is configured only for the preview and not for the stable. However this causes issues with keybindings applied in preview for resharper shortcuts not mapping correctly on stable.
e.g. I have mapped ctrl+T for Resharper goto in VS preview. I expected that stable will have ctrl+T pointing to VS default Goto All since resharper is not configured but apparently not the case.
Is there a way to keep the key bindings independent between preview and stable ?

Resolved by unchecking the synchronize settings across devices in VS settings. Tools -> Options -> Environment -> Accounts -> Synchronize settings across devices when signed into Visual Studio

Related

Visual Studio 2017 Build Configuration Missing

I have Visual Studio 2017 Community 15.7.2 installed. The build configuration drop down options disappear. I have been having Problems with the build configuration disappearing on my work machine (Visual Studio 2017 Enterprise 15.8.2) as well.
If I create a new project File -> New Project -> Web -> ASP.Net Web Application (.Net Framework).
The build configuration option shows up. Then if I click on a controller class e.g. HomeController.cs. The option clears out.
The option will show up again after changing "Show output from" under the Output window. If I bring up a .cs file again. The build option disappears:
Is this now a normal behavior in Visual Studio? I suspect a bug in Visual Studio and have been updating more often than usual in attempt to fix it.
The latest update to Visual Studio Community 2017 (15.8.4) did not fix the problem.
Go through each of the Tools -> Extensions and Updates and disable an extension and then restart Visual Studio. Start with ones that aren't created by Microsoft.
Repeat this until you have tried all the extensions.

Can We Use the VS 2015 Report Designer in VS 2017?

The newest Report Viewer for Visual Studio 2017 has some bugs that prevent us from using it. We’ve downgraded to Microsoft ReportViewer Runtime 2015 for Web Forms (v 12.0.2402.15). However, the report designer in Visual Studio creates new reports in the new “2016” format, and even editing old reports upgrades them to the new format as well. The older Report Viewer doesn’t understand the new format and bombs.
The new report designer is an extension to Visual Studio, “Microsoft Rdlc Report Designer for Visual Studio,” version 14.2. We haven’t found an earlier version of the designer available as an extension.
We’ve tried installing an earlier version of SQL Set Data Tools, but the report designer was still the same. We also haven’t found a separate download for the earlier report designer.
Is there a way to add the older report designer to VS 2017? Or do we have to downgrade to VS 2015?
(A similar problem here: Change RDL version for RDLC Reports in Visual Studio 2017)
The problems in ReportViewer that made it unusable for use were partially resolved in a later version. For example, the CSS in the ReportViewer changed the styles in the rest of the surrounding web page, which was pretty horrible (now fixed). We also saw problems of the viewer's export button drop-down list positioned far from its intended location. We had to fix that with custom JavaScript on the page.
You can include/add any RDLC created on VS 2015 to VS 2017 by click on add existing item and select the RDLC directly from your local location and will run on your VS .Add existing item
From what I can tell, ReportViewer for Visual Studio 2017 which is Version 14, is for compiling in Framework 4.5. My application is depended on 4.0 and if I switch then a bunch of other libraries need to be updated as well. I would rather get the previous version of ReportViewer 12 working, as it was working for my application without issues.
With ReportViewer Designer 14 for VS2017 installed, there is an error in the design of the page, and the application deployed and running on the server does not render the Report.
So, which way to move? Up or back...and how.

How to enable IntelliSense for C++ in Visual Studio 2015

I've just installed VS2015 for C++ development, however traditional hot keys like ctrl+space or . or -> don't show the IntelliSense window.
Somewhere on the web I found that I needed to open the IntelliSense Manager from the Tools menu. But that's not in my Tools window.
In addition, I reviewed related items in my IDE settings and found a Text Editor -> C++ -> Advanced - IntelliSense section with a number of settings, including Disable IntelliSense, which is True in my setup. The problem is that all settings in this section are readonly (not editable).
How do I fix the problem?
VS2015.2, fresh install. No previous installation on this host.

Debugging a Windows Phone 8.1 Unit test (Visual C++)

The issue is that I have created an Universal App for Windows 8.1 and Windows Phone 8.1 choosing in the wizard Visual C++ -> Store Apps -> Universal Apps -> Windows Runtime Component.
So to test its behaviour we have created a Windows Phone 8.1 Unit test project (also Visual C++) where we add as reference the Universal App project, and also in the project properties in the tab Configuration properties -> C/C++ -> General, in Additional include directories I referenced the Universal App (specifically the folder .Shared of the Universal App). Then we add also some .lib to this Unit test project through Configuration properties -> Link -> Input.
So this ok, the Unit test project find the references, and we can call methods from the Universal App even test them with assertions, and so on.
The issue is when I try to debug the Unit test code in the ARM platform (I have Nokia Lumia 920 plugged in the computer) it starts to load the microsoft symbols, etc. but finish the test without stopping or just terminate the test with an exception message (even passing the test or not).
I'm using Visual Studio Ultimate 2013 Update 2.
PS. In case of not being able to debug it due to any Microsoft and/or version issue or whatever, could I show in the console some values? Cause I also tried with std::cout, or OutputDebugString, without success.
PS2. My case reminds me to this issue descripted in this ticket but with a different version of Visual Studio and working with Windows 8.1 and WP 8.1 instead of 8 version ---> Cannot debug Windows Phone Runtime Components with Visual Studio 2012 Update 4
I fixed this issue by adding and selecting the .runsettings file as shown in this article. You can select the .runsettings file by using the guide on this page under "Customizing tests with a .runsettings file". The app I used this technique on was also a WP 8.1 RT app.
I fixed this by changing Default Processor Architecture to x64 under Test > Test Settings

Removing Pocket PC pollution from VC++ project

I have a VC++ project in VS 2005 that I make 32 and 64bit releases of. I just installed VS 2010 and am trying to port the project to the newer Visual Studio. It won't port because the project references the platform "Pocket PC 2003 (ARMV4)".
I have never created any project for Pocket PC. I don't know why this is device exists as an Option under Device Tools.
VS 2010 does not support this device, and won't convert my 2005 project because of it. How to I remove un-needed devices from my old project.
Thanks,
Gerry
Open the project/solution files in a text editor and manually remove the references to it.
Build + Configuration Manager. Upper right combo (Active solution platform), pick Edit. Select the unwanted platform and click Remove.