Alternate you can also add false and keep Properties.cs. I also had to delete the Properties.cs file that hold assembly configuration - that information by default gets generated by the project file info. To start I simply created a mostly empty project file from my old project: Īt this point I can actually open the project in Visual Studio as a new SDK style project. What's nice about that is that you can easily create a new project by basically deleting the old one and adding just a few simple things into the file. You only explicit add files that require special instructions like static files or folders to copy, or files to exclude from building or copying. Instead the project knows about common file types and automatically builds what it knows how to build. NET projects because you generally don't have to list every file that the project needs to build. NET SDK projects are much simpler than the old.
NET SDK Project Format file by switching the old. So the first thing I did is convert the MM exe project file to the new. To start I unloaded the Addin projects to focus only on the main project first. Markdown Monster is comprised of one main WPF EXE project which contains the bulk of code, plus several Addin projects that handle things like Weblog Publishing, Screen Captures and the Snippet Editor. NET Core 3.0 Preview 5 which is the latest Preview at the time of writing. I edited out some extraneous stuff, but it's mostly just off the cuff, but if you're thinking about porting an application I think most of the things I describe here are things you are likely to run into yourself even if this application is a bit more esoteric as it includes some interop features due to the Web Browser control used the core UI.Įxamples are based. Heads up: This is a long rambling post as I just wrote down a bunch of stuff as I was going through it. How do resources (Assets) get embedded into the project.Porting - How do I get my project ported.How do external assembly loads (for addins in MM) work.
How to handle non-.NET Standard NuGet Packages.NET Core are pretty trivial - you can see how the process works, but just looking at those examples I had a million questions of how certain things will be handled. Most of the examples I've seen so far for ports or running applications on. Today I took the day to explore what it would take to port Markdown Monster to.
0 kommentar(er)
