I had recently wanted to enrich a datasource with some preconfigured metadata. In order to this I used the Newtonsoft Json.NET library. The unit test demo below contains an example that can take a JSON string or by taking C# objects. The results should look as follows:

Configure your .CSProj File The .csproj file you wish to target for building as a Nuget package will need the PackageId and Version properties at a minimum in order to work. See here for more details: https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package-dotnet-cli 1) Get Nuget API Key https://www.nuget.org/account/apikeys 2) Add the key to your GitHub While at the root of your repository, go to Settings located in the top navbar then on the next page, proceed to Secrets…

Just a very quick one with Preview5. I encountered this gotcha whereby the project's name in the solution explorer doesn't match that of the folder name. I'd had a change of heart on the project name but of course the folder on disk doesn't change automatically. Once I'd renamed the folder and then proceeded to fix the path in the .sln file this error went away. tl;dr project folder name and project name in the solution explorer seemingly have to match up at present

Using GitLab to host both the source control and perform CI/CD, we will take a blazor project and build it and then proceed to deploy it on Netlify. This article presumes that you have some familiarity with the following: GitLab for source control (See here) GitLab for CI/CD (See here) Netlify CLI for deployment (See here) 1. Using the current SDK 3.0.100-preview4-011223 (See here), create a new blazor (client-side) project called 'testproj': Now create a file called .gitlab-ci.yml and add it to…

On the odd occasion you wish to debug Seed method code which has been executed from the Package Manager Console using the Update-Database command, a quick and dirty method is to add the following code: Yes it's dirty! It will however fire up a new Visual Studio debug window and allow you to see what's going on inside. This method will also work for any code that happens to sit outside of a normal debugging scenario.