File Registration on VISTA Question ????

We have an install that places some .net .dll's and places some
'stuff' in the registry, etc. The registration 'stuff' is written to
HKEY_CLASSES_ROOT, which I now know is a merge of HKCU/Software/
Classes and HKLM/Software/Classes.

On XP all seems OK as the registry information appears under HKCR and
HKEY_CURRENT_USER/Software/Classes (it is only set up under HKCR in
the .wsi (Wise installation template file)).

Now on VISTA, all looks the same after the install, but our installed
PlugIn is seen as not registered by our application. The way I trudged
around this was to export the information from HKCU/Software/Classes
and import under HKLM.

Would anyone know why this might be?

"Superfreak3" <> wrote ...
> We have an install that places some .net .dll's and places some
> 'stuff' in the registry, etc. The registration 'stuff' is written to
> HKEY_CLASSES_ROOT, which I now know is a merge of HKCU/Software/
> Classes and HKLM/Software/Classes.
> < ... snip ... >

Do you mean, this is your application, which you developed and are
distributing? Or do you mean it's a 3rd party app which you have obtained
and you are trying to install?

Basically, the developer of the app needs to update their installer to match
Vista guidelines. If you're the developer, take a look at Microsoft's
document "ISV Windows Vista Compatibility Cookbook":
http://sharepoint.microsoft.com/inno...20Cookbook.doc
Pages 34-37 talk about your situation. There's a wealth of practical advice
in there for any application developer working with Vista. There's also a
tonne of additional information at the Vista Application Compatibility
website:
http://msdn2.microsoft.com/en-us/win.../aa904987.aspx
There are some useful tools to download, esp the App Compat Toolkit.

Note that Microsoft didn't make these changes capriciously, just to dick
around ISVs; everyone wanted Windows to be more secure so this is the
result.

Hope it helps, good luck with the project!
--
Andrew McLaren
amclar (at) optusnet dot com dot au

On Jul 7, 1:11 am, "Andrew McLaren" <and...@fakeaddress.com> wrote:
> "Superfreak3" <Matt.Wal...@synergis.com> wrote ...
>
> > We have an install that places some .net .dll's and places some
> > 'stuff' in the registry, etc. The registration 'stuff' is written to
> > HKEY_CLASSES_ROOT, which I now know is a merge of HKCU/Software/
> > Classes and HKLM/Software/Classes.
> > < ... snip ... >
>
> Do you mean, this is your application, which you developed and are
> distributing? Or do you mean it's a 3rd party app which you have obtained
> and you are trying to install?
>
> Basically, the developer of the app needs to update their installer to match
> Vista guidelines. If you're the developer, take a look at Microsoft's
> document "ISV Windows Vista Compatibility Cookbook":
> http://sharepoint.microsoft.com/inno...er/Developer%2...
> Pages 34-37 talk about your situation. There's a wealth of practical advice
> in there for any application developer working with Vista. There's also a
> tonne of additional information at the Vista Application Compatibility
> website:
> http://msdn2.microsoft.com/en-us/win.../aa904987.aspx
> There are some useful tools to download, esp the App Compat Toolkit.
>
> Note that Microsoft didn't make these changes capriciously, just to dick
> around ISVs; everyone wanted Windows to be more secure so this is the
> result.
>
> Hope it helps, good luck with the project!
> --
> Andrew McLaren
> amclar (at) optusnet dot com dot au

Yes, it is our application that we are deploying and NOT a third part
app. installation attempt.

I'll check out the links.

Thanks for the information!

On Jul 8, 7:27 pm, Superfreak3 <Matt.Wal...@synergis.com> wrote:
> On Jul 7, 1:11 am, "Andrew McLaren" <and...@fakeaddress.com> wrote:
>
>
>
>
>
> > "Superfreak3" <Matt.Wal...@synergis.com> wrote ...
>
> > > We have an install that places some .net .dll's and places some
> > > 'stuff' in the registry, etc. The registration 'stuff' is written to
> > > HKEY_CLASSES_ROOT, which I now know is a merge of HKCU/Software/
> > > Classes and HKLM/Software/Classes.
> > > < ... snip ... >
>
> > Do you mean, this is your application, which you developed and are
> > distributing? Or do you mean it's a 3rd party app which you have obtained
> > and you are trying to install?
>
> > Basically, the developer of the app needs to update their installer to match
> > Vista guidelines. If you're the developer, take a look at Microsoft's
> > document "ISV Windows Vista Compatibility Cookbook":
> > http://sharepoint.microsoft.com/inno...er/Developer%2...
> > Pages 34-37 talk about your situation. There's a wealth of practical advice
> > in there for any application developer working with Vista. There's also a
> > tonne of additional information at the Vista Application Compatibility
> > website:
> > http://msdn2.microsoft.com/en-us/win.../aa904987.aspx
> > There are some useful tools to download, esp the App Compat Toolkit.
>
> > Note that Microsoft didn't make these changes capriciously, just to dick
> > around ISVs; everyone wanted Windows to be more secure so this is the
> > result.
>
> > Hope it helps, good luck with the project!
> > --
> > Andrew McLaren
> > amclar (at) optusnet dot com dot au
>
> Yes, it is our application that we are deploying and NOT a third part
> app. installation attempt.
>
> I'll check out the links.
>
> Thanks for the information!- Hide quoted text -
>
> - Show quoted text -

" http://sharepoint.microsoft.com/inno...er/Developer%2...
Pages 34-37 talk about your situation."

Are you referring to the Default Programs Guidelines and Best
Practices section? I just want to be sure I'm in the right place.

THANKS AGAIN FOR THE INFORMATION & HELP!!!

On Jul 9, 10:12?am, Superfreak3 <Matt.Wal...@synergis.com> wrote:
> On Jul 8, 7:27 pm,Superfreak3<Matt.Wal...@synergis.com> wrote:
>
>
>
>
>
> > On Jul 7, 1:11 am, "Andrew McLaren" <and...@fakeaddress.com> wrote:
>
> > > "Superfreak3" <Matt.Wal...@synergis.com> wrote ...
>
> > > > We have an install that places some .net .dll's and places some
> > > > 'stuff' in the registry, etc. The registration 'stuff' is written to
> > > > HKEY_CLASSES_ROOT, which I now know is a merge of HKCU/Software/
> > > > Classes and HKLM/Software/Classes.
> > > > < ... snip ... >
>
> > > Do you mean, this is your application, which you developed and are
> > > distributing? Or do you mean it's a 3rd party app which you have obtained
> > > and you are trying to install?
>
> > > Basically, the developer of the app needs to update their installer to match
> > > Vista guidelines. If you're the developer, take a look at Microsoft's
> > > document "ISV Windows Vista Compatibility Cookbook":
> > > http://sharepoint.microsoft.com/inno...er/Developer%2...
> > > Pages 34-37 talk about your situation. There's a wealth of practical advice
> > > in there for any application developer working with Vista. There's also a
> > > tonne of additional information at the Vista Application Compatibility
> > > website:
> > > http://msdn2.microsoft.com/en-us/win.../aa904987.aspx
> > > There are some useful tools to download, esp the App Compat Toolkit.
>
> > > Note that Microsoft didn't make these changes capriciously, just to dick
> > > around ISVs; everyone wanted Windows to be more secure so this is the
> > > result.
>
> > > Hope it helps, good luck with the project!
> > > --
> > > Andrew McLaren
> > > amclar (at) optusnet dot com dot au
>
> > Yes, it is our application that we are deploying and NOT a third part
> > app. installation attempt.
>
> > I'll check out the links.
>
> > Thanks for the information!- Hide quoted text -
>
> > - Show quoted text -
>
> " http://sharepoint.microsoft.com/inno...er/Developer%2...
> Pages 34-37 talk about your situation."
>
> Are you referring to the Default Programs Guidelines and Best
> Practices section? I just want to be sure I'm in the right place.
>
> THANKS AGAIN FOR THE INFORMATION & HELP!!!- Hide quoted text -
>
> - Show quoted text -

Is this the answer?

https://blogs.msdn.com/cjacks/archiv...ows-vista.aspx