I have a number of projects created in earlier version of Visual Studio. These open fine in 2017, I can edit and save changes, but the solution file still has the icon indicating they are VB10, VB11 or VB14 solutions.
My concern is that in later versions of Visual Studio the solutions will no longer be supported. Can I force a complete upgrade to Visual Studio 2017? Is this necessary?
Related
I installed VS 2022 Community and am trying to work on a project that was developed on VS 2008 Pro. VS is giving me this report:
How do I force VS to make whatever upgrades it needs in order to run this program? I can provide more info if needed.
MS in their wisdom, dropped support for the Setup & Deployment project, can't remember when exactly, then after a bit of an uproar re-instated it through the Visual Studio marketplace https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects
Since your project has a file .vddproj, it might be a Smart Device CAB project.
It is not supported by later versions of visual studio.
It is recommended that you open it with VS2008.
I tried to open a .Net Core solution which was working fine in 2015. Recently they added some .Net Core projects to the solution and asked us to upgrade to Visual Studio 2017 to be able to run them. We installed Visual Studio 2017 and tried to open the solution, but I am not able to build it. I get the following errors when I right-click and try to select "Manage Nuget packages".
I tried to open the PackageManager console from Tools: even this is not working
I also performed the "repair Visual Studio" process too.
Finally i resolved it by deleting my nuget.config both at project level and also in %appdata%/roaming/nuget .I think the issue is because of broken config file due to change from visual 2015 to visual studio 2017 .Not sure about the exact issue though
After I installed an extension to Visual Studio 2017 Enterprise, VS crashes on startup. In previous versions there was a /safemode switch. I tried it but it seems to be no longer supported. What can I do to suppress loading of extensions in Visual Studio when it crashes (cannot disable extensions via extension manager).
Thanks
There is still a /SafeMode switch. If this does not help you need to do a repair on visual studio 2017
https://learn.microsoft.com/en-us/visualstudio/ide/reference/safemode-devenv-exe
I am using Windows 7 SP1.
I have SQL Server 2012 installed along with Visual Studio Community 2015.
The SQL Server 2012 installation has always forced me to use VS2010 Shell to launch SQL Server Data Tools.
I recently installed an update through the NuGet Package Manager in VS2015 which included SSDT. I was hoping that this would enable me to use SSDT with VS2015. However it still launches with VS2010.
My question is: How do I used SQL Server Data Tools with Visual Studio 2015?
Thanks
The latest release (Feb 2016) is the first release of SSDT that can target different versions of SSIS so you can now target 2012 from visual studio 2015:
https://blogs.msdn.microsoft.com/ssdt/2016/03/07/ssdt-preview-update-feb-2016/
It is still in preview though so you will need to download the pre-release bits:
https://msdn.microsoft.com/en-us/library/mt204009.aspx
or wait a month or so for the RTM release.
I usually use the pre-release builds and they are normally pretty solid but each environment is different :)
ed
Visual Studio 2012 Premium crashes when I use the Solution Configuration Manager (or drop down on tool bar) to switch from Debug solution config to Release. As soon as I make the selection to the Release config, I get a dialog with a progress bar stating it is looking for a solution to the problem and after a few seconds that dialog closes VS closes and another dialog opens that states it is restarting Visual Studio. I get this same behavior if I try to create a new configuration from within the Solution Configuration Manager; i.e., as soon as I save the new config VS crashes. During the crash I'm not given the option in the dialogs to get detailed info for the crash.
This did not happen with the same code in VS2010 and Win7.
My work-around is to modify the Debug config to be what I need for Release, and then put it back to what I need for Debug.
VS 2012 was installed on a clean (not an update) install of Windows 8. I've installed all the latest updates for both Win8 and VS. Here is the Visual Studio boiler-plate info:
Microsoft Visual Studio Premium 2012
Version 11.0.50727.1 RTMREL
Microsoft .NET Framework
Version 4.5.50709
Installed Version: Premium
LightSwitch for Visual Studio 2012, Team Explorer for Visual Studio 2012, Visual Basic 2012, Visual C# 2012, Visual C++ 2012, Visual F# 2012, Visual Studio 2012 Code Analysis Spell Checker, NuGet Package Manager 2.0.30717.9005, PreEmptive Analytics Visualizer 1.0, SQL Server Data Tools 11.1.20627.00, Web Developer Tools 1.0.30710.0