open 2 instances of visual studio for mac

Open 2 instances of visual studio for mac for mac#
Open 2 instances of visual studio for mac software#
Open 2 instances of visual studio for mac code#

Open 2 instances of visual studio for mac code#

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.“DeNA aims to entertain and to serve through our businesses, under our mission to delight people beyond their wildest dreams. 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).

Open 2 instances of visual studio for mac for mac#

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++. The Mac version is perhaps a historical accident since it arrived at Microsoft via Xamarin and was originally based on a. There are also requests for a native ARM64 variant. 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. 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.

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. 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. This relies on a C# codebase and is maintained by engineers with primarily C# experience. 'Many of our core internal processes are enabled by in-house VSTO addins that support our domain experts. I would also note that VSTO has received essentially no updates since 2010,' said developer Eric Smith. Additionally, VSTO offers capabilities that OfficeJS simply does not. '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. 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. What about VSTO?Ī long-running feature request to port VSTO to. '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. Yeah – NO,' said developer Howard Richards. 'I've just created a repo and when I select 'push' my two options are GitHub and GitHub Enterprise. When Microsoft introduced a 'new Git experience,' using Azure DevOps became harder.

Open 2 instances of visual studio for mac software#

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.Īzure DevOps users are concerned that as Microsoft improves GitHub support in Visual Studio, their experience is going backwards. And we've started down that path by first tackling multi-repo support.' Live in my new world or die in your old oneĪnother 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. Microsoft Program Manger Pratik Nadagouda answered that 'it's a tough, complex problem to solve. '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. 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.