Installing tools
- Visual Studio 17.14.* or greater
- dotnet sdk
Check that you have the latest SDK, currently 9.0.304
If not, Install sdk
- Install Github CLI
For windows:
Note: This will also upgrade existing installations of the gh cli*.
You can also install using choco:
- Remove older Aspire
See Upgrade your development environment for details.
Check for workloads:
Following these instructions
Use Windows Search to find the Visual Studio Installer. Choose Modify on the current version (which should now me the latest), then select Individual COmponents, and enter “aspire” in the search box. Just remove the checkmark for that, and start the install. It will then run for a minute or two, and the it will be removed. Check again that the dotnet workload list now are empty.
How to convert an existing Api to Aspire
For documentation on this see Add Aspire to Existing-App
How to list remotes for multiple git repositories
Background
When you have been working with git over some time, you end up with a lot of repositories. Many of them will be connected with your favourite remote site, Azure DevOps, GitHub, Gitlab, BitBucket or something else, and some will be local only.
You will normally have them organized under some common folder. The state of the repositories will be different. Some of the folders under this common root may not even be a repository. And you might have organized them into subfolders, per application or per company or whatever.
How to conditionally fail a build in Pull Requests with TFS/VSTS
When you have a build that is used for CI also covering pull requests (PR), you often want to enable more checks before you let this go into the master (or any target) branch. It can be extra tests you want to run, or, you might want to block the PR if you have warnings, e.g. from tests.
Setting a single test task to fail could be done, but that only works well if you have a single step, with multiple you can have build stops for one and every step, so it also reduces the error reporting granularity. And, it is nice to be able to see what is an absolutely blocker, red, and what is quality issues, yellow.
You can achieve this by adding a standard command line task that fails given these conditions.
How to Recipes
The “How to recipes” are short solutions to a problem, not delving into the why and how like I would do with an ordinary blog post. The recipe will contain links for further reading.
https://hermit.no/net-core-setup/
https://hermit.no/findclear-nuget-caches/
https://hermit.no/get-nunit3testadapter-pre-release-packages/
https://hermit.no/enabledisable-user-dumps/
https://hermit.no/trick-fixing-strange-missing-project-json-error-old-csproj-format/