We have successfully deployed a word template. Now we've made some changes, and after installation of the new version of the template, the template is not loaded. On my development machine, i do not get any error at all. On other users (none-dev machines) the following error is shown:

System.IO.FileLoadException: Could not load file or assembly 'xxxxxxx, Version=, Culture=neutral, PublicKeyToken=6f98f00a36220540' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040).

I have changed the version of the assembly in order to keep track of versions. When i set the version back to then the assembly is loaded correctly.

What strategy should be used when upgrading document level customisations. Should you create a converter app which reattaches the customisation to the documents or should you just never change the

AssemblyVersion and AssemblyFileVersion attributes



Re: Visual Studio Tools for Office Document-level customisation upgrade strategy

Ji Zhou ¨C MSFT

Hi Eduard,

I remember someone has encountered such a question before and resolved by deleting a bunch of files and rebuilding.

Refer this link to see if it helps please:

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=2044338&SiteID=1