Repair during running another application
Hello, I've packaged two applications.
The first application is already deployed to over 5000 machines.
Now, if I deploy the second application, it cuases at every start of it a configuration "reapir" of the first application.
If I start the second application as administrator, the repair action does not occure! Can somebody tell me why it not occurs when I run as admin?
I think it's a conflict of the registered components of the packages..
Is there a way to resolve the problem, without repackaging and deploying the first application again?
Thank you very much!
Answers (6)
Sry, I removed the last question because it wasn't defined clearly..
I find out which component is causing the repair. It's a dll-file in "C:\Windows\microsoft.net\assemblys\GAC_MSIL\". My problem is that I don't really know what I have to do in the second application-package, because there is no same component represent in the second package.
Thank you very much.
Comments:
-
Did you repackage the application? - jaybee96 11 years ago
The component that is causing the repair is from the first app ( because it is repairing..)
This means that somehow your first package includes .net info that you repackaged with the app?
You could create a Patch / upgrade for the first package to clean up .. but I would know for sure when I could see your repackaged MSI (no.1)