.Net 2.0 and Office

[Beppe]

We have an addon for Excel compiled with .NET 1.1.
When .NET 2.0 is also installed on computers it doesn't work anymore.

We have followed the paragraph "Configuring Unmanaged Applications" at
http://msdn.microsoft.com/netframew.../library/en-us/dnnetdep/html/sidexsidenet.asp

and we (and our customers as well) wonder that we must put an
EXCEL.exe.config in the Office folder forcing the use of 1.1 by:

<configuration>
<startup>
<supportedRuntime version="v1.1.4322" />
</startup>
</configuration>

My Addon works, but the customers' addons .Net 2.0 will not work. Compiling
it with Visual Studio 2005 a lot of "obsolete functions" error arises.
Are we forced to move to 2.0 and spend effort and revise our internal
workplan? Any news about a patch for Office or .Net 2.0 for solving this
problem? Is there another way without moving to .Net 2.0?
Thanks in advance

Giuseppe

 

[Peter Huang [MSFT]]

Dear Customer,

From you description, I understand that you have both .NET 1.1 and 2.0
installed on your machine. You have an Excel Addin which is compiled with
..NET 1.1. You know how to use an "Excel.exe.config" file to set your Excel
process to host .NET 1.1 for your Addins. But this will prevent the Addins
built with .NET 2.0 from working.

You would like to know if we can host both .NET 1.1 and 2.0 in the Excel
process simultaneously.

If I misunderstood, please feel free to let me know.

Based on my research, so far a single process can not host both .NET 1.1
and 2.0 simultaneously. That is to say we have to run the Addins built with
..NET 1.1 or 2.0, but not both.

I think we may try to recompile the Addins which are originally built with
..NET 1.1 in .NET 2.0. That way we only need to host the .NET 2.0 in Excel
process.

Please try this and let me know the result.

If you still have any concern, please feel free to let me know.
I look forward to hearing from you.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Beppe]

Hi Peter,

thanks a lot for your kind answer.
Yes you have perfectly understood the problem.
So your answer is: all world-wide existing Office addins built with .NET 1.0
and 1.1 are forced to move to the .NET 2.0 because Office tools can host
only one CRL at time ... with extra cost of development and testing.

We have already tried to compile in .Net 2.0 with a lot of compiling
errors.

Thanks, Beppe

 

[Peter Huang [MSFT]]

Hi Beppe,

Thanks for your quickly reply!
Commonly the .NET 2.0 will be back compatible with .NET 1.1 built code.
That is to say, the .NET 1.1 built addin will run on the .NET 2.0 runtime.
But so far we have problem to run the .NET 1.1 built addin on .NET 2.0. So
I think some of the code is not complete compatible.
So I suggest we try recompile it under .NET 2.0 to adjust the code.



Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.