Support for .NET Core

[Remo]

Is it feasible to support .NET Core? If yes, do you have any intention to do that?

[ramon-mendes]

I do think think it is feasible. However I don't have experience with .NET core and no real time available for doing so.

[pveliz]

Hi @Remo it is possible to do it, I did it with .Net Core 2.2 and .Net Core 3 if you need help, just let me know.

[Remo]

thanks @pveliz I started myself, but I stopped due to changing priorities. Maybe I will clean up what I did and publish it. It isn't complete yet though..

[ramon-mendes]

Keep it up guys. If you need help making tests, let me know.

[AnthoniG]

Hi guys, does anyone have an example for C# Core that I could play about with. Am hoping this is a better way that Electron, etc. However it has to cross-platform, thus C# Core

[ramon-mendes]

Its is cross-platform! No need for .net core.
Just head to https://misoftware.com.br/Bootstrap/Download and download the project:

You can compile it on Windows with VS, on Mac with VS for Mac, and on Linux with MonoDevelop

[AnthoniG]

@ramon-mendes Thanks, did not see that 😀

[kashfshah]

This issue could be important to undertake, given the future of .NET 5 and the advances in cross-platform support with .NET Core.

Are there any particular challenges or roadblocks that could be broken into other issues?

[ramon-mendes]

I will put it in my roadmap. I just need to learn how make the NuGeT packaged available for .net core. I really don't know where to start looking for. Any advice?

[kashfshah]

Making the NuGet package itself isn’t really any different; the biggest difference is the process of building the project for .NET Core.

Probably the easiest way to start seeing how difficult it might be is to try the simple approach first:

• Make a brand new solution
• For each of the existing projects, make brand new projects in that new solution which target some version of .NET Core (3.1 would be latest, iirc, but 2.2 or something is maybe better for lowering the dependency version for consumers of this NuGet package)
• Copy the code files from the old projects to the new projects, excluding configs, assemblyinfo, etc.
• Start the porting effort: start adding the nuget packages that you reference in the old projects to see if any of those packages don’t have .NET Core support yet
• Try to build and see if you are using any .NET Framework code that hasn’t made it into .NET Standard
• Find alternatives for anything found missing in the previous two steps.

If you’d like to do some analysis before jumping into it, there is the .NET Portability Analyzer built into Visual Studio that you can use to analyze the existing solution to see what will be causing problems in those last three bullet points.

Finally, when I get a free moment from work one of these coming weeks, I’d be happy to give it a try and let you know what I find out.

[kashfshah]

Also, there is this documentation from Microsoft which is a little overboard, but is the true documentation: https://docs.microsoft.com/en-us/dotnet/core/porting/

[kashfshah]

This might be one technical challenge: https://stackoverflow.com/questions/40892189/net-core-and-system-drawing

[kashfshah]

Also, this: https://docs.microsoft.com/en-us/dotnet/core/compatibility/winforms