Anyone have luck in packaging Dynamics AX?
Was wondrin if anyone have had any experience by packaging Dynamics AX 4.X client?
If so how did you do it
The installation files contains a native msi file which i was able to get installed by deleting all content under LauncCondtionStatement. But if i now run the program it says somethinh about a missing active x component
If so how did you do it
The installation files contains a native msi file which i was able to get installed by deleting all content under LauncCondtionStatement. But if i now run the program it says somethinh about a missing active x component
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Whenever I re-package, I ALWAYS do a test install using this procedure:
- run my MSI
- start a lightweight snapshotting tool (I use Ziff-Davis's In Control)
- remove any file or registry data that indicates to the original installer that the product is installed
- run the vendor install again
- you *may* want to start the app so that you capture any configuration that it might make
- complete the snapshot
- add any relevant file or registry data to my package
- repeat
This way, I know that my package exactly reproduces the vendor's installation. In your case, I'm willing to bet that the vendor's set-up stub performs a bunch of DLL/OCX registrations.
Lastly, deleting stuff from a vendor-supplied MSI - or making changes of any kind - isn't a good idea. Always use a transform.
- run my MSI
- start a lightweight snapshotting tool (I use Ziff-Davis's In Control)
- remove any file or registry data that indicates to the original installer that the product is installed
- run the vendor install again
- you *may* want to start the app so that you capture any configuration that it might make
- complete the snapshot
- add any relevant file or registry data to my package
- repeat
This way, I know that my package exactly reproduces the vendor's installation. In your case, I'm willing to bet that the vendor's set-up stub performs a bunch of DLL/OCX registrations.
Lastly, deleting stuff from a vendor-supplied MSI - or making changes of any kind - isn't a good idea. Always use a transform.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
