In Visual studio select the ClientApp then set the target CPU architecture to match your system’s architecture (x86 / x64…).
Choose a safe place to temporarily store the certificate generated in the next step then right click and select “Open in Terminal” or CD into that folder (Run command Prompt as Admin may be necessary - untested as yet).
Run the command: "dotnet dev-certs https --export-path ./sidekickapp.pfx --password sidekickapp!@#"
Double click on the certificate and install it for Current User.
Back in Command prompt run: "dotnet dev-certs https --trust"
Win Key + R and run: "certmgr.msc"
In certmgr check the certificate is successfully installed as in the below image with 1 year from your current date as an expiry date on the new certificate...
Select the server app in the solution explorer then in the developer console (ensuring that the file path points to the server app) run:
If dotnet-ef hasn’t already been installed then run: “dotnet tool install --global dotnet-ef“
CD into the SidekickApp_WebAPI project folder.
Set the WebAPI project as the EF startup project by running: “dotnet ef migrations list --project [PathToYourProject.csproj] --startup-project [PathToYourStartupProject]“
Run the migrations: “dotnet ef database update --startup-project [project path]”
Run the Insert into the AspNetUserTokens table using the attached inserts.
Use Visual studio’s SQL Server Object explorer to ensure that in the AspNetUserTokens table the row containing the “user1” record has the value “1234567890“ in the SLT column.
Set your JWT_SECRET_KEY by going into your PC’s Environment variables and adding it manually as a System variable