Oh I don't think there's anything wrong with the SilentBootStrapper other than I wanted there to be some indication that the net framework was installing. And I wasn't sure what other types of bootstrapper applications are available because the one thing I thought of happened to be the abstract class that SilentBootstrapper and probably the others are built off of. So I just commented it out and hoped the default one would do so.
And the weekly build for Wix version 3.11 from July 4th does have the Netfx461web tag :D
The only thing that's not doing as its supposed to is that I still need to assign the bootstrapper output file name to it. If I don't it gives two errors with first one saying it exited with a code of -1 and the second one saying "The file name 'setup.exe' creates an insecure bundle. Windows will load unnecessary compatibility shims into a bundle with that file name. These compatibility shims can be DLL hijacked allowing attackers to compromise your customers' computer. Choose a different bundle file name."
Refusing to allow the name setup.exe is like when Microsoft suddenly decided we couldn't write to the directory our program is stored in. Very Annoying. Or when they decided to make it harder to use the registry. Which I ceased using back then because I thought it was going to become impossible like writing to the directory. Though I never returned to using it, I think they backed off that. Or with the new Windows 10 apps where you can't even load or save files without jumping through a gazillion hoops... Which is why I will continue to focus on the desktop till I can't.
Okay done ranting about Microsoft's decisions ;)
WixSharp is awesome. I remember when they first released Wix I was excited to have access to how Microsoft builds MSIs. Then I saw the xml, couldn't understand why anyone would want to type all that, and ran fast back to innosetup. Using c# to build is awesome. (since c# is my favorite language)
I'm not sure how to attach a project to this or Id include it.
And the weekly build for Wix version 3.11 from July 4th does have the Netfx461web tag :D
The only thing that's not doing as its supposed to is that I still need to assign the bootstrapper output file name to it. If I don't it gives two errors with first one saying it exited with a code of -1 and the second one saying "The file name 'setup.exe' creates an insecure bundle. Windows will load unnecessary compatibility shims into a bundle with that file name. These compatibility shims can be DLL hijacked allowing attackers to compromise your customers' computer. Choose a different bundle file name."
Refusing to allow the name setup.exe is like when Microsoft suddenly decided we couldn't write to the directory our program is stored in. Very Annoying. Or when they decided to make it harder to use the registry. Which I ceased using back then because I thought it was going to become impossible like writing to the directory. Though I never returned to using it, I think they backed off that. Or with the new Windows 10 apps where you can't even load or save files without jumping through a gazillion hoops... Which is why I will continue to focus on the desktop till I can't.
Okay done ranting about Microsoft's decisions ;)
WixSharp is awesome. I remember when they first released Wix I was excited to have access to how Microsoft builds MSIs. Then I saw the xml, couldn't understand why anyone would want to type all that, and ran fast back to innosetup. Using c# to build is awesome. (since c# is my favorite language)
I'm not sure how to attach a project to this or Id include it.
