Forum Discussion
Add custom installation in specified directory along with registry entry
AtulD OK then!
- Deploying dll components for use by non-containerized applications outside the container they are delivered in is not supported at this time.
- Depending on the type of COM registration, those might be available external to the container, and depending on their internal design (i.e. does the software inside the COM require access to package registry once activated) might work.
- There is the possibility of creating a dependency (or maybe framework, I'm not sure which term applies here) package with shared components. If you look on your system you'll see these for things like .net packages and vcruntime packages. Each package that requires this would need to list it as a dependency in the manifest.
- Microsoft has discussed the possibility in the future of defining a group of packages that should run together in a single container, but not provided details or dates (to my knowledge).
Newer is better when it comes to runtime, so stay working with 2004. You'll eventually need to test on back-rev OS due to the COM, but I'd start here.
Thank you TIMOTHY_MANGAN
You are correct but some other applications are dependent on some of the DLL and registry entry and i want to deploy when we installing the app and and i want to remove those registry entry and other folder when uninstalling the application just like MSI work.
This can be achieved using InstallShield suit but we can not distribute them with web browser.
I am looking the solution which can install both from the web browser.
Your inputs most welcome.
AtulD OK then!
- Deploying dll components for use by non-containerized applications outside the container they are delivered in is not supported at this time.
- Depending on the type of COM registration, those might be available external to the container, and depending on their internal design (i.e. does the software inside the COM require access to package registry once activated) might work.
- There is the possibility of creating a dependency (or maybe framework, I'm not sure which term applies here) package with shared components. If you look on your system you'll see these for things like .net packages and vcruntime packages. Each package that requires this would need to list it as a dependency in the manifest.
- Microsoft has discussed the possibility in the future of defining a group of packages that should run together in a single container, but not provided details or dates (to my knowledge).
Newer is better when it comes to runtime, so stay working with 2004. You'll eventually need to test on back-rev OS due to the COM, but I'd start here.