Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
See more: Windows Server
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 2-Nov-11 5:13am
Edited 2-Nov-11 5:16am
(no name)32.9K
v2

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

  Print Answers RSS
0 Sergey Alexandrovich Kryukov 620
1 CPallini 140
2 CHill60 130
3 ashok rathod 119
4 BillWoodruff 115
0 Sergey Alexandrovich Kryukov 9,543
1 OriginalGriff 6,984
2 CPallini 5,820
3 George Jonsson 4,017
4 Gihan Liyanage 3,266


Advertise | Privacy | Mobile
Web04 | 2.8.140926.1 | Last Updated 2 Nov 2011
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100