Introduction

Going Big! Support for Windows Desktop Apps

Easy Conversion of existing Desktop Applications

Made it Simple Deployments

Updating Project Files: A new approach

Closing Notes

Our previous article was on What Is New In ASP.NET Core 2.0 and we also discussed what is HAP and how is it useful! Here, in this blog, we are going to see the new tale of the powerful beast for the computer world which is the .NET that simplify the task of developing cross-platform applications. Microsoft has recently announced about sharing their plans ofand therefore, it is important for us to know. The version 2.1 of the .NET is ready for the release this year that offers a greater blend of tools and features but to add more excitement to it, Microsoft has started to lay roads for the development of .NET Core 3.0 and are expecting to release it in 2019. The interesting part is that features that were requested by the individual developers and coding enthusiasts have been implemented.One of the most exciting and impressive features that the team from Microsoft has planned is to provide support for the Windows Desktop applications and will span those especially such as UWP XAML, Windows Presentation Framework(WPF) and Windows Forms. Thus, it is a great opportunity for you as a developer to unleash your app developing skills to a higher level as you would be able to run any window desktop app regardless of it being old or new. This feature is in addition to those that are already present with the benefits that .NET Core has already got. The idea to give support came into the picture after the Microsoft has received numerous requests for the feature. Hence, its a delight for the desktop app lovers as this is a bonus to their interests. It has to be noted that, the other features such as that of web and cloud will still continue to exist as it used to be earlier, with the change being is the addition of desktop applications support.Given the details of the information that there are some new features in .net core 3.0, any professional would be interested in converting their present applications to the system that uses the .NET core 3.0. Usually, developers face many troubles in moving the existing application to other technologies especially if the application size is big. It is such a painful task for them, but the process isn't hectic in the case of .NET Core 3.0. Surprisingly the entire procedure is rather made simple and straightforward. All that is required of you to do is to set the target of your existing desktop application as .NET Core 3.0 and compile the files again. You needn't set target for the dependencies but doing so would carry some benefits. One good example of this easy process is the story of conversion of the popular MS Paint application. The .NET team didn't have the source code of Paint within their reach but were able to get the binaries of the Paint.NET that were working based on the .NET Core. They used the WPF binaries that were available in the .NET directory which was present on their machine in the lab as they were not having the WPF special build. The paint, to their surprise was working very well and that too it reported a faster start-up without any optimization work being done on it. Apart from this, the .NET team had a heavy breath after they were able to find out the tricky bug that existed in .NET Core and have fixed it. Apart from this, there has been an attempt to make the EF6 work on .NET Core 3.0 by updating it. The EF Core is expected to come equipped with few new features. New applications regardless of what type they are, the EF Core remains to be the data stack that would be recommended highly. Those developers who are willing to take the advantages and extra benefits, it is advised from Microsoft to port to the new EPF Core for the projects.One could conclude easily that there is a lot of flexibility offered in deploying the project to suit the newly installed. You are given the ability to do the central installation and service the application with its benefits. The good thing here is these don't require any in-place updates. For the subsequent versions release of .NET Core, apps could be updated in a pattern by doing it on one system after the other. These steps are accompanied by a guarantee that they won't affect any other apps. The above said deployment is of one variety which can be termed as Side-by-side deployment. You can also deploy your application updates yet in another way where you are in need of maximum isolation. The Microsoft is striving hard to deliver a new build tool that can enable you to bundle the app and .NET Core into a single exe(Executable) file.The adoption of SDK-style for projects forhas given a lot of improvements in various dimensions. NuGet packages are thereafter referenced using PackageReference, which is one of the key aspects of projects that are following SDK style. Project files result in smaller and cleaner versions when SDK is the approach. The advantage of support to multi-targeting is leveraged with this style. The packages.config is replaced by the PackageReference. This change helps a developer to refer the entire component area which is a total contrast to the earlier facility where only one single assembly could be referenced at once.The team from Microsoft are working hard to plan for few early releases of theso that they would have the measure of the quality with the help of user feedback. In addition to it, they have been conducting surveys to get a bigger picture of what more the users are willing to have in the latest version. Finally, the staff claims that there isn't any kind of big architectural changes in the newer version though!