More than one CLR per process / addin isolation

Hi,

Is there a way to load different versions of CLR into one process? We need
this in order to be able to use .Net 2 add-ins and .Net 1 add-ins in Excel at
the same time.

--
Best regards,
Ruslan Popov

Hi Ruslan,

Thanks for your post!

Yes, this is a frequently asked question. Currently, .Net does not support
loading 2 different versions of CLR in the same process, our Fusion
developer Junfeng Zhang has answered this question in his blog:
"CLR Side by Side and Compatibility"
http://blogs.msdn.com/junfeng/archiv...26/422014.aspx

I am not an Office Addin expert, however, based on my experience, Office
process will always load the highest version of CLR on the machine although
your Addin may target for lower version of .Net.
However, normally this will not be a problem. .Net2.0 has considered
.Net1.1 backward compatibility in design, so .Net1.1 code should work well
in .Net2,.0 runtime without break-change. So your 2 addins should run on
.Net2.0 without any problem.

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jeffrey,

Thanks. Unfortunatelly, some .Net 1.1 add-ins do not work correctly under
..Net 2.0.

--
Best regards,
Ruslan Popov


""Jeffrey Tan[MSFT]"" wrote:

Hi Ruslan,

Thanks for your post!

Yes, this is a frequently asked question. Currently, .Net does not support
loading 2 different versions of CLR in the same process, our Fusion
developer Junfeng Zhang has answered this question in his blog:
"CLR Side by Side and Compatibility"
http://blogs.msdn.com/junfeng/archiv...26/422014.aspx

I am not an Office Addin expert, however, based on my experience, Office
process will always load the highest version of CLR on the machine although
your Addin may target for lower version of .Net.
However, normally this will not be a problem. .Net2.0 has considered
.Net1.1 backward compatibility in design, so .Net1.1 code should work well
in .Net2,.0 runtime without break-change. So your 2 addins should run on
.Net2.0 without any problem.

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jeffrey,

However, normally this will not be a problem. .Net2.0 has considered
..Net1.1 backward compatibility in design

Would it be a normal case I would not post a question her

--
Best regards,
Ruslan Popov


""Jeffrey Tan[MSFT]"" wrote:

Hi Ruslan,

Thanks for your post!

Yes, this is a frequently asked question. Currently, .Net does not support
loading 2 different versions of CLR in the same process, our Fusion
developer Junfeng Zhang has answered this question in his blog:
"CLR Side by Side and Compatibility"
http://blogs.msdn.com/junfeng/archiv...26/422014.aspx

I am not an Office Addin expert, however, based on my experience, Office
process will always load the highest version of CLR on the machine although
your Addin may target for lower version of .Net.
However, normally this will not be a problem. .Net2.0 has considered
.Net1.1 backward compatibility in design, so .Net1.1 code should work well
in .Net2,.0 runtime without break-change. So your 2 addins should run on
.Net2.0 without any problem.

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ruslan ,

Oh, it seems that your 1.1 Addin uses some break change classes which do
not work in .Net2.0. Can you provide some more detailed information
regarding which code does not work in .Net2.0? I may help you to workaround
these code snippets.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Don't know, Jeffrey, as it's in a third-party component. We didn't get into
details of what is not working, just the fact that something might break if
we switch to 2.0 prevents us from doing so, unless we find a way to load all
add-ins in their "native" version of CLR.

--
Best regards,
Ruslan Popov


""Jeffrey Tan[MSFT]"" wrote:

Hi Ruslan ,

Oh, it seems that your 1.1 Addin uses some break change classes which do
not work in .Net2.0. Can you provide some more detailed information
regarding which code does not work in .Net2.0? I may help you to workaround
these code snippets.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ruslan,

Oh, in this scenario, we are out of luck. You have to contact the 3rd party
addin vendor for this break change issue. I assume the vendor company may
cowork with Microsoft to find out the break change root cause.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

This is not a solution. The point is that if one add-in breaks we can't
guarantee stable work if we switch to 2.0. We don't know what add-ins our
users theoretically might use.

--
Best regards,
Ruslan Popov


""Jeffrey Tan[MSFT]"" wrote:

Hi Ruslan,

Oh, in this scenario, we are out of luck. You have to contact the 3rd party
addin vendor for this break change issue. I assume the vendor company may
cowork with Microsoft to find out the break change root cause.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ruslan,

Unfortunately, since the addins are developed by 3rd party, I do not think
there is a good workaround for it. The 3rd party vendor is the only source
that can fix it. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Can we get comments of the CLR team on how difficult it is to make it
possible to host more than one CLR in one process?

--
Best regards,
Ruslan Popov


""Jeffrey Tan[MSFT]"" wrote:

Hi Ruslan,

Unfortunately, since the addins are developed by 3rd party, I do not think
there is a good workaround for it. The 3rd party vendor is the only source
that can fix it. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.