-
Notifications
You must be signed in to change notification settings - Fork 0
Getting Started
This project requires VS Code, .NET 5, Docker Desktop running Kubernetes, a Docker Hub account, and Insomnia or Postman. All of these tools and accounts are free to create or obtain.
Also, because I'm not on a Microsoft machine I had to apply some extensions to make adding NuGet packages easier, specifically NuGet Package Manager GUI v1.1.8. Along with that extension, I added the Docker v1.17.0 to VSCode to make it easier to see when containers were running or stopped.
Finally, the following packages are required. Utilizing the NuGet Package Manager GUI, packages are automatically added to the project's .csproj file:
- AutoMapper.Extensions.Microsoft.DependencyInjection
- Microsoft.EntityFrameworkCore
- Microsoft.EntityFrameworkCore.SqlServer ONLY IF USING WINDOWS OS
- Microsoft.EntityFrameworkCore.Design
- Microsoft.EntityFrameworkCore.InMemory THIS IS TO CREATE THE DB INTERNALLY TO BEGIN WITH I also included, because as noted in the next section there were issues with the building, though I'm not sure it's necessary after updating the terminal:
- Microsoft.AspNetCore.Mvc.NewtonsoftJson
- Newtonsoft.Json
My machine is running macOS Catalina, which uses zsh as its default interactive shell. This is important to note because without this update timestamp signatures for .NET packages will not be accepted, NU3037 and/or NU3038 are errors I kept getting. See the following note from my Terminal that provides instructions on the update:
"To update your account to use zsh, please run
chsh -s /bin/zsh. For more details, please visit https://support.apple.com/kb/HT208050."
After resolving the build issues with my project, localhost was inaccessible via Chrome and Safari because of an untrusted SSL certificate. This is in part because of Catalina's more robust security features, so I followed steps from the following link to get past this issue. https://expeditedsecurity.com/blog/localhost-ssl-fix/
Without this step, I'm not sure there is a way to consistently allow localhost access. As a developer building skills, this is just an annoyance I was not willing to bear with repeated testing.