H
hduyker
Hi,
I have the following problem:
I'm writing a small VB.NET SmartClient app for internal use, using VS 2005.
- Our users have Office 2003 on their machines.
- My development machine has both Office 2003 (Word, Excel) and Office 2007
(full) installed.
The GAC on my development machine contains:
- Microsoft.Office.Word.Interop 11.0.0.0
- Microsoft.Office.Word.Interop 12.0.0.0
- office 11.0.0.0
- office 12.0.0.0
- Microsoft.VBE.Interop 11.0.0.0
- Microsoft.VBE.Interop 12.0.0.0
For some reason (if I knew why, I would possibly have the solution...), my
compiled and deployed application says in it's .manifest:
<assemblyIdentity name="Microsoft.Office.Interop.Word"
version="12.0.0.0" publicKeyToken="71E9BCE111E9429C" language="neutral" />
<assemblyIdentity name="Microsoft.Vbe.Interop" version="12.0.0.0"
publicKeyToken="71E9BCE111E9429C" language="neutral" />
<assemblyIdentity name="office" version="12.0.0.0"
publicKeyToken="71E9BCE111E9429C" language="neutral" />
So, when I try running it on a client PC with only Office 2003 installed, it
complains about not having those three assemblies present. And changing the
manifest is not really an option (as it breaks the signature).
i could use some pointers on where to look / what to change (without
deinstalling Office 2007, preferably).
I have the following problem:
I'm writing a small VB.NET SmartClient app for internal use, using VS 2005.
- Our users have Office 2003 on their machines.
- My development machine has both Office 2003 (Word, Excel) and Office 2007
(full) installed.
The GAC on my development machine contains:
- Microsoft.Office.Word.Interop 11.0.0.0
- Microsoft.Office.Word.Interop 12.0.0.0
- office 11.0.0.0
- office 12.0.0.0
- Microsoft.VBE.Interop 11.0.0.0
- Microsoft.VBE.Interop 12.0.0.0
For some reason (if I knew why, I would possibly have the solution...), my
compiled and deployed application says in it's .manifest:
<assemblyIdentity name="Microsoft.Office.Interop.Word"
version="12.0.0.0" publicKeyToken="71E9BCE111E9429C" language="neutral" />
<assemblyIdentity name="Microsoft.Vbe.Interop" version="12.0.0.0"
publicKeyToken="71E9BCE111E9429C" language="neutral" />
<assemblyIdentity name="office" version="12.0.0.0"
publicKeyToken="71E9BCE111E9429C" language="neutral" />
So, when I try running it on a client PC with only Office 2003 installed, it
complains about not having those three assemblies present. And changing the
manifest is not really an option (as it breaks the signature).
i could use some pointers on where to look / what to change (without
deinstalling Office 2007, preferably).