You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Daniel, unfortunately, what you are trying to do is not supported.
If I am not mistaken, you are trying to AOT compile WixSharp.UI.dll assembly and this is what triggers the problem.
For any UI you still have to use .NETFramework
The reason for this is rather logical than technical. If you try to distribute the .NET Core managed UI with your setup it means that it needs to AOT compile it. This, in turn, meant the AOT will try to pack into your native *.aot.dll not only CLR but also complete WinForms (or WPF). Having such fat masi does not make any sense. For UI scenarios you are definitely much better off with te .NET Framework WixSharp build. Remember, all this struggle is because WiX does not support .NET Core. Only .NET Framework
Your setup definition can be .NET Core assembly compiled with AOT switch but the UI is the usual WixSharp custom UI assembly as per any template. You can find the sample for this here.
While I have provided the working sample, I did not create the VS project template for this very scenario as I did want to encourage the users to build UI this way. Simply because I do not believe it offers an adequate dev experience. :(
Scenario 4 is supported as a hybrid solution when the msi is built with .NET Core (currently supported) and the UI is built as a .NET Framework assembly and simply referenced from the msi as an external EmbeddedUI assembly. See this sample.
Was it a typo and it's meant to say "Scenario 5" (Embedded UI)?
Our purpose with upgrading WixSharp to use net8 was because we're upgrading our app from .Net Framework 4.6 to .Net 8.0, and we saw the opportunity to upgrade the installer code too. But it's being a little difficult. Is there any limitation of WixSharp 1.2.6 to deploy applications that are built for .Net 8.0? We're thinking on leaving the installer on an older version than our actual program.
For example I wonder if lines like these would not work 100% of the times as we would be trying to enforce a higher version of .Net than the installer knows about:
Hello,
I'm getting errors like these in the aot.entrypoints.cs file:
Looking at line 98, I see the class name has a backtick:
So the syntax errors seem to be caused by the presence of the type name of a generic class with 1 parameter?
I tried setting the language level in my csproj to
<LangVersion>default</LangVersion>
to use the latest one, but it didn't help.These are the other file names that are giving me syntax erros, some have backticks and some have plus signs:
By the way, there is a typo in the class name
AotEnrtyPoints
instead ofAotEntryPoints
.The Wix# version I'm using is 2.5.1, although I tried 2.3.1 and I get the same error. And I'm targeting
net8.0-windows
Thanks.
The text was updated successfully, but these errors were encountered: