Well It's been a while, and I've resorted to asking some of you out there. There seems to be something wrong with the new repackager tool. Captures are good, but when we want to convert it into and ISM file, it deletes all the folder in the same directory as the IRP file is. Has anyone bumped into this? We are currently using Admin Studio 11.

Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment



I am also using this same tol but have not faced this issue ever.

Can you check your settings.

Answered 10/03/2012 by: piyushnasa
Red Belt

  • im not sure which settings though, both me and my colleagues are facing a dead end over this, basically we have an IRP, after some deletions of unwanted files etc, we build the ISM, if the ISM is to be stored in a subdirectory of the IRP, its fine but if under the same dir as the IRP, it deletes the entire folders in it.
  • Yeah.. that is how it is built. It will create all the files into cab format inside the MSI so all the folders outside will be deleted. We create a different subfolder to create ISM. That is how you can preserve it. Why do you want to create it in the same folder anyways?
Please log in to comment

Correct,  you should create a separate folder to place the ISM (and MSI's) in to work efficient and clean: (are you a former Wise user?)

I am using the following:
> Projects
  > ApplicationVendor-App.Name-AppVersion
     > 1_DOC  (documentation)
     > 2_SRC  (Your sourcefiles, legacy setup etc..)
     > 3_IRP ( your Captured installation)
     > 4_ISM (your Projectfile + first MSI's)
     > 5_MSI (Your "in production MSI")
     > 6_VIRT  (Your Virtual Package )


Answered 10/04/2012 by: jaybee96
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity