Multi-targeting source code packages with Nuget

 
event

Time goes on and change is constant. What we thought it worked, it may not now; sometimes for a good reason, sometimes not.

This time I'll dig on what I had to do to attach code to a solution, even if the solution is targeting the classic .NET Framework (net)or the newer .NET Core Framework (netcore). Because that is what I had to do myself.

share
comment
  class ,

NMoneys serialization gets a lifting

 
event

After migrating NMoneys (and NMoneys.Exchange) to support .NET Core it is time to lend a little love to the support for serialization via third-party serialization libraries.

This support operates in a very different way than the usual: 1. install package 2. some library is referenced 3. time to code against that library as it comes in the shape of source code that are added to your solution and compiled as part of it.

share
comment
  class , ,

Migrating libraries to .NET Core. Post-mortem 2

 
event

I have already gone through some of the choices I considered when porting my Open Source Libraries to support the .NET Core platform.

Let's dive into details of each of them, as each has its own peculiarities.

share
comment
  class , ,

Got change?

 
event

This is a honest question for which, fortunately, there is an answer now.
I am sure that there was one before, but sure as well that NMoneys could not provide an answer easily.

Until now.

share
comment
  class ,

Migrating libraries to .NET Core. Post-mortem 1

 
event

I recently went about the task of migrating most of my OSS libraries to the "new" .NET Core platform.

I would like to share with others some of the choices I made and the motivations I had. Besides, I also want to reflect about the pains and gains of doing so.

share
comment
  class , ,