• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • FREE workshop: Preparing contractors for Autumn : Weds 29th Sep at 7.15pm. More details here.

InstallShield LE in VS 2012 - How to get relative paths to dependencies

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    InstallShield LE in VS 2012 - How to get relative paths to dependencies

    Putting together an installer for a windows service & have to use the built in InstallShield LE that comes with VS (a steaming pile of cack if I've ever seen one...).

    I just can't work out how to include dependencies - I get the config file & exe included ok by selecting the primary output of the project but the only way I can see to add another dll is to navigate to it & add it. This then leaves you with a hard coded path which is no good.

    I'm sure there's an easy way around this but I'll be buggered if I can find it.

    #2
    After a couple of days of plodding away at trying to create a deployment solution using InstallShield LE I've come to the conclusion that it's a complete waste of space.

    You can't even do half the stuff you could do with the old style VS installer projects and they were pretty neanderthal (ISTR a problem where it would always evaluate the program files directory as c:\program files even if it was on d:\ & you had to edit the setting via Orca once the installer was built).

    Looks like I'm going to have to roll up my sleeves and learn Wix....

    Comment


      #3
      Originally posted by wurzel View Post
      After a couple of days of plodding away at trying to create a deployment solution using InstallShield LE I've come to the conclusion that it's a complete waste of space.

      You can't even do half the stuff you could do with the old style VS installer projects and they were pretty neanderthal (ISTR a problem where it would always evaluate the program files directory as c:\program files even if it was on d:\ & you had to edit the setting via Orca once the installer was built).

      Looks like I'm going to have to roll up my sleeves and learn Wix....
      Since you mentioned this, and the fact that I have had to start leaning WiX as well, there is a nifty tool called WiXEdit, which allows you to create installers using WiX with powerful options like checking for pre-requisities etc. Link: WixEdit
      And this:

      http://blogs.planetsoftware.com.au/p...nd-visual.aspx
      Last edited by tranceporter; 19 March 2013, 12:29.
      I am Brad. I do more than the needful and drive the market rates up by not bobbing my head.

      Comment


        #4
        Originally posted by wurzel View Post
        Looks like I'm going to have to roll up my sleeves and learn Wix....
        Will work inside IR35. Or for food.

        Comment

        Working...
        X