![]() I was part of a team which created a game as their master project. If you want quick and easy, go with Wise or Installshield.In this tutorial I’ll show you a really simple way to get a Windows installer for your Unity game with totally free tools but without any scripting involved in less than ~10 minutes! Intro Do them both at the same time and your in for a long uphill battle.Īs for visual studios, its probably the worlds most "fail" MSI packaging tool surprising being they are both from MS. WiX is very hard to get into if you do not understand MSI first. Re doco for MSI / WiX its pretty poor all over the place, probably because its so complex ppl have limited ability to reproduce this in non techno babble. pay particular attention the following topics and your well on your way to understanding msi You may find this a little easier to interpret. Re your other comments yeah MSDN is fail at explaining things. It is not an easy learning curve nor should it be because it is much much more than a simple single application deployment solution like inno setup. Windows Installer on the other hand is a complex deployment mechanism designed to cater for upgrades, uninstalls, sociability with other applications, rollback, self repair and many many other things all deployment related. It is expressly designed to deploy a single application with complete disregard to anything else that may currently be on your machine. It has limited comprehension of things as upgrades etc. Inno setup is simple script / procedural code delivery. Ok looking at your requirements to handle upgrades etc then I would suggest MSI being the better delivery mechanism for you. XML isn't a big deal, so no worries there, but I would like to be able to easily (relatively speaking) install upgrades with the following major points:Ģ- Not add a new entry in the Add/Remove Programs listģ- Actually understand the upgrade process with MSI a little better.ĭue to time contrainsts I have decided to go back to the standard MSI in Visual Studio.ĭoes anyone kow how to set a file in the installer so it will NOT overwrite the existing version if its found? If I can accomplish that I will have everything need. Last, I spent several days producing a decent installer with Inno so I would rather not abandon that right away- especially if I have to learn something just as complex as the default MSI with VS. I know that may sound simple, but as I mentioned before the "Codes" were confusing me. Next, my original reason for going down this path was that I wanted a simple manner to upgrade inplace installations without creating additional items on the Add/Remove Programs list and without overwriting my data and config files. Second, I was wondering if you guys could help me explore a couple of questions and options on this topic.įor starters, is there good documentation for Wix and Tallow? My biggest frustration with MSI is that the documentation is plentiful- but written in typical MSDN "If You're Not Smart Enough To Understand Our Technospeak, Maybe You Shouldn't Be Doing This" format. Thanks in advance for whatever assistance you can offer.įirst, I REALLY appreciate you taking the time to get back to me on this. Second, if Inno does not support this, how can I get the best of both worlds? Can I package the Setup file from VS to only include the prerequisites AND the Inno setup project once the other pre-reqs are complete? If so, does anyone have some direction on how to accomplish this? Therefore, two questions: First, does anyone know if Inno can do this? If so, can someone cite some examples with brief explanations? Or, is there a better way that somehow incorporates the VS 2008 Setup project? At this time I'm not even sure if Inno can accomplsh this or not. The Windows Installer version would automatically package the prerequisite third-party MSI files, determine if they were needed on the target system, and install accordingly. However, I have run into one problem that I'm not sure how toovercome. I like Inno quite a bit because the scripting lets me have more direct input on the installer (which helps appease my control issues). program codes was giving me a migraine, and I needed a simple solution that allowed clean upgrades. Additionally, the entire concept of upgrade codes vs. Here's my issue: I was initially deploying my software using Windows Installer via the Setup project built into VS 2008, but I found it a little too complicated and I wasn't able to put together the right "feel" for my installer package. ![]() I'm really glad to see that there is a community dedicated to deployment because this is an area I need a lot of knowledge in, and hopefully you folks don't mind teaching someone who is fairly new (and more than a little thick). This is my first post to this message board, so I apologize if I'm asking this in the wrong forum (If so: Admin, please boot be over- thanks!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |