Hey friends, if you have been enjoying my series with @stephentoub on “deep .net” then please come to this “highly technical talk” (that’s literally the title!) be sure to rate it after the session so leadership knows that highly technical talks are valuable! #msbuildhttps://msft.it/6017YXyZH
It's a bit of a conflicting situation because it happens at the same time of my lab😁, but this session from @Jthake and @barnambora is one you don't want to miss! Get an overview of all the Copilot customization capabilities: plugins, connectors, custom copilots and many more! https://t.co/6pQy0FpBH9#copilot#microsoft365#msbuild
This is some deep lore, but what I'm doing here is orchestrating the publishing of a #dotnet Web application into 4 OCI containers, pivoting on
2 user-facing tag names
2 architectures
and building+publishing those in parallel. From there, I'm gathering those container names and creating 'multi-arch' manifests - so users can use the nice names without the architectures.
So, like many #GameDev#programming folks, I'm doing a bit of saturday work from home to support the project as it is getting closer to release.
Since my home desktop is primarily a #Linux system, I decided to try and see if I could compile a #Windows game without Windows.
Short answer: No. I could not.
There is actually an #AUR package that gives you a working #MSVC compiler in #Wine, but there is no way to get #MSBuild to work to build .sln and .vcxproj files.
I wonder how much worse the build time would be in a VM 🤔
Will probably move to a company GitHub soon-ish. I cleaned up a lot of my trial-and-error but there's testing needed to be done on Windows targeting both .NET Fx 4.8 and .NET 7.0.
Still some bugs, e.g., version information not being displayed in the splash screen and weirdly the upgrade-tool put the version info from one of the sub-projects into the metadata of the main project... but those are minor things.
I have multiple projects that can support net7.0-windows on, well Windows, and net48 on Windows and Unix (through #Mono) in one solution. This works fine if I build #Linux on Linux and #Windows on Windows, but if I choose to specify the target OS using dotnet build --os or the runtime dotnet build --runtimeexplicitly (they both amount to the same thing), either for cross-compilation or even when it matches the host, this breaks horribly since specifying a RID (Runtime Identifier) on solution level is not possible since .NET 5.0 and errors with #NETSDK1134. This is well-known and there's also a really weird workaround:
While the connection dialog (https://github.com/rusanu/dataconnectiondialog) wouldn't allow me to select SQL Server Authentication initially, editing the FOCA.exe.config to set Integrated Security=false in connectionString (which allows using something different than Windows Authentication/NTLM) fixed that issue.
Unfortunately, after logging in with user name to "SA" and logging in with the password, it instantly crashes. Starting it again, it instantly hangs. It does work through #wine though.
/usr/lib/mono/msbuild/Current/bin/NuGet.targets(131,5): error : 'base-devel' is not a valid version string. [/path/to/my.sln]
/usr/lib/mono/msbuild/Current/bin/NuGet.targets(131,5): error : Parameter name: value [/path/to/mysln]
Done Building Project "/path/to/my.sln" (Restore target(s)) -- FAILED.
Guess which file does not contain the string 'base-devel' nor does any file in the whole directory? Hmmmmm?
We will be recording a new #iACast episode today discussing everything from #MSBuild, #FinalCutProIpad, #LogicProiPad, and the changes coming to streaming services. I hope you will join our live strem, which I will post later today.
It’s up! The #MsBuild closing keynote, “Scott and Mark learn to code” with me and @markrussinovichhttps://aka.ms/build/ScottandMark we write a multiplayer game in an unfamiliar language live on stage with GitHub copilot in Visual Studio. This is the most fun I’ve ever had presenting