How To Update Microsoft Visual Studio
Elpidio Heart
The Visual C++ Redistributable installs Microsoft C and C++ (MSVC) runtime libraries. Many applications built using Microsoft C and C++ tools require these libraries. If your app uses those libraries, a Microsoft Visual C++ Redistributable package must be installed on the target system before you install your app. The Redistributable package architecture must match your app's target architecture. The Redistributable version must be at least as recent as the MSVC build toolset used to build your app. We recommend you use the latest Redistributable available for your version of Visual Studio, with some exceptions noted later in this article.
Unlike older versions of Visual Studio, which have infrequent redist updates, the version number isn't listed in the following table for Visual Studio 2015-2022 because the redist is updated frequently. To find the version number of the latest redist, download the redist you're interested in using one of the following links. Then, look at its properties using Windows File Explorer. In the Details pane, the File version contains the version of the redist.
Some of the downloads that are mentioned in this article are currently available on my.visualstudio.com. Log in using a Visual Studio Subscription account so that you can access the download links. If you're asked for credentials, use your existing Visual Studio subscription account. Or, create a free account by choosing the No account? Create one! link.
Visual Studio versions since Visual Studio 2015 share the same Redistributable files. For example, any apps built by the Visual Studio 2015, 2017, 2019, or 2022 toolsets can use the latest Microsoft Visual C++ Redistributable. However, the version of the Microsoft Visual C++ Redistributable installed on the machine must be the same or higher than the version of the Visual C++ toolset used to create your application. For more information about which version of the Redistributable to install, see Determining which DLLs to redistribute. For more information about binary compatibility, see C++ binary compatibility between Visual Studio versions.
These links download the latest available en-US Microsoft Visual C++ Redistributable packages for Visual Studio 2013.You can download other versions and languages from Update for Visual C++ 2013 Redistributable Package or from my.visualstudio.com.
These links download the latest available en-US Microsoft Visual C++ Redistributable packages for Visual Studio 2012 Update 4. You can download other versions and languages from Microsoft Visual C++ Redistributable Packages for Visual Studio 2012 Update 4 or from my.visualstudio.com.
Today we are announcing the retirement of the Visual Studio for Mac IDE. Visual Studio for Mac 17.6 will continue to be supported for another 12 months, until August 31st, 2024, with servicing updates for security issues and updated platforms from Apple. While the decision has been made to retire Visual Studio for Mac, we remain committed to our developers on Mac with alternatives like the recently announced C# Dev Kit for VS Code and other extensions that will allow you to take advantage of our ongoing investments in .NET development on a Mac.
Visual Studio for Mac will no longer be supported starting August 31st, 2024. On that date, Visual Studio for Mac will be available as a legacy installation only via my.visualstudio.com for users with Visual Studio subscriptions but will no longer be serviced or maintained. If you have any support agreements, you will continue to have access to technical support until August 31st, 2024.
Visual Studio IDE running on Windows in a VM on Mac: This option will cover the broadest IDE needs such as legacy project support for Xamarin, F#, and remote development experiences on iOS by using a virtual machine (VM).
Visual Studio IDE running on Windows in a VM in the Cloud: Visual Studio continues to be the premier tool of choice for .NET/C# development. A Cloud hosted VM from Microsoft Dev Box provides access to the full power of VS through your Web or native RDP client from a Mac without the overhead of running a virtual machine on your local machine.
Not unexpected and we on Uno team hope its for the better. Thanks for many years of service! Go Dev Kit, go. Looking forward to supporting / leveraging C# Dev Kit in the future from our VS Code plugin . Sasha.
I spent Thursday and Friday trying to get a simple maui app that I wrote to load and run under vscode and the Maui extension. Never could get it to work. Bought Rider, and it popped right up. Vscode is not an ide that we are looking for.
There is no change to our investment in MAUI. the .NET team is releasing many .NET MAUI updates in .NET 8. We understand the extension is not a replacement for a full IDE, but we are continuing to invest in making it a great experience.
And that is part of the problem. The Xamarin devs are gone, the MAUI team is too small, WinUI is years in and in even worse shape. Microsoft needs to increase its commitment. The current state is brink of death ?
Investment in MAUI should mean to be fully committed to actively develop and support it at least 10 years from now, on all 4 platforms: Windows, Android, Mac and iOS and to make it the main framework for desktop applications in .NET.
Otherwise, it will just be an abandoned technology like WinForms, WPF, Silverlight, UWP etc..
There is a whole drama around this topic, that Microsoft allegedly forked Omnisharp plugin only to be able to give it a price tag. So they took advantage of the open source nature of the project, without giving back to the open source project.
This announcement would make sense if VS had become multi-platform or VS Code had been substantially improved. In the absence of that, it seems like this risks burning the bridges with non-Windows devs so many at MS have worked hard to build the past 10 years.
This combined with that new C# Dev Kit extension for VSCode seems to be pointing to a planned decommissioning of Visual Studio itself. We were already in a situation where vendors were favoring VSCode for new extensions etc (things would be developed first for VSCode, and then later (or never) for Visual Studio).
Xamarin support ends on May 1, 2024, so technically VS for Mac will be supported for at least as long as Xamarin is. Beyond that, you would need to continue using an unsupported VS for Mac version to build an app on unsupported Xamarin.
The Maui extension for vscode is not very good. I recommend against it. I spent Thursday and Friday trying to get it to work and gave up. I installed rider and everything just popped up, worked, and I could debug.
My team switched to Rider a while back and it is a viable alternative with full XIB support via Xcode sync (just as VS for Mac did). There are some quirk, but in general, Rider is just a better experience than VS for Mac was.
The build and publish functionality is one of the reasons Visual Studio on Mac is good, in many regards even better than VC on PC. Visual Studio Code is a JSON settings clunky infection mess. They need to work on that A LOT!
Same too with the clear and easy ability to manage and update dependencies and packages.
yes, I am also very interested in knowing the implications towards mac build agents for xamarin and maui. I do understand xamarin will be out of support by then, but what about maui? how are we supposed to set up build agents without visual studio?
In some ways developers are the reason for this. Developers are always chasing the newest shiny object. Always. MS is more than happy to give them another shiny object to chase. The product managers for MS need to stop being so naive about the grandiose plans their developers are selling them, maintain focus, and act like they actually respect the time and effort all of us are investing in their technologies.
I like VSC for coding actual lines of code way better for many reasons but the intelisense experience on mac is just still clunky, slower and when you have overloads for example more of a pain to use as well.
I use VS on mac for the management, build and publish side because of the better UI management experience and the time saving it offers.
You need to do a lot of work on the UI of Visual Studio Code not just for Mac and Linux users but especially for them to have a better experience. You can not just shoehorn features into JSON settings files and ever increasing complicated command lines.
This is exactly our use case for VS Code. Nice, useful and straightforward for debugging, building, and publishing iOS apps using Xamarin (and soon MAUI?). It is also very good for working with ASP.NET Core projects and Web APIs.
We have a backlog of work that will EASILY span more than a year just for the most critical work, so we have no bandwidth to suddenly take a right turn, as it were, and deal with migrating off Xamarin and VS for Mac. In short, this is a nightmare for us.
Since you are retiring it, could you opensource it and leave it to the community to develop/ improve?
+ at least make it support future versions of dotnet like NET8 lts that will be released in November?
that would be a nice goodbye gift
It seems those complaining are the ones trying to do native app development using a non-native technology. Which is always a dangerous thing to do. I find VS Code to be adequate for quite a large number of tasks (on my old Macbook Pro as well), but I mainly build command line tools and web applications. None of which are really that dependent on a fully fledged IDE.
If Visual Studio for Mac must be discontinued, it should be after support for .NET 8 has been added.
.NET 8 is the next long term servicing version of the framework. Even if the IDE is not getting support, it would be valuable for an extra three years for commercial users because it can compile and deploy using the latest SDK.
Having thought about this overnight, my prediction is that MS re-evaluates this decision. I suspect they are underestimating the impact. They are not just discontinuing an IDE, they have shaken all faith in everything cross-platform from MS.
d3342ee215