2016-08-21 18:28 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > Hi > > I've got a bunch of questions about the .NET Core build and before I > spend more time searching for the anwers I though I may as well ask for > help. > > Version > ======= > > The current version is set as 3.0.0 - why? log4net's next assembly > version is 1.2.16. I know the nuget package uses 2.x - probably because > it changed the major version when it switched to the new key - but > adding another platform shouldn't require a new major version IMHO. >
I was puzzled by 3.0.0 too. We could however use the opportunity to line up all the different version numbers between the codebase, nuget and .net core extension. > > 4.x Builds > ========== > > On my Linux box it builds assemblies for net40 and net45 as well. Are > these assemblies expected to be the same as the assemblies we build > using NAnt? If so, I may be able to use the net45 version built by the > dotnet too as NAnt really doesn't seem to want to use 4.5 for me. > I can build the net40 and net45 assemblies on my windows 7 machine. We could then compare binary compatibility and a few other things to double check if these binaries are the same. md5 won't do because of the meta data changes that are written into the binary on every build. > > Signing > ======= > > I'd like to see strong named assemblies using "the new key" is this > supported? > .NET core supports also strong named assemblies. At least there are a few strong named assemblies out there and a few that are not strong named too. A quick hack in the search engine brought up a few results. -- Dominik Psenner
