![]() ![]() 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 |