Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Discussion: should we keep support for net40 and net45?

See original GitHub issue

Recently, Markdig which this project relies on, has dropped for net35and net40 (see https://github.com/lunet-io/markdig/pull/416).

It means that we can’t upgrade the version we use anymore. So I am opening a discussion to decide what we should do from now on.

cc @mengluwang121 you were the one to request support for net45 (and not net452) in #25. Is it still a requirement?

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

Kryptos-FRcommented, Sep 12, 2020

Given that net40 has been out of support for more than 4 years (see Support Ending for the .NET Framework 4, 4.5 and 4.5.1, there is little sense keeping it. Therefore the final decision is to drop it for Markdig.wpf.

However, net452 is supported until January 2023 (as part of Windows 8.1 lifecycle), so we will keep it until either this expiration or if Markdig drops support for it sooner ; there were kind enough to put back the support for now, but it might change again in the future.

0reactions

Kryptos-FRcommented, Oct 18, 2020

Markdig doesn’t support net45 anymore, so there really is nothing I can do on my side. You will have to use an earlier version.

I am still quite surprised to read that you have to support Win7 given that the OS is out of support, and even for people still using it, they should now have had net452 runtime installed as an automated Windows Update 4 years ago, when both net45and net451 went out of support.

Since we are talking about a development tool (Visual Studio), I can’t think of any developer in the whole world that would still work on a machine that can only produce applications and libraries on obsolete and unsupported platform. Surely, a developer would always have a more recent (if not the most recent) set of tools to do their work. Your scenario sounds really unrealistic to me.