all groups > dotnet interop > december 2007 >
You're in the

dotnet interop

group:

Impact of InprocServer32\RuntimeVersion ?


Impact of InprocServer32\RuntimeVersion ? Mark
12/21/2007 7:23:01 AM
dotnet interop:
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
Re: Impact of InprocServer32\RuntimeVersion ? Phil Wilson
12/21/2007 2:02:04 PM
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.
--
Phil Wilson
[MVP Windows Installer]

[quoted text, click to view]

Re: Impact of InprocServer32\RuntimeVersion ? wawang@online.microsoft.com (
12/24/2007 5:18:20 AM
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.
AddThis Social Bookmark Button