Je cherche des infos sur les fichiers d'extension .exe.local qui serviraient
à forcer l'exe à utiliser les DLL de son répertoire plutôt que les DLLs COM
du système. Aucune info sur le Web et pourtant quand on renomme un fichier en
.local, l'icône obtenue est celle des DLLs
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
Jean-Claude BELLAMY
Dans le message news: , OfaMCT s'est ainsi exprimé:
Je cherche des infos sur les fichiers d'extension .exe.local qui serviraient à forcer l'exe à utiliser les DLL de son répertoire plutôt que les DLLs COM du système. Aucune info sur le Web et pourtant quand on renomme un fichier en .local, l'icône obtenue est celle des DLLs
Il ne s'agit pas de renommer un fichier .exe, mais de créer dans le même dossier un AUTRE fichier, vide, qui aura le nom du fichier .exe concerné et l'extension ".exe.local"
C'est expliqué dans un article du MSDN (DVD) ms-help://MS.MSDNQTR.2004OCT.1033/sbscs/setup/dll_com_redirection_on_windows.htm
Extrait :
DLL/COM redirection is activated by installing a special file along with a copy of the local component file into the same directory as the application's executable file. The special file is an empty file named after the application executable's file name and appended with .local. For example, to activate DLL/COM redirection for an application named Myapp, the local version of the component and an empty file named Myapp.exe.local must be copied into the folder containing Myapp.exe. This binds the application to the local version of the component rather than the globally shared version of the component.
When an application loads a component file, such as a DLL or .ocx file, Windows first searches for it in the folder where the application's .local and executable file is installed. If found, the application uses that component file regardless of any directory search path defined in the application or the registry. If not found, the component file in the defined search path is used.
The installation utility must do the following to install the application with DLL/COM redirection: - An empty .local file must be copied into the same folder as the application's executable file. - All of the components, DLL, and .ocx files used by the application must be copied into the same folder as the application's executable file. - Isolated COM components must be registered with Windows so that different versions of the assembly will not conflict with each other when loaded into memory at the same time. The registration process requires that, while the implementation of the component can change between versions, certain COM metadata such as CLSID, ProgID, Type Library, and Threading Model cannot. - If the application is installed using the Windows Installer, then the application directory can be secured by using the LockPermissions table. Typically, the system is given read, write, and execute access; all other processes are given only execute and read access.
For additional discussion about DLL/COM redirection, see the following white paper "Implementing Side-by-side Component Sharing". http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsetup/html/sidebyside.asp
-- May the Force be with You! La Connaissance s'accroît quand on la partage ---------------------------------------------------------- Jean-Claude BELLAMY [MVP] - http://www.bellamyjc.org http://www.bellamyjc.org *
Dans le message news:3A84EF84-18D9-4BBF-83B1-855320B6CDC0@microsoft.com ,
OfaMCT <OfaMCT@discussions.microsoft.com> s'est ainsi exprimé:
Je cherche des infos sur les fichiers d'extension .exe.local qui
serviraient à forcer l'exe à utiliser les DLL de son répertoire
plutôt que les DLLs COM du système. Aucune info sur le Web et
pourtant quand on renomme un fichier en .local, l'icône obtenue est
celle des DLLs
Il ne s'agit pas de renommer un fichier .exe, mais de créer dans le même
dossier un AUTRE fichier, vide, qui aura le nom du fichier .exe concerné et
l'extension ".exe.local"
C'est expliqué dans un article du MSDN (DVD)
ms-help://MS.MSDNQTR.2004OCT.1033/sbscs/setup/dll_com_redirection_on_windows.htm
Extrait :
DLL/COM redirection is activated by installing a special file
along with a copy of the local component file into the same
directory as the application's executable file.
The special file is an empty file named after the application
executable's file name and appended with .local.
For example, to activate DLL/COM redirection for an application
named Myapp, the local version of the component and an empty
file named Myapp.exe.local must be copied into the folder
containing Myapp.exe.
This binds the application to the local version of the component
rather than the globally shared version of the component.
When an application loads a component file, such as a DLL or
.ocx file, Windows first searches for it in the folder where the
application's .local and executable file is installed.
If found, the application uses that component file regardless
of any directory search path defined in the application or the
registry. If not found, the component file in the defined search
path is used.
The installation utility must do the following to install the
application with DLL/COM redirection:
- An empty .local file must be copied into the same folder
as the application's executable file.
- All of the components, DLL, and .ocx files used by the
application must be copied into the same folder as the
application's executable file.
- Isolated COM components must be registered with
Windows so that different versions of the assembly will
not conflict with each other when loaded into memory
at the same time. The registration process requires that,
while the implementation of the component can change
between versions, certain COM metadata such as CLSID,
ProgID, Type Library, and Threading Model cannot.
- If the application is installed using the Windows Installer,
then the application directory can be secured by using
the LockPermissions table. Typically, the system is given
read, write, and execute access; all other processes are
given only execute and read access.
For additional discussion about DLL/COM redirection, see the following white
paper "Implementing Side-by-side Component Sharing".
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsetup/html/sidebyside.asp
--
May the Force be with You!
La Connaissance s'accroît quand on la partage
----------------------------------------------------------
Jean-Claude BELLAMY [MVP] - http://www.bellamyjc.org
http://www.bellamyjc.org Jean-Claude.Bellamy@wanadoo.fr *
JC.Bellamy@free.fr
Dans le message news: , OfaMCT s'est ainsi exprimé:
Je cherche des infos sur les fichiers d'extension .exe.local qui serviraient à forcer l'exe à utiliser les DLL de son répertoire plutôt que les DLLs COM du système. Aucune info sur le Web et pourtant quand on renomme un fichier en .local, l'icône obtenue est celle des DLLs
Il ne s'agit pas de renommer un fichier .exe, mais de créer dans le même dossier un AUTRE fichier, vide, qui aura le nom du fichier .exe concerné et l'extension ".exe.local"
C'est expliqué dans un article du MSDN (DVD) ms-help://MS.MSDNQTR.2004OCT.1033/sbscs/setup/dll_com_redirection_on_windows.htm
Extrait :
DLL/COM redirection is activated by installing a special file along with a copy of the local component file into the same directory as the application's executable file. The special file is an empty file named after the application executable's file name and appended with .local. For example, to activate DLL/COM redirection for an application named Myapp, the local version of the component and an empty file named Myapp.exe.local must be copied into the folder containing Myapp.exe. This binds the application to the local version of the component rather than the globally shared version of the component.
When an application loads a component file, such as a DLL or .ocx file, Windows first searches for it in the folder where the application's .local and executable file is installed. If found, the application uses that component file regardless of any directory search path defined in the application or the registry. If not found, the component file in the defined search path is used.
The installation utility must do the following to install the application with DLL/COM redirection: - An empty .local file must be copied into the same folder as the application's executable file. - All of the components, DLL, and .ocx files used by the application must be copied into the same folder as the application's executable file. - Isolated COM components must be registered with Windows so that different versions of the assembly will not conflict with each other when loaded into memory at the same time. The registration process requires that, while the implementation of the component can change between versions, certain COM metadata such as CLSID, ProgID, Type Library, and Threading Model cannot. - If the application is installed using the Windows Installer, then the application directory can be secured by using the LockPermissions table. Typically, the system is given read, write, and execute access; all other processes are given only execute and read access.
For additional discussion about DLL/COM redirection, see the following white paper "Implementing Side-by-side Component Sharing". http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsetup/html/sidebyside.asp
-- May the Force be with You! La Connaissance s'accroît quand on la partage ---------------------------------------------------------- Jean-Claude BELLAMY [MVP] - http://www.bellamyjc.org http://www.bellamyjc.org *
