Microsoft has announced 64-bit Visual Studio, but in its rush towards modern development some developers using older Windows or Azure technology are feeling left behind.
The forthcoming release of 64-bit Visual Studio 2022 (VS 2022) is huge news for devs who have been requesting this for over a decade. But the company still has some tricky issues to navigate with its developer community, especially those using older Microsoft technology, as well as areas where the full Visual Studio finds it hard to keep up with its nimbler cross-platform cousin, VS Code.
The context here is that today's Microsoft cares most about winning developers for its Azure platform. The combination of VS Code and GitHub is strategic because, although these tools work fine with competing platforms like AWS or Google Cloud, Microsoft can ensure that Azure is well integrated.
In addition, features like the forthcoming GitHub Codespaces, remote development environments, run on Azure. Microsoft is also improving Visual Studio for Azure and GitHub development. Corporate veep of product Amanda Silver promised that VS 2022 will set up 'a complete CI/CD solution when you first create a project' based on GitHub workflows and actions as well as Azure resources.
Eclipse is an extensible development platform with runtimes and application frameworks. Rating & Review Visual Micro is an Arduino compatible Build, Upload and Debugging solution for Visual Studio 2017 & 2019. License: Perpetual or Yearly Licenses are available from $12 per year (includes forum support and updates). Extension for Visual Studio Code - Jamstack IDE. Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
This kind of pre-baked wizardry saves time for developers and keeps them hooked on Microsoft's platform.
That said, there are a few problems with Visual Studio in a modern development context. The first is that it runs mainly on Windows (there is a Visual Studio Mac, of which we will say more in a moment). Modern development is dominated by web and mobile clients and Windows is increasingly isolated as the only common platform that is not Unix-like. This can cause friction with things like line endings, filemode settings, Bash scripts, and Node.js modules when some developers are on Windows and some on Mac or Linux.
Microsoft has invested in Windows Subsystem for Linux to make working on Windows a hybrid Windows/Linux experience – but VS Code is ahead of Visual Studio with strong support for WSL already.
A second issue is that Visual Studio is not ideal for JavaScript and TypeScript debugging, which involves browser integration.
Git integration is a third issue. Git integration in VS Code is excellent, but in Visual Studio there are issues like lack of submodule support, where in effect multiple repositories are open. 'Stop rewriting the basic git experience to make things nicer and start including this which is something developers are really blocked by!' said developer Joris Kommeren in response to a post from the team about Git support earlier this week.
Microsoft Program Manger Pratik Nadagouda answered that 'it's a tough, complex problem to solve. And we've started down that path by first tackling multi-repo support.'
Another challenge for Microsoft is that as it adapts Visual Studio to fit better with modern development, it risks leaving behind developers still using older technology. Two examples are Azure DevOps, the software development and lifecycle manager which evolved from Team Foundation Server, and Visual Studio Tools for Office (VSTO), the old set of tools for extending Microsoft Office.
Azure DevOps users are concerned that as Microsoft improves GitHub support in Visual Studio, their experience is going backwards. When Microsoft introduced a 'new Git experience,' using Azure DevOps became harder. 'I've just created a repo and when I select 'push' my two options are GitHub and GitHub Enterprise. Yeah – NO,' said developer Howard Richards. 'I know that GitHub is 'hip,' but it really seems like Microsoft is just throwing DevOps Repos under the bus with all of this focus on GitHub,' said another.
A long-running feature request to port VSTO to .NET 5 (formerly called .NET Core) is so far unresolved. The problem here is that Microsoft has been trying to get developers to migrate Office add-ins to JavaScript and a web-based model, which works in Office 365 and cross-platform, but developers say that this approach is less powerful and that there are no porting tools.
'My company relies on VSTO to deliver our product, and while I understand that OfficeJS is the future, we need to be able to maintain our current product for the next several years while an OfficeJS-based successor is developed. Additionally, VSTO offers capabilities that OfficeJS simply does not... I would also note that VSTO has received essentially no updates since 2010,' said developer Eric Smith.
'Many of our core internal processes are enabled by in-house VSTO addins that support our domain experts. This relies on a C# codebase and is maintained by engineers with primarily C# experience. The last time I looked Office Addins didn't support everything that we do in our VSTO addins, and regardless it would be extremely costly for us to port this to JavaScript and re-train the team,' said another.
Past experience suggests that while Microsoft will maintain compatibility with its old technologies (such as VSTO add-ins) for a long time, it will not put significant further investment into them.
These real-world business needs illustrate how Microsoft is being pulled two ways, pressed by its most loyal Windows-based developers to maintain and enhance their tools, while also transitioning to a cloud-based platform that is more Linux than Windows.
What about cross-platform Visual Studio? One might think that VS Code is the cross-platform tool, but Microsoft also has Visual Studio for Mac as well as requests for Visual Studio for Linux. There are also requests for a native ARM64 variant.
The Mac version is perhaps a historical accident since it arrived at Microsoft via Xamarin and was originally based on a .NET IDE called MonoDevelop. Silver said: 'We're working to move Visual Studio for Mac to native macOS UI,' which raises many questions about what is happening to this tool and whether more of its code will be written in C++.
It is currently less capable than Visual Studio on Windows, with its main role still for Xamarin development, which will become MAUI (Multi-Platform pp UI). It makes sense for Microsoft to share code between Visual Studio Windows and Mac as far as possible, and more cross-platform code would help with a possible future Visual Studio for Linux, but it may be hard to take Visual Studio in that cross-platform direction without further eroding its features for Windows-only development. ®
Today, Microsoft announced Visual Studio 2022 along with its first public preview coming this summer. The next major release of Microsoft's flagship development toolkit will be 'faster, more approachable, and more lightweight', according to Amanda Silver, who made the announcement on Microsoft's DevBlogs.
One of the big news with Visual Studio 2022 is going to be the transition to a 64-bit app. Indeed, Microsoft has been making a push towards 64-bit across the board, and now Visual Studio is joining the fray. A major advantage of 64-bit apps is that they're not limited to 4GB of memory, so this new release will have unrestricted access to all the memory on your PC. That should result in much better performance across the board and fewer out-of-memory errors.
The new version of Visual Studio will also come with updated icons that should be easier to identify and understand at a glance, support for the new Cascadia Code font that Microsoft introduced with Windows Terminal, new product themes, and integration with Accessibility Insights to help developers spot any accessibility barriers quicker. Microsoft is also making it easier to customize your experience with Visual Studio, with settings for the IDE and the ability to sync (or not) settings across devices.
As for what types of apps you can build with it, Visual Studio 2022 will be compatible with Azure resources, .NET 6, and C++ 20. That includes full support for the unified framework in .NET 6 and things like the Multi-platform App UI (MAUI) that can be used to create apps for Windows, Android, macOS, and iOS.
Other improvements include better performance for the core debugger, support for text chat during Live Share sessions, more capabilities for the IntelliCode engine, improvements to code search, and better asynchronous collaboration, with new logic related to making commits and reviewing pull requests from platforms like GitHub.
Microsoft also says it's 'refreshing' Visual Studio for Mac, switching to a native macOS UI to offer better performance and reliability. It will also integrate with macOS accessibility features, and Microsoft is updating the terminology across the IDE so it's more consistent between Mac and Windows versions.
As mentioned above, the first preview of Visual Studio 2022 will be available this summer, and Microsoft will likely iterate on it a few times leading up to the stable release.