There are older questions on this topic, but I'd like to get advice on the current situation.
Details:
VS 2019 gives the message in the title. Even though it was recently updated, it still uses Xamarin.iOS 15.2.0.17, vs Mac's recent update to 15.4.0.0, to support the recent XCode update.
VS 2022 PREVIEW works - though its version says 15.3.0.41.
Question:
Is there a way to get VS 2019 to use the updated Xamarin.iOS? I assume the issue is that this is only on PREVIEW channel, but now that 2019 isn't the latest VS, I don't know how to give 2019 a preview version of Xamarin.iOS.
(I'd rather not do the alternative, which is to downgrade the version on the Mac.)
ALTERNATIVE: I could also install VS 2022 stable, if it is easier to get that to work with current XCODE + Xamarin.iOS. (I prefer to do certain tasks in a stable VS, not the PREVIEW one.)
(The reason I'm not using VS 2022 stable for my production VS, is that I uninstalled it while trying to solve a problem involving WinUI3 (Windows Desktop app) launch profiles in 2022 Preview - I was making 100% sure that there was only one version of 2022 involved. Probably didn't have anything to do with that issue, so I'm fine with re-installing it, if there is a good reason to do so.)
Is there a way to get VS 2019 to use the updated Xamarin.iOS?
ADAIK , there is no other way except updating visual studio for windows.
The latest Visual studio provides the latest package (Xamarim.iOS), if visual studio 2019 can't do that it means that it's time to use visual studio 2022 .
BTW , we can install latest Xamarin.iOS package without updating IDE in visual studio for mac , but it only works on mac.
Go to Xamarin.iOS github repo and download the pkg file ,install on mac .
I installed the new release of Visual Studio 2022 (not preview) available since yesterday. I also installed MAUI workload from a command prompt
dotnet workload install maui
I can create a new project and choosing the .Net MAUI App (Preview)
I see the solution and all the files inside.
I can compile the solution successfully.
If I close then re-open the solution it failed.
I don'have problems for a simple Console App project. So the problem seems to be related to MAUI templates.
As of today, the new Visual Studio 2022 (released november 8th 2021) does not allows us to play with MAUI templates. We will have to wait until second quarter of 2022 (I think) to get an update.
The alternative is to still use the Visual Studio 2022 Preview edition which allows us to use MAUI templates pretty well.
As today the same thing happened to me, try to install the visual studio 2022 preview version; it's working and you find .Net MAUI here:
I want to try out Blazor and it wants Visual Studio 2019 Preview. Now, I already have Visual Studio 2019 (Professional) on my machine. It is safe to install the Preview version side-by-side?
Tried to find any help on forums, but didn't find any advice.
Ok, I'll answer my question myself. Visual Studio 2019 Preview works fine side-by-side with released Visual Studio 2019. And I only got Blazor to install after I installed VS 2019 Preview.
Link to official Blazor Getting Started Documentation which specifically requires the Preview version (as of today)
I am currently using Visual Studio 2015 for programming ASP.NET Core applications. I have the following questions regarding installing Visual Studio 2017:
What is considered to be best practice and/or cleanest method?
Should I install Visual Studio 2017 beside Visual Studio 2015?
Should I first uninstall Visual Studio 2015 and all .NET Core dependencies and then install Visual Studio 2017?
Are there any tools that would ensure a clean uninstall of Visual Studio 2015?
From page Visual Studio 2017 Platform Targeting and Compatibility
Compatibility with Previous Releases Installation
You can install and use Visual Studio 2017 alongside previous versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visua Studio 2012.
So yes. you can install them without any problem.
VS 2013, VS 2015, and VS 2017 all work well side-by-side. VS 2012 can be a little dodgy on Windows 10, but should also work side-by-side. In theory VS 2010 should also work side-by-side with those, but I've run into quirks in the past with them interfering with one-another.
Projects should round-trip between 2015 and 2017 generally, although there are some one-way upgrade scenarios.
Note that if you really just need the older compiler toolset for some reason, you can also install VS 2017 and select the optional component Microsoft.VisualStudio.Component.VC.140 which installs the older v140 compiler which you can still use with the VS 2017 IDE. That said, there's not a lot of reason to do this since the VS 2015 & VS 2017 C++ standard libraries are binary compatible so you can mix them in a project.
See this blog post for information on VS 2017.
It sounds like you have done some projects in 2015 already, so you will probably want to keep it.
Once you open a project in a new version, it will try to upgrade the project and then you can't go back.
However, if you have multiple versions installed at the same time, when you try to open a project, say, from Windows Explorer, it will open it with the "Visual Studio Version Checker" and will look at the project file and determine which version to open it in.
Bottom line, if you have the hard drive space, there is no reason to not install them alongside each other.
In the past, it was recommended to install them in sequential order if you are installing multiple versions, but it doesn't sound like this is an issue for you and I don't know if that is even a problem anymore as it has been several versions since I have had to deal with that.
Good luck!
Personally, I would keep both - there have been multiple times through the years where you have compatibility issues and NEED to have the prior version(s). I've also had old project that will not upgrade and I've gone back and reinstalled old VS versions.
If you have no reason to keep VS2015 in your computer I would suggest uninstalling it.
I uninstalled VS2015 after installing VS2017 and later noticing that I was still using an old taskbar shortcut to VS2015.
So I was inadvertently still using VS2015.
Maybe some special cases require keeping older versions of VS along side the new version, but for the rest of us, I say, uninstall!
VS 2015 is the last version that is supported by Installshield LE.
If you have a need for building installers in the future, it will be useful to have VS 2015
1,2,3. Visual Studio 2017 has more features over 2015 and it contains 2015's current features so you don't need 2015 alongside 2017. Just stick with 2017. And I don't think you will have any problems while opening 2013 and 2015 projects with Visual Studio 2017.
Uninstall Tool is a good tool to use. It cleanses all the leftover files and registry entries after running the original uninstallation wizard and even tells you how many files will be cleaned after the required reboot.
For people continuing to read this, I have Visual Studio Professional 2008 (For Windows Embedded 6.5), 2010, 2015, 2017 and they all work even if open at the same time.
Edit: As stated in other answers, they need to be installed from oldest version to newest.
I originally created an ASP.NET site in Visual Studio 2010 a few years ago and it went through the VS 2010 SP1 update as well. This meant that Visual Studio 2012 opened the solution without performing a one time upgrade.
The issue I am having is that the built-in browser selector in Visual Studio 2012 is not available for this project and the settings only let you use the default browser.
When I looked in the .SLN file, the version line indicates Visual Studio 2012 (i.e. # Visual Studio 2012) and no other setting in there appears to have anything to do with this limitation.
Has anybody had this issue and, if so, can you please let me know how your overcame it?
Thanks!
You're going to have to upgrade your project to allow it to make use of Visual Studio 2012 only features. Note, if you do this you will no longer be able to open your project in earlier versions of VS.
http://msdn.microsoft.com/en-us/library/hh266747%28VS.110%29.aspx
For VS 2010 , you can install WoVS Default Browser Switcher extension
Also a related question Change default browser in Visual Studio 2010 RC