Results 1 to 5 of 5

Thread: Need help with Visual Studio Installer 1.1

  1. #1

    Thread Starter
    New Member
    Join Date
    Jul 2004
    Location
    Belgium
    Posts
    2

    Need help with Visual Studio Installer 1.1

    Hi,
    I use VSI 1.1 to distribute a VB6.0 application. I have included in the install procedure some non critical text files used by the application. My application deletes on specific conditions some of these files. When this happen, the next time I will run the application, the installer start en put the deleted file back. This is not what I will, and for the end-user it is not so nice, because the installer need the installing CD. I cane suppose that this feature is very helpful with critical files, but cane somebody tell me how to disable this feature for certain files?

    Best regards,
    Vic

  2. #2
    Addicted Member
    Join Date
    Jan 1999
    Posts
    239
    Instead of deleting the files, why don't you create a temproary directory and send them there.

  3. #3
    Addicted Member
    Join Date
    Aug 2002
    Location
    Michigan
    Posts
    181
    I doubt that it can be done. I just checked the VSI help file. There are several properties you can manipulate; none of them appear relevant.

    The Windows Installer maintains a database of all components and reinstalls if any of them are deleted or currupted.

    If you zip your .msi file and make a self extracting.exe, you can preserve the installer in a special folder. Then, if it goes home to momma, the user will not need to hunt for the cd.

    If you want the file to be optional, don't install it!! Add code to your program to create the file if it is needed.

  4. #4

    Thread Starter
    New Member
    Join Date
    Jul 2004
    Location
    Belgium
    Posts
    2
    Hi,
    Thanks for this fast replay. Move the file to a temp instead of deleting is not an option because the file isn’t anymore on the same place and the installer will try to ‘repair’ its application. I think, like Ben mention, will be the best work around. Not install the option files with the installer but on the very first run of the application via code place then on the right place.
    If there is somebody with a better idée I will very grateful.

    Best regards
    Vic

  5. #5
    Hyperactive Member
    Join Date
    Feb 2001
    Posts
    280
    hi,

    err - I have no specific answer but I think that this is work loojking at....

    http://msdn.microsoft.com/library/de..._reference.asp

    (But - Firstly search MS's site for "orca" and download and install it - this allows U to update msi properties once U have authored the install package. (or in C:\Program Files\Microsoft SDK\Bin\Orca.Msi) in the platform sdk).

    I would have a look at the reinstall list property - this seems to be a list of object that are "re-installed"......

    perhaps your text files are mentioned here - and perhaps removing them will stop Vsi from rebuilding them of U delete after install..

    If not, then there are so many properties - im sure one of them will help...

    dunno - U will have to have a play - hope that helps some,

    cheers AJP
    Intel 486dx3 - VB4 - DR-Dos - 2mb EdoRam - 2x CDrom drive - Window for Workgroups - CGA monitor

    Real programmers use less....

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width