using Microsoft.Office.Interop.Word not working!

[Guest]

ISSUE (reposted)
===========================
Can someone please explain to me why I can't get the MS Word Interop assembly
to work in my VS2005 project? For many people, they say they add the
reference and it works, however when I add the reference the application
can't find it. Not sure why it says the system cannot find the file when it
exists in that location? Please help, thanks in advance...

GOAL
===========================
Basically I am making an intranet application for my company and this
feature will only be used inside our network to create/open word documents
that can be modified programatically.

ERROR MESSAGE
===========================
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly
'Microsoft.Office.Interop.Word, Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system
cannot find the file specified.

Source Error:
Line 20: during development.
Line 21: -->
Line 22: <compilation debug="true">
Line 23: <assemblies>
Line 24: <add assembly="Microsoft.Office.Interop.Word, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c"/>

Source File: C:\Inetpub\wwwroot\MyApp\web.config Line: 22

Assembly Load Trace: The following information can be helpful to determine
why the assembly 'Microsoft.Office.Interop.Word, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].

 

[Ken Wilson]

ISSUE (reposted)
===========================
Can someone please explain to me why I can't get the MS Word Interop assembly
to work in my VS2005 project? For many people, they say they add the
reference and it works, however when I add the reference the application
can't find it. Not sure why it says the system cannot find the file when it
exists in that location? Please help, thanks in advance...

GOAL
===========================
Basically I am making an intranet application for my company and this
feature will only be used inside our network to create/open word documents
that can be modified programatically.

ERROR MESSAGE
===========================
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly
'Microsoft.Office.Interop.Word, Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system
cannot find the file specified.

Source Error:
Line 20: during development.
Line 21: -->
Line 22: <compilation debug="true">
Line 23: <assemblies>
Line 24: <add assembly="Microsoft.Office.Interop.Word, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c"/>

Source File: C:\Inetpub\wwwroot\MyApp\web.config Line: 22

Assembly Load Trace: The following information can be helpful to determine
why the assembly 'Microsoft.Office.Interop.Word, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].

My initial guess would be that the PIA for Word and also the other
office PIAs may not have been installed properly. I would first
re-install Office doing a 'Complete' installation and go from there.

http://msdn2.microsoft.com/en-us/library/15s06t57.aspx

Ken Wilson
Seeking viable IT employment in Victoria, BC