Vitek Karas

[Damian Edwards @DamianEdwards]

It's an exciting release day today! #dotnet 8 Preview 3 brings with it the first support for native AOT deployment of #aspnetcore apps! Go read about the details right now & try it out for yourself! https://t.co/XbBYGc8KgA

[Vitek Karas @vkaras]

@jjoergensen @ScottDotMS @philiplaureano And WPF specifically is currently really problematic, you should get an error trying to trim WPF app currently.

[Vitek Karas @vkaras]

@jjoergensen @ScottDotMS @philiplaureano Default behavior is that only assemblies which have AssemblyMetadata("IsTrimmable", "True") attribute are fully trimmed. Trim problems are global though - if there's a reflection code somewhere in the app which is not understood, it can break anything. https://t.co/KQph71VtQq

[Vitek Karas @vkaras]

@evocationist @davidfowl RequiresUnreferencedCodeAttribute https://t.co/VzLIBTW2ky

[Vitek Karas @vkaras]

@SitnikAdam That would be tricky. Apparently one needs to look at molars. Also as a horse owner, please do not feed a horse without owner's agreement. (you don't know if it could hurt it).

[Vitek Karas @vkaras]

@SitnikAdam Wife: look at its teeth. 😁

[Vitek Karas @vkaras]

@Nick_Craver Which dotnet is it running? The one from Windows or one from WSL? Just run dotnet --info to tell.

[Vitek Karas @vkaras]

@rickbrewPDN @Donny_V Single file should work, but not trimming.

[Vitek Karas @vkaras]

@__matr It's your release as well!

[Steve Carroll @ScareAll]

ok, finished first draft of Czech name pronunciation for English speakers section. Czechs, if english speakers butcher your name, can you please reply with your name so I can check it against my guide and maybe add to the example list? https://t.co/fvm1mWCyR8

[Vitek Karas @vkaras]

@SitnikAdam It was a good talk... Good job 👍

[Vitek Karas @vkaras]

@lucasmeijer @runfaster2000 @terrajobst Yes - that is correct. (unless you also enable trimming which could strip the original R2R data and without ability to rebuild it you would lose it for more/most assemblies).

[Vitek Karas @vkaras]

@marcindeptula @raffaeler @ugidotnet Aaron who is one of the owners of interop in .NET Core created a project to do exactly that. It basically generates the necessary native code (along with the CoreCLR hosting) for you. Let us know if this works for you: https://t.co/eZl5TcGcBE

[Vitek Karas @vkaras]

@xoofx @terrajobst @runfaster2000 Is your app in VB? If so this is not very surprising, there's lot of work left to make even the core framework behave correctly in all cases with member-level trimming.

[Vitek Karas @vkaras]

@Nick_Craver It might work for you to include build.proj and define how to run the built project. See for example https://t.co/vIy2IUWA9E. The property RunCommand should make the project "runnable".

[Vitek Karas @vkaras]

@runfaster2000 @gcaughey @DamianEdwards Agreed. I was providing more a "workaround" than a solution :-)

[Vitek Karas @vkaras]

@gcaughey @runfaster2000 @DamianEdwards I guess that depends on what kind of apps - services and such should be easy as they are typically started by some script (and thus easy to tweak the env. for). UI apps are different and we don't have a good solution for those yet.

[Vitek Karas @vkaras]

@gcaughey @runfaster2000 @DamianEdwards It's possible to do this today with env. variables. Build the apps as framework dependent, then download the binaries (.zip) into any folder and then set DOTNET_ROOT=folder. Run the app via .exe and it will work. Updating the docs with it here: https://t.co/Kc5ItHH4Xw

[Vitek Karas @vkaras]

@lafp 🙂

[Matt Warren @matthewwarren]

This is pretty cool, an ETW event is being added to .NET Core that will give info about 'Assembly Loading' successes/failures https://t.co/jArzp3YpLR