Thank you. Yes, we are using MSI/MSP to install. We have been doing some removing with the QuickPatch feature but understand that can do some special things. We'll see how it goes. ... View more

Thanks for the input. Just to kind of answer "is it a Product or System" question you possed... We distribute our CD to a larger field force, some under our control and some not. Our corporate network group is pushing us to distribute this update, because they do it to all the corporate environment. So it is a like your statement about is it a Product or System. To the control group it is like a System, to the non-controlled group it is a Product. ... View more

I have an Activex exe (out of process server). I tried to do what a previous post mentioned of adding a new component with the exe and extracting registry data for the component and then deleting the file (this is for the client install). But I had multiple issues with this for some reason. First it didn't seem to extract everything I needed, multiple keys where missing (not sure why). I tried multiple times and same result. I also had problems that when I would delete the exe from the component and build the registry data would disappear. I didn't have the "Extract registry data at build time" selected either. I had a suggestion from IS support to use RegSpyUI.exe in the [IS 2008]\Support directory. I extracted the data to a registry file and imported it, but it had a few paths to the file that needed to be changed. So changed those to be pointing to the TLB file instead of the exe. And had to add the association of the CLSID and the AppId and added RemoteServerName to the AppId. So what I have for the client... One component with the TLB file set to "Extract Com data at build" One component with the imported reg file from the Active exe with modifications (pointing to TBL file instead of EXE) and the addition of the RemoteServerName. There is no file in this component. The actuall exe will be installed in the server component. If someone has another way.... I would still like to hear. All my comparing and testing was against how the Microsoft Package and Deployment Wizard was doing it. ... View more

Anybody have some links to point me to??? Feel like I have searched the entire web and nothing. ... View more

Here seems to be my problem but not sure why. For each component (one exe and the dll), I have them installing to a directory defined in the MSI Directory table. It is called INSTANCE_PATH and set in a CA by the InstanceId. (I am using the Instance Transforms functionality). When I run the wizard, it shows the normal directories where files can possibly be installed like [AppDataFolder], [ProgramFilesFolder], [SystemFolder], and it shows my custom directory INSTANCE_PATH. So I pick INSTANCE_PATH and continue and it blows up. If I switch the components to INSTALLDIR, the run the wizard it works fine. I could switch back the directories after I build, but I don't want to have to do that for each build and have somebody remember to do that. Any ideas? ... View more

I created a new project and just added the exe and dll and ran the wizard and it worked no problem. I can try to remove stuff little by little from the current install to see what the problem is, but is there anything to try to make the narrowing a little easier? ... View more

It is just an in-house custom dll. ... View more