Assemblies Not Registering Properly During Install

See platformsdk.msi.

--
Phil Wilson
The Definitive Guide to Windows Installer
http://www.apress.com/book/view/1590592972


<mawa316@rcn.com> wrote in message
news:8b98e348-8d99-4b74-b810-5758857d3690@u20g2000vbq.googlegroups.com...
> Hi there,
>
> This topic has been a thorn in my side since I've been working in
> Installation Development. We are currently using a Wise product,
> Installation Studio 7, to create our installations. We will be moving
> away from this to InstallShield 2010 in the very near future.
>
> Anyway, when a file is added to the Wise installation template, it is
> supposed to be scanned and its registry information added. When I
> look at the registry information for problematic post install files,
> the registration stuff appears to be there, but I don't believe it
> contains all the necessary information -- I guess that is pretty
> obvious since we have problems post-install.
>
> Custom Actions were added to register these files with RegAsm.exe (I
> know this is probably a no-no, but it was done in my several month
> absence due to layoff.), which worked for the most part, but you saw
> the ugly command windows flashing during execution. I have not yet
> tested this method on Windows 7 yet. I planned on creating a little
> WiseScript .exe to run RegAsm for each of the problem files. This way
> you could hide the command windows.
>
> However, this method is not working. I think it has something to do
> with the Security Structure of Win 7. I log in as administrator and
> run the install. The widget runs, but the files are still not
> registered. After closer examination, messages were displayed that
> there were inadequate permissions to touch the registry. I tried
> running the little install widget outside of the install to see these
> messages. If I manually run the .exe As Administrator, it works.
> This is failing during the install.
>
> The widget looks to HKCU for our installation location so the Custom
> Action that fires it is set to Deferred Execution - User Context. If
> I set it to System Context, it doesn't find the HKCU key value.
>
> I'm wondering how I can get around this.
>
> Here are some alternatives that I can see..
>
> -Use RegAsm /regfile and compare to what is in the install to see what
> is missing and add it directly to the Registry view of my template.
> -I guess I could try writing the key value to HKLM and change the
> Custom Action that fires the widget back to System Context.
>
> Like I said, I would like to have all the information scanned properly
> upon adding a file or compiling the installation, but that doesn't
> appear to be happening. Any workarounds such as that described above
> require uninstall Custom Actions to un-register, etc - additional
> overhead.
>
> Any help is GREATLY APPRECIATED!!!!!

Hi there,

This topic has been a thorn in my side since I've been working in
Installation Development. We are currently using a Wise product,
Installation Studio 7, to create our installations. We will be moving
away from this to InstallShield 2010 in the very near future.

Anyway, when a file is added to the Wise installation template, it is
supposed to be scanned and its registry information added. When I
look at the registry information for problematic post install files,
the registration stuff appears to be there, but I don't believe it
contains all the necessary information -- I guess that is pretty
obvious since we have problems post-install.

Custom Actions were added to register these files with RegAsm.exe (I
know this is probably a no-no, but it was done in my several month
absence due to layoff.), which worked for the most part, but you saw
the ugly command windows flashing during execution. I have not yet
tested this method on Windows 7 yet. I planned on creating a little
WiseScript .exe to run RegAsm for each of the problem files. This way
you could hide the command windows.

However, this method is not working. I think it has something to do
with the Security Structure of Win 7. I log in as administrator and
run the install. The widget runs, but the files are still not
registered. After closer examination, messages were displayed that
there were inadequate permissions to touch the registry. I tried
running the little install widget outside of the install to see these
messages. If I manually run the .exe As Administrator, it works.
This is failing during the install.

The widget looks to HKCU for our installation location so the Custom
Action that fires it is set to Deferred Execution - User Context. If
I set it to System Context, it doesn't find the HKCU key value.

I'm wondering how I can get around this.

Here are some alternatives that I can see..

-Use RegAsm /regfile and compare to what is in the install to see what
is missing and add it directly to the Registry view of my template.
-I guess I could try writing the key value to HKLM and change the
Custom Action that fires the widget back to System Context.

Like I said, I would like to have all the information scanned properly
upon adding a file or compiling the installation, but that doesn't
appear to be happening. Any workarounds such as that described above
require uninstall Custom Actions to un-register, etc - additional
overhead.

Any help is GREATLY APPRECIATED!!!!!