search

MarimerLLC / cslaforum

Discussion forum for CSLA .NET
https://cslanet.com
Other
31 stars 6 forks source link

Good news and bad news about v4.8.100 #622

Open rockfordlhotka opened 6 years ago

rockfordlhotka commented 6 years ago

So the good news about 4.8.100 is that it'll get us back to a simpler world where there's only one CSLA-Core package in NuGet.

The bad news is that this is (obviously) a breaking change that'll affect anyone currently referencing the CSLA-Core-NS package. To upgrade you'll need to remove the old package and reference CSLA-Core.

This is, btw, why this next release is 4.8.x instead of another 4.7.x...

The NuGet change is tracked by https://github.com/MarimerLLC/csla/issues/927

ajj7060 commented 6 years ago

It really wasn't that big of an issue to switch to the -NS packages so I don't imagine this will be an issue either.

Off-topic, is there a plan to use SemVer for Csla at some point?

ajj7060 commented 6 years ago

So does this mean we can just have NS20 libraries and use them on Full .net as well as Xamarin, asp.net (full) etc?

rockfordlhotka commented 6 years ago

@ajj7060 it means we have just one set of packages.

As long as I have a .NET Framework assembly in the CSLA-Core package, that's what any .NET Framework project will use. And until everyone has migrated to .NET 4.7.2+ I'll need to keep old .NET Framework assemblies in that package.

So for the next several years at least I'll be building Csla.dll for .NET Framework and .NET Standard both.

But nobody should really care now that it is back into a single CSLA-Core package.

rockfordlhotka commented 6 years ago

Regarding SemVer, I have been thinking about that, yes. Silverlight was the problem originally, because it didn't honor the build number (major.minor.release.build). But Silverlight is out of the picture, and I believe .NET Framework and .NET Standard both support all 4 parts of the version.

Maybe I'll try that with the new 4.8.x release, as it would be nice!