I just created the following post, and then saw your newer post, but I'll post it here as it outlines the process, seemingly pointless process!
Thanks for the offer of help...I suspect I'm going to need it, but I'll give another try and let you know.
I'll try it again with the updated info you have provided, I was certain I had tried that, but may have missed a step.
Okay, I'm confused now, so here is what I'm doing.
1) I download spark.exe
2) I install spark so I can edit the default.properties within the spark.jar (I use 7zip)
3) I now have my custom version of the spark.jar which I save someplace else for now
4) I uninstall spark.exe and clean-up
5) I run AppDeploy, select "Create a MSI..." and point it at the spark.exe I downloaded, which obviously still has the stock spark.jar, so I already starting wonder how this going to work.
6) I click "Next" and then was hoping to see something that would allow me to add in my spark.jar file (I've tried Advanced etc), I see no option for this so except the defaults
7) I then launch spark.exe from within AppDeploy and run through the installer, and as the installer is running I can see it extracting the various files...spark.jar etc etc...hmmm..I think to myself, this is not going to work as that is the original spark.jar compiled into spark.exe
8) Click "Next" to create second snapshot, I accept the defaults, and to cut a long story short, it completes and I have a nice spark.msi, unfortunately just as I suspect, it does not have my spark.jar in it.
I have tried various differnet options and approaches and cannot get it to do what I need...and this makes me believe I have to compile my spark.jar into a new spark.exe...I'm obviously missing something, as Church seems to have used AppDeploy to do this.