winsxs and side by side issues in msi
we are working on sage 100 for one of our client.
it is a suite of applications and we have to install only 3 sub products in it. for two sub products we have found the solution , for one product we are not successful in creating response files(weird behavior it install only on the machine where we have created it)
we tried capturing the application and ended up in error related to winsxs folder. application is writing application related files in this folder. i am sure it is not any vc++ files.
we tried to find merge modules for this files to overcome issue related to winsxs but in vain.
if we retain winsxs file as such in the msi, when we install the package it is getting installed in c:\windows instead of c:\windows\winsxs folder. when laucnhing the application it fails with side by side error and when we checked in event vwr it points to applcation related file in winsxs.
any sugesstion on how to overcome this issue.
the application needs vc++ as dependency i have taken care of removing all the files related to vc++ from my application.But application itself is writing some files in winsxs folder. for e.g one such file is sage100.core.runtime.dll. upon deleting the files from winsxs we are receiving errors while launching the shortcut.
the error is related to side by side, saying side by side configuration is incorrect. unfortunately i could not install it silently using response file and i could not contact the vendor also.
i removed vc++ entries from the package. but my application itself is writing some files to winsxs folder for e.g sage100.core.runtime.dll.
i tried not to repackage it since there are embedded msi's in it but i see no solution to it.
we created response file but as i said earlierr in my post it is not working either.
I done a bit of work packaging sage as well, hopefully the following will help. I think I had a similar problem to the one you're describing. Have you tried disabling/deleting the winsxs folder through your packaging program and then deploying the Visual C++ packages? I've also noticed that some of the VC++ and/or program needed VC++ updates from Windows Updates but these can be deployed as well.(at least the ones i was looking at could be.)
Let me know how that works please.