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.
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.
Tools are important in the daily work of a developer (as they are in any other handcraft). The better tools one have the less effort should be needed, with the added plus of getting a lot more done and unlocking scenarios that, without them, would be close to impossible.
Sometimes (more often than not, fortunately enough), things work as they should and one feels the warmth that things done the right way bring.
Ok, now I am writing this while I am still angry. I know I shouldn't, but I really can't help it.
I have been using Visual Studio since it's been RTM.
Call me a chicken, cheap or whatever you like, fut I have always felt weird doing QA for Microsoft for free. So I did not use their CTPs or Betas that much and therefore I did not submit any suggestion or reported any bug. Should I complain then? Absolutely YES.
At work we migrated our 2.0 solution from Visual Studio 2005 to a Visual Studio 2008.
I have successfully migrated myself some pet projects (both library projects and web application projects). I had not tested migrating Visual Studio Tests projects since I don't use them myself, preferring the faster, more stable and extensible NUnit.