search

firegiant / HeatWaveSupport

Issues-only repository to report HeatWave bugs and feature requests to FireGiant
3 stars 0 forks source link

A simple way to execute a built Installer (.msi) would be helpful #11

Open ghost opened 1 year ago

ghost commented 1 year ago

HeatWave Version

0.9.0.5

What's your idea?

I'm using HeatWave to build a Windows Installer Package (.msi).

It would be helpful for me doing this, if I could start the build .msi from the Visual Studio IDE (devenv.exe) directly. Maybe with menu Debug -> Start without debugging (Ctrl+F5).

Ok, I can add my own external tool inside the IDE with an execution of msiexec.exe, but maybe I'm not the only one how want's to have this feature?

If you should implement it, I would be nice to have additional start options like add MSIFASTINSTALL=1 not prevent the system restore point creation while development.

chrpai commented 1 year ago

@NilsHoyer it's very dangerous to run an installer thats still under development on your own machine. It's best to run it on a VM or in a sandbox. The only time I ever find myself wanting to run it on my own machine is when I'm working on UI. I'll comment out all the features and components to get a super fast build, run, test the UI and cancel before installing. Nothing gets installed on my machine until I have a degree in confidence that it's not going to make me rebuild my machine.

And I'm someone who knows the tricks to get blocked uninstalls to uninstall. Other people are going to have a higher risk of needing a rebuild.

FireGiantHelp commented 1 year ago

This is an idea we have on our backlog. Thank you for opening the issue. We'll consider this issue a vote in favor of the idea. 👍

ghost commented 9 months ago

Why are you not able to start an external program from inside devenv.exe, since other people are able to do this?