The Watch2 NuGet package project now has interfaces,making it test-friendly and ready for action. To make life easier,we’ve sprinkled some Dependency Injection (DI) magic throughout the project. Classes have been refactored to embrace constructor injection,ensuring all necessary interfaces are on board. The DI container has been set up in `Program.cs`,making dependency resolution a breeze. The…

Now I want to do build and auto-deployment as a Nuget Package( at https://www.nuget.org/packages/watch2 ) The most simple build action on GitHub Actions is simple example of how to do it. However,I want to do more than that. I want to build,test and deploy on demand the Nuget package to Nuget.org. However,the building should be…

The Watch2 just intercepts the dotnet watch,adds a clear console,and a delay to give a breather between running the app and the tests. So I need to have tests – if I want to be sure what the software does and to modify it without summoning the coding gremlins. More importantly,the output from dotnet watch…

The first attempt to writing the code was very fast – and,surely,not testable. (Speedy Gonzales would be proud!) Some observations: 1. If you start any process inside a console application,you should intercept the cancel signal and stop the process. This is done by using the CancelKeyPress event of the Console class. This is important because…

I frequently use .NET Watch for two main reasons: Running .NET applications during development. Executing tests. Seriously,if you haven’t tried .NET Watch,you’re missing out. It’s like having a personal assistant who never sleeps compiling code . For more info,check out Microsoft’s documentation  at https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-watch But,like all good things,it comes with a couple of quirks: The…