B
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
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