You need to decide whether you want to update the existing library or create a new one. Creating a New Project vs Using an Existing One Be sure to use branching or some other versioning system so you can get back to the original code if things aren’t working out. If you’re using GitHub, Azure DevOps (VSTS/TFS) or any other source control system then you should be fine. NET Standard then you are ready to start making changes. NET Standard doesn’t mean you cannot use older libraries. As discussed here libraries built against newer versions of the. NET Core and therefore would not benefit from being replatformed to. This would include any library that specifically targets WCF or ASP.NET. Firstly you should evaluate whether this is even a good idea. I’m going to document that process here because I think my upgrade path is going to be very similar for others.īefore you begin you should do a couple preliminary steps.
NET Core it is time for me to upgrade Kraken to. NET Standard 2.0 is out and my company is looking at moving to. Prior to that I ran my own private NuGet server where I hosted the packages and used them in my projects. The entire source code is available on Github and I have recently been pushing builds to NuGet. It has evolved over the years to support new featuers as. If you aren’t aware, Kraken is my personal class library that I’ve been using since the early days of.
0 kommentar(er)
