github/greenshot
1
0
Fork 0
mirror of https://github.com/greenshot/greenshot synced 2025-08-22 22:34:27 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Edit of dotnet core blog entry, with additional information coming from the Connect(); 2018 event.

Browse source
This commit is contained in:
Robin 2018-12-05 09:53:22 +01:00
commit 480a08ecf1
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
_posts/2018-12-04-dotnet-core.markdown
View file

@ -35,7 +35,9 @@ The announcement was just what I was waiting for! Microsoft demonstrated that wi
One of the challenges with Greenshot was picking the version of the .NET Framework to run on, actually we were way to conservative and this limited our possibilities. The problem with the .NET Framework is that there can be only one version installed on a Windows PC! So if we want to use the newest version, we force a lot of people to update and a lot of companies might not be able to do so without extensively testing their other applications. The Greenshot installer needed to start the .NET Framework installer if this wasn't available, managing this added another complexity. With dotnet core this is a thing of the past, every application __can__ provide their own version of dotnet core and multiple versions run side by side!
Although Greenshot is open source it currently needs the .NET Framework to run, but this isn't open source! The [.NET Foundation](https://dotnetfoundation.org), which is an independent organization which supports many open source .NET [projects](https://dotnetfoundation.org/projects), is also taking good care of dotnet core. As soon as Greenshot is released for dotnet core, the complete stack (well ~99%) is running with open source technologies!
Although Greenshot is open source it currently needs the .NET Framework to run, but this isn't open source! The [.NET Foundation](https://dotnetfoundation.org), which is an independent organization which supports many open source .NET [projects](https://dotnetfoundation.org/projects), is also taking good care of dotnet core. As soon as Greenshot is released for dotnet core, the complete stack is running with open source technologies!
__Edit__: On the 4th of December, "coincidentally" only hours after my blog post was made available, Microsoft announced on the Microsoft Connect(); 2018 event the following [NET Core 3 Preview 1 and Open Sourcing Windows Desktop Frameworks](https://blogs.msdn.microsoft.com/dotnet/2018/12/04/announcing-net-core-3-preview-1-and-open-sourcing-windows-desktop-frameworks/) This shows that Microsoft is really serious about its open source commitment, and that going towards dotnet core is the right thing to do for Greenshot! With this announcement the full stack of Greenshot on dotnet core, including the UI components, is build with open source technologies!
Another interesting fact is that the .NET Framework is used by billions of applications, this makes it __very__ hard to maintain backwards compatibility while adding new features or fixes. With dotnet core, which doesn't have all the legacy applications, a different approach is possible. By releasing more often and not having the need to support years of backwards compatibility, it's finally possible to introduce new features and maybe sometimes even make breaking changes. One thing where this shows is that dotnet core has many performance enhancements, which will also be noticeable in Greenshot.
@ -51,7 +53,7 @@ With this available I worked for the last 3 months to get the whole of Greenshot
At the time I am writing this the current state is that Greenshot is running on .NET Framework 4.7.1 and dotnet core 3.0 __side by side__! Having things work side by side is very convenient, we can stay on the "stable" .NET Framework and release from there, but as soon as dotnet core 3.0 is available for the general audience we can also release for this. I would say that the dotnet core implementation has around 95% of the functionality which .NET Framework has, and the only reason for this is time. There are __currently__ no show stoppers why the dotnet core 3.0 version of Greenshot would have less functionality, in fact I expect that it will be the other way around.
I expect that the first release candidate of dotnet core 3.0 is available before I finish all the open ends on Greenshot, but we might be able to start releasing alpha builds at the end of the first quarter of 2019. Around that time I will also write a blog post about the coming features, and give a bit more information on the release timeline.
I expect that the first release candidate of dotnet core 3.0 is available before I finish all the open ends on Greenshot, but we might be able to start releasing alpha builds at the end of the first quarter of 2019. Around that time I will also write a blog post about the coming features, I still need to see what else is possible in this new world of dotnet core, and give a bit more information on the release timeline.
P.S.