Switch Target Framework version to .NET 4.5 / 4.5.2 about jurassic HOT 3 CLOSED

I'm closing this issue as Jurassic now targets .NET Standard 2.0.

from jurassic.

I needed to switch to v4.0 because that's the first version that has the ConditionalWeakTable class. Is there any benefit for a class library to switch to v4.5?

from jurassic.

Hi,
If there is currently no need to use a type that is available in v4.5 or higher, then there is no immediate benefit in switching to v4.5.
My thinking was, since this is going to be a new major version (Jurassic 3.0) where a higher .NET version than v3.5 is required anyway (with using of the ConditionalWeakTable), it might make sense to switch to v4.5 instead of to v4.0, because then if in the lifetime of the Jurassic 3.0 version a change or new feature is required that is only available in v4.5, you can just start using it.

This would have an impact for Application projects that want to use the new Jurassic version but target v4.0, which would need to retarget their app for v4.5. I don't see this as big problem, because if someone has the v4 CLR installed, we can except the BCL to be at least v4.5.2 as this is the minimum supported version (and switching from v3.5 to v4.0 already means Apps which target v3.5 also need to retarget a higher version).

However, of course it is up to you if you want to make that change, I can live with the library targeting v4.0. :-)

from jurassic.