Click here to Skip to main content
15,916,951 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I did a server install of our application on Windows 2008 R2 and ran the application, but it could not instantiate the local assemblies.

Note that the application uses side by side and are installed to "C:\Test" by default.

I copied the auto-print sub folder from "C:\Test" to "C:\TEST_TeMp" and ran the app and it ran.

It seems like Windows 2008 is caching information about the executable, its full-path and manifest.

If the executable ran without a manifest, windows 2008 caches that an external manifest is not needed. It only resets itself to look at external manifest when you set this in the registry key.

Afterward it does not care whether the registry key exists it still uses the external manifest.

However, once you reboot it does not look at the external manifest any longer.

http://blogs.msdn.com/b/vistacompatteam/archive/2006/11/13/manifest-and-the-fusion-cache.aspx

http://blogs.msdn.com/b/chrisforster/archive/2007/12/11/changetomanifest.aspx

How can this be fixed changing manifest modified date and exe file modified date does not work for me?
Posted
Updated 2-Nov-11 5:16am
v2

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900