| GitHub | https://github.com/filipnavara |
#JetBrains is running a 65% off the first year for #JetBrainsRider. That’s $4/mo! 😱
We also offer perpetual fallback licenses. This should get you into the #dotnet 8 era for development on #Windows, #Linux, and #macOS.
Rider supports #aspnetcore, @avaloniaui, #MAUI, #Unity, and other .NET stuff.
Check it out before firing up the grill for Labor Day. 🇺🇸🌭🍺
I just learned from Marc Gravell that these are false:
Version.Parse("6.0") >= Version.Parse("6.0.0")
Version.Parse("6.0.0") >= Version.Parse("6.0.0.0")
And these are true:
Version.Parse("6.0.0") >= Version.Parse("6.0.0")
Version.Parse("6.0") < Version.Parse("6.0.0")
Version.Parse("6.0.0") < Version.Parse("6.0.0.0")
I'm gonna need more coffee.
"Your Apple ID has been locked."
I don't like it, Apple. There's 2FA enabled but it still randomly decided to lock the account. So, you have to unlock it, change the password, which invalidates all the app-specific passwords... because hey, we are Apple, it's 2023, and we still don't do OAuth. #apple
#rant
We had a NuGet dependency that was ordered before a certain target. If the NuGet was not restored first, then the build failed. This was not a problem on command line but in VS IDE it create a chicken-and-egg dependency problem.
Once we figured out the root cause a simple `Condition="'$(DesignTimeBuild)' != 'true'"` addition fixed the design time build. This allowed the NuGet Restore in VS IDE to proceed and correctly resolve all PackageReferences.
The output of the build is fed into the built-in NuGet restore pipeline. If the design time build fails, then you can get incomplete restore. All of this is open source and documented, but also very complex! (https://github.com/dotnet/project-system; https://github.com/NuGet/NuGet.Client/tree/dev/src/NuGet.Clients/NuGet.PackageManagement.VisualStudio)
Notoriously, this works differently from `dotnet restore`, `msbuild /restore`, or `msbuild /t:Restore`.
Jerome Laban
Khalid ⚡
Nick Craver
