N
Nicu
Hello!
(Office Word 2003, Visual Studio 2005, VSTO 2005 SE)
I have a problem with a vsto word add-in. Until last week, everything worked
fine, the setup was installing everything ok. Now I modified the name of one
of my dlls, updated custom actions on setup properties. Registry keys are ok.
Symptoms:
I run setup on client machine, everything seems to install correct. But I
don't see any add-in on COM Add-Ins, or under Disabled Items on Help. In
registry everything it's ok, I can tell you that this is not the first time
when I make a setup, so in the past worked fine. All the files are installed
in the TARGET directory, I put the Register property of the Primary Output
from my project to "vsdrpCOM", I tried also with "vsdrpCOMRelativePath" si
"vsdrpCOMSelfReg". In registry, load behavior is set to 3, the CLSID is ok,
Full Trust is set due to SetSecurity and checked also with .NET Framework
Console.
Everything it's ok, no error. I set up also VSTOSUPRESS... to 0. Nothing. A
few hours ago, I found a solution to check the misterious behaviour by using
FUSLOGVW.exe. Run it, and it seems I get on one of the entries:
*** Assembly Binder Log Entry (10/3/2008 @ 6:07:28 PM) ***
The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.
Assembly manager loaded from:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\WINDOWS\system32\MsiExec.exe
--- A detailed error log follows.
LOG: IJW explicit bind. File path:C:\Program Files\TRP\Magnon Word
Add-In\MagnonWord2003.dll.
LOG: IJW assembly bind returned file not found.
The dll is there, is strong named. I used on my development machine to set
strong name, the sn.exe -k path\nameofdllhere.dll so I wrote the pair to it.
What can I do else? I need help please cause I can't figure out what is
happening. Very very strange.
Thanks in advance.
Regards,
Nicu
(Office Word 2003, Visual Studio 2005, VSTO 2005 SE)
I have a problem with a vsto word add-in. Until last week, everything worked
fine, the setup was installing everything ok. Now I modified the name of one
of my dlls, updated custom actions on setup properties. Registry keys are ok.
Symptoms:
I run setup on client machine, everything seems to install correct. But I
don't see any add-in on COM Add-Ins, or under Disabled Items on Help. In
registry everything it's ok, I can tell you that this is not the first time
when I make a setup, so in the past worked fine. All the files are installed
in the TARGET directory, I put the Register property of the Primary Output
from my project to "vsdrpCOM", I tried also with "vsdrpCOMRelativePath" si
"vsdrpCOMSelfReg". In registry, load behavior is set to 3, the CLSID is ok,
Full Trust is set due to SetSecurity and checked also with .NET Framework
Console.
Everything it's ok, no error. I set up also VSTOSUPRESS... to 0. Nothing. A
few hours ago, I found a solution to check the misterious behaviour by using
FUSLOGVW.exe. Run it, and it seems I get on one of the entries:
*** Assembly Binder Log Entry (10/3/2008 @ 6:07:28 PM) ***
The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.
Assembly manager loaded from:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\WINDOWS\system32\MsiExec.exe
--- A detailed error log follows.
LOG: IJW explicit bind. File path:C:\Program Files\TRP\Magnon Word
Add-In\MagnonWord2003.dll.
LOG: IJW assembly bind returned file not found.
The dll is there, is strong named. I used on my development machine to set
strong name, the sn.exe -k path\nameofdllhere.dll so I wrote the pair to it.
What can I do else? I need help please cause I can't figure out what is
happening. Very very strange.
Thanks in advance.
Regards,
Nicu
) it was something about CLSID on HKLM. I