C
craig
Environment: MDE 2002 V7.0.9466; Visual Studio.NET; Framework 1.0.3705
I have a fairly complex application which has been running properly at field
test sites for over a year. Recently, after being rebuilt, the application
started failing in my test environment with a runtime filenotfound error. I
traced it to the instruction which creates the Outlook Application, e.g.,
ol = New Outlook.Application() where ol is dimensioned as Outlook.Application
Further research revielded that the Object Library reference for Outlook has
substantially changed between version 9.0 and 9.2 so that the object gets
referenced ?incorrectly? within my VB application. The differences that I
can see in the library properties section of Visual Studio are as follows:
Property V9.0 (still works) V9.2(fails)
---------- -------------------- ------------
Name Interop.Outlook Microsoft.Office.Interop.Outlook
Copy Local True False
Identity ...\9.0\tlbimp ...\9.2\0\primary
Path program output \windows\assembly\GAC...
Strong Name False True
Type ActiveX ActiveX
Version 9.0 9.2
I've tried changing my program references from Outlook.Application to
Microsoft.Office.Interop.Outlook. This solves build assembly errors, but the
runtime still fails at the application creation statement with filenotfound.
When I look at the Assembly Binding Log, the search path appears to be back
to my program output location (as I believe it should be for an ActiveX
component).
Why is my development environment creating this new (v9.2) object library as
a GAC reference instead of Copy Local True. [BTW, I've tried forcing the
Copy Local flag to True - the problem remains the same.
Thanks in advance for your time.
-
craig
Mergellina Designs Inc
I have a fairly complex application which has been running properly at field
test sites for over a year. Recently, after being rebuilt, the application
started failing in my test environment with a runtime filenotfound error. I
traced it to the instruction which creates the Outlook Application, e.g.,
ol = New Outlook.Application() where ol is dimensioned as Outlook.Application
Further research revielded that the Object Library reference for Outlook has
substantially changed between version 9.0 and 9.2 so that the object gets
referenced ?incorrectly? within my VB application. The differences that I
can see in the library properties section of Visual Studio are as follows:
Property V9.0 (still works) V9.2(fails)
---------- -------------------- ------------
Name Interop.Outlook Microsoft.Office.Interop.Outlook
Copy Local True False
Identity ...\9.0\tlbimp ...\9.2\0\primary
Path program output \windows\assembly\GAC...
Strong Name False True
Type ActiveX ActiveX
Version 9.0 9.2
I've tried changing my program references from Outlook.Application to
Microsoft.Office.Interop.Outlook. This solves build assembly errors, but the
runtime still fails at the application creation statement with filenotfound.
When I look at the Assembly Binding Log, the search path appears to be back
to my program output location (as I believe it should be for an ActiveX
component).
Why is my development environment creating this new (v9.2) object library as
a GAC reference instead of Copy Local True. [BTW, I've tried forcing the
Copy Local flag to True - the problem remains the same.
Thanks in advance for your time.
-
craig
Mergellina Designs Inc