Michael Dietrich

I published a PR that brings the option to define the parsing behavior for command line options, whether to use single or double dashes: #767 Maybe you could consider this...

Oh great, it would be really nice if this could be merged, so there is no need for our dev team to maintain a local fork anymore. I will have...

OK, I updated the PR. There were hard coded occurrences of `--help` and `--version` that I missed before. But now they are also handled correctly in respect to the used...

Same here. I always used quotes, since new MSBuild files in the .NET SDKs also used quotes. If we are now at the point that there was a lot of...

What do you think about adding support for using the `signtool.exe` from these two NuGets? https://www.nuget.org/packages/Microsoft.Windows.SDK.BuildTools https://www.nuget.org/packages/signtool

Yes, the Windows SDK is **not** needed for Nuke to run. Only a matching .NET SDK is needed to run Nuke.

In my opinion it is fine to target these runtimes, since that way it is highly compatible to almost any WPF application out there. As these frameworks are upward compatible...

> Dictionary.cs not found This is the message Visual Studio displays when trying to debug the `ArgumentNullException` to load the source file where the exception occurred, but this has nothing...

OK, it really took me quite some time to understand your problem here. 😅 What we see here is expected. You have to know that `InitializeComponent()` means that the basic...

I always thought this was by design, since the ad-hoc `TextBlock` created by the `ContentPresenter` has no real connection to the surrounding `MainWindow`. Likewise the text within a `ToolTip` would...