ExcelBanter

ExcelBanter (https://www.excelbanter.com/)
-   Excel Programming (https://www.excelbanter.com/excel-programming/)
-   -   Excel-called Dotnet DLL is using wrong Framework (https://www.excelbanter.com/excel-programming/401557-excel-called-dotnet-dll-using-wrong-framework.html)

Tim Zych

Excel-called Dotnet DLL is using wrong Framework
 
Does anyone know how to get Excel to use the proper Framework for a Dotnet
DLL that needs the 2.0 Framework, but that is installed on a machine with
1.1 and 2.0 Frameworks?

An Excel reference to a VS 2005 (2.0) Windows Application, with an output
type as a Class Library (with ComClass so that Excel can see it), doesn't
run properly because Excel is invoking the 1.1 Framework, which is
incompatible with the .net solution.

When the reference to the project is instantiated in Excel (Set o = New
Project.Class), there is an error "File or assembly name Project, or one of
its dependencies, was not found).

A workaround solution is to create a config file for Excel so that it is
forced to use the 2.0 framework, but the proper solve, I believe, is to get
Excel to invoke the proper framework the project needs, much like the config
file does, but dynamically.

Does anyone know how to fix this? I am using a Setup project to install.

Thx


--
Tim Zych
SF, CA



Tim Zych

Excel-called Dotnet DLL is using wrong Framework
 
Problem solved. By default Office 2003 uses the 1.1 Framework, unless the
OTKLOADR.DLL has been updated to the newer version. There is a hotfix
available and this is a known bug (thanks for MS support for their help).

http://support.microsoft.com/?id=907417

http://support.microsoft.com/?id=908002


--
Tim Zych
SF, CA


"Tim Zych" <tzych@NOSp@mE@RTHLINKDOTNET wrote in message
...
Does anyone know how to get Excel to use the proper Framework for a Dotnet
DLL that needs the 2.0 Framework, but that is installed on a machine with
1.1 and 2.0 Frameworks?

An Excel reference to a VS 2005 (2.0) Windows Application, with an output
type as a Class Library (with ComClass so that Excel can see it), doesn't
run properly because Excel is invoking the 1.1 Framework, which is
incompatible with the .net solution.

When the reference to the project is instantiated in Excel (Set o = New
Project.Class), there is an error "File or assembly name Project, or one
of its dependencies, was not found).

A workaround solution is to create a config file for Excel so that it is
forced to use the 2.0 framework, but the proper solve, I believe, is to
get Excel to invoke the proper framework the project needs, much like the
config file does, but dynamically.

Does anyone know how to fix this? I am using a Setup project to install.

Thx


--
Tim Zych
SF, CA





All times are GMT +1. The time now is 06:23 AM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com