Customization not loading

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jeppe Jespersen - 21 Feb 2006 08:48 GMT

I have created a very simple customization on a Word Template. Having built
it, I shut down Visual Studio, browse to the folder where the .dot (and
.dll) is located, and double click the .dot.
A new document fires up and the customization is activated. No problem.

Now....

I move the .dot and the .dll to a different folder. Now the customization
doesn't load, it seems. The document starts up, no exceptions are thrown, no
"customization could not be loaded" errors or anything. Just nothing.

Any ideas, anyone? I have extracted what I believe to be the application
manifest from the .dot (using a serverdocument). Seems to me that copying
both files to a new location should _not_ be a problem. But it is. :-( Am I
completely missing something. I am just completely out of ideas.

Please help. Desperation on horizon. Getting bigger. AAArrrhghgg!

Thanks
J. Jespersen

<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" manifestVersion="1.0">
<assemblyIdentity name="myTemplate.dll" version="1.0.0.0" />
<asmv2:entryPoint name="Startup" dependencyName="dependency0">
<asmv2:clrClassInvocation class="myTemplate.ThisDocument" />
</asmv2:entryPoint>
<asmv2:dependency asmv2:name="dependency0">
<asmv2:dependentAssembly>
<assemblyIdentity name="myTemplate" version="1.0.0.0" />
</asmv2:dependentAssembly>
<asmv2:installFrom codebase="myTemplate.dll" />
</asmv2:dependency>
</assembly>

Reply to this Message

Ron - 21 Feb 2006 15:30 GMT

I believe you have to update the AssemblyPath property in the document's
embedded manifest so that it points to the new location. Also, you may have
to set the .NET security policy accordingly.

Ron

> I have created a very simple customization on a Word Template. Having built
> it, I shut down Visual Studio, browse to the folder where the .dot (and
[quoted text clipped - 30 lines]
> </asmv2:dependency>
> </assembly>

Reply to this Message

dlc - 22 Feb 2006 14:44 GMT

Jeppe,

I have had the exact same issue for quite some time. Deploy the
solution to one PC; it functions. Deploy to another PC; it doesn't.

In my case, I recently learned (within the last few days) that the
problem lies with the version of Office Excel the user has on their PC.
Although all of the machines had what looked like Office Excel 2003,
some were a part of Office Professional, some were a part of Small
Business Edition. The one's with SBE did not work. No message, no
nothing.

My solution came as a result of the information contained in the recent
articles at the following links:

http://msdn.microsoft.com/office/default.aspx?pull=/library/en-us/odc_vsto2005_t
a/html/OfficeVSTOWindowsInstallerOverview.asp

http://msdn.microsoft.com/office/default.aspx?pull=/library/en-us/odc_vsto2005_t
a/html/OfficeVSTOWindowsInstallerWalkthrough.asp

If you build the deployment as the articles suggest, you may get a
message stating that "Microsoft Office Excel is not installed on this
computer" (or in your case Word). That's a big clue.

To have to build this deployment package is a huge pain in the ... It
shouldn't be this difficult.

Hope this helps,

David

Reply to this Message

Customization not loading

Free Magazines