Replies: 6 comments 9 replies
-
here's the error output from the new executable:
|
Beta Was this translation helpful? Give feedback.
-
Correct. MSI/WiX cannot work with .NET Core assemblies (e.g. .NET 8.0) so you need to use .NET Framework as a target. A simple hint - use VS templates for WixSharp. They will give you the project that is already properly prepared for the WixSharp build. |
Beta Was this translation helpful? Give feedback.
-
If I want to "automagically" populate the "MyProduct","My Company","My Company" values is my little helper app the best way to do that? or is there an exposure of the "main project" that I'm missing? |
Beta Was this translation helpful? Give feedback.
-
Here's my dependency list All the build stuff is superfluous now I think.. but.. yeah.. |
Beta Was this translation helpful? Give feedback.
-
Yeah, despite all my hopes I cannot say WPF is flawless. Don't get me wrong, it's not beta, it's done as it's supposed to be done, to the level of the production code strength. But the overall outcome is not at the same level. The problem is that at runtime because WPF dialog is hosted in WinForms some "strange and wonderful" stuff is happening. I think it was you @smaudet who reported it. And we could not find any work around it. Thus if you tested WPF and it works fine then there is a good chance it will always be fine. But if you see some artifacts then it's unlikely you can solve them. From this perspective, WinForms is a safer choice. |
Beta Was this translation helpful? Give feedback.
-
While it is possible, it's not what The answer @smaudet gave you is exactly on the point: |
Beta Was this translation helpful? Give feedback.
-
Good Morning All!
I've got a couple issues I'm trying to understand.
I've built a .NET 8.0 application. When I build it I rearrange output files into appropriate folders -- the build folder pretty much exactly represents where/how I want the app output into the user's target directory.
While I've manually set the assembly to .net 8.0, I'm getting the feeling we're not compatible.
Here's my project file:
and my Program.cs:
I've built a helper class to read the info from the main App.cs so i can build them together.
They all
kindawork.\bin\Debug\net8.0-windows\win-x86 gets created, but instead of following by debug folder structure, it is the messy garbage that was before my cleanup stage (created a lib folder and a locale folder to hold all the extraneous dlls and language elements)
I see the new installer exe/dll alongside my program files here, but i'm still getting errors in output:
Do I need to be building a different template? Is there something in the build process I can do here, similar to what I do in my source project, where I do directory cleanup before we build the msi?
Thanks in advance!!
Beta Was this translation helpful? Give feedback.
All reactions