All geek questions in one place

Mono vs. .NET Interop Curiosity

I am developing a huge console application for Unix using C # through Mono. If I develop this application using M Visual Studio and .NET 3.5, and I carefully neglect to use the Win32 API calls, should I expect the application to work automatically in my Unix window? Or should I just get MonoDevelop and go into Mono mode?

+4
source share
3 answers

According to the compatibility page Mono Mono supports:

Everything in .NET 3.5 except WPF and WF is limited to WCF.

If you want to develop in Visual Studio, you should do regular testing on Mono to make sure that you don't run into a rough edge.

+5
source

You can also use the Mono Tools add-in for Visual Studio, which allows you to remotely test Linux, deploy it on Linux systems, etc. This is a commercial, but there is a free trial.

http://go-mono.com/monotools/

+3
source

In the general case, if you use only material supported by mono, you can use Visual Studio, but you should also often test mono. And not only mono for windows, but mono works on the target OS. You can do this from visual studio by remote debugging on the target OS using mono add-ons for visual studio.

Having said that MonoDevelop is really becoming very good, I see no reason not to skip Visual Studio at all and develop using MonoDevelop on the target OS. This way you do not need to worry about the differences at all.

+1
source

Source: https://habr.com/ru/post/1304842/

More articles:


All Articles