Hi,

1. We used SCSF june 2006 version and have built our own composite UI framework.

2. We have used GAT June 2006 version to create guidance packages for ourcomposite UI Framework built on top of SCSF.

3. We use GAX April 2007 version to distribute to the developers of UI that is required as a prerequisite to install our framework.

For your info: We have created a merge module for the Guidance Packageand have included it in a setup project which will install both our framework dll's and the Guidance Packages.

Allwas fine until we released version 1.1 of our Composite Framework. Version 1.1 and 1.0 of the Composite framework created by usmust be able toco-exist on the same machine. There is no problem with installing the two versions. But there is something done by the Guidance package that is corrupting the installation. The steps we took to fix this was to

1. Change the GUID present in the GuidanceAutomation.xml file for both versions.

Even this did not fix our problem. Now let me explain the problem.

1. Installed Version 1.0 of our framework and created a Solution using this 1.0 version. Lets call it V10App

2. Installed Version 1.1 of our frameowrk and creted a solution using this 1.1 version. Lets call it V11App

3. Now tried uninstalling V1.0 of the framework. The uninstallation does not happen fully and there are few registry entries of the guidance package still existing in the registry. But still the uninstallation does not give any error and finishes.

4. Now if we try installing v1.0 again, it says the application we are trying to install already exists.

4. Next, if you try uninstalling v1.1 it uninstalls successfully and cleanly.

5.Once v1.1 is uninstalled, what we need to do it install v1.0 again and then after that uninstall it. Now v1.0 will uninstall cleanly.

I know this has surely something to do with the Guidance packages. As mentioned above, I triedsetting different GUID for the two guidance packages. Even this did not help.

Are there any other steps that i need to take to solve this problem. Or is it we should be creating different guidance packages altogether using the GAT for every version of the Framewrok that we release?? Please advice

Thanks,

Ranjith

1. You just need to make sure you use unique values for the Caption, Guid and Name attributes of the <GuidancePackage> element in your guidance package manifest file.

2. Not sure what the question is about this.

HTH,
-Victor.

Hi,

To add on to the above query, i had some look into the registry entries and came out with the following findings.

1. Under the Registry HKLM->SOFTWARE->Microsoft->VisualStudio->8.0->NewProjectTemplates->TemplateDirs i found two registry entries with the GUIDs assigned for the GUidance package.

2. Under both the Keys named after their GUIDs the values of Package and Folder are the same. i.e they have the same GUID as their values.

Does this by any means cause the problem?

You mentioned you created your own MSM and MSI and then you said:

>>>Now if we try installing v1.0 again, it says the application we are trying to install already exists.

what does this message reads? is this a message from your custom installer?

Keep in mind that GAX packages doesn't support versioning, so if you have an 1.0 and a 1.1 guidance package you need to make sure you use different GUID and Names for them.

Are you using WiX to author your MSM and MSI? If so can you post the relevant fragments regarding GAX's custom actions?

Hi,

Let me make it very simple. Let's assume i created a guidance package using the GAT and i installed it in my box. Next lets assume i made some changes to the guidance packages and i want that to be released not as a replacement to the first one i created instead i want them both to co-exist.

1. In this case what all changes should i make to my guidacne package apart from chaning the GUID? Can you please list out all things that i need to change in the guidance package?

2. Now the other point isI will not be using the setup that is created by GAT. I will be creating a merge module for the Guidance package and the will include it in my own setup project which includes other dll's. THis will be finally rolled out to our customers.

-Ranjith

PS: Please consider points 1 & 2 as separate ones.

1. You just need to make sure you use unique values for the Caption, Guid and Name attributes of the <GuidancePackage> element in your guidance package manifest file.

2. Not sure what the question is about this.

HTH,
-Victor.

From a guidance package standpoint all you need to change is what I mentioned.

Now, from a VS Setup project standpoint you need to create either manually or by using GAT a new Setup project, you can't reuse the same VS Setup project to install more than one package. I believe this may be your case.

Can you post the error message you're getting? That should help the guessing game.

HTH,
-Victor.