Impact of InprocServer32\RuntimeVersion ?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mark - 21 Dec 2007 15:23 GMT

Hi...

Just out of curiousity, I was wondering if the InprocServer32\RuntimeVersion
registry setting of a .Net COM interop object had any effect?

I happened to notice the other day that our Wix msi projects errorneous
install all our .Net COM interop with this set to v1.1.4322 even though all
the assemblies are built v2.0.50727.

Having this registry key set wrong doesn't appear to have any ill effect, so
I was wondering if it had any effect at all?

Thanks
Mark

Reply to this Message

Phil Wilson - 21 Dec 2007 22:02 GMT

I've not seen it have any effect at all. I think it's just info. I think WiX
used a 1.1 regasm equivalent to create the registry entries because WiX has
been a 1.1 framework app until literally this week.

Signature

Phil Wilson
[MVP Windows Installer]

> Hi...
>
[quoted text clipped - 13 lines]
> Thanks
> Mark

Reply to this Message

Walter Wang [MSFT] - 24 Dec 2007 05:18 GMT

The "RuntimeVersion" key is there to enforce that the component can only be
run on a CLR version equal to or higher than the version specified in this
key. This key may get ignored in versions of the CLR < 2.0. I haven't
found any further information about this key and it seems undocumented and
unsupported.

Regards,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Impact of InprocServer32\RuntimeVersion ?

Free Magazines