reactos/base/shell/filebrowser/browseui.sxs.manifest
Giannis Adamopoulos f47e7d9c12 [filebrowser]
- Do not embed a manifest in the resources in order to allow three different scenarios that can be accomplished by using two manifests
- In the first scenario we have filebrowser.exe + filebrowser.exe.manifest in the same folder. This should work only in windows xp, 2003 and reactos as it depends on the browseui that exists in windows
- The second scenario is to have filebrowser.exe + filebrowser.exe.manifest + browseui.dll in the same folder. This should also work in the same platforms as above but the core of the file browser will be used from the supplied browseui. However browseui will also request to instantiate some com objects implemented in browse and as a result some objects will be used from the browseui that exists in windows
- The third scenario is to have filebrowser.exe + filebrowser.exe.regfree.manifest + browseui.dll + browseui.sxs.manifest. This scenario should work in windows xp and all later versions. Note that filebrowser.exe.regfree.manifest must be renamed to filebrowser.exe.manifest. In this scenario all the functionality of the file browser window is used from the supplied browseui.dll

svn path=/branches/shell-experiments/; revision=62081
2014-02-09 21:23:07 +00:00

26 lines
1 KiB
XML

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
type="win32"
name="browseui.sxs"
version="6.0.2900.2180" />
<file name="browseui.dll">
<comClass clsid="{0BE35200-8F91-11CE-9DE3-00AA004BB851}"/>
<comClass clsid="{00BB2765-6A77-11D0-A535-00C04FD7D062}"/>
<comClass clsid="{01E04581-4EEE-11d0-BFE9-00AA005B4383}"/>
<comClass clsid="{A08C11D2-A228-11d0-825B-00AA005B4383}"/>
<comClass clsid="{F61FFEC1-754F-11d0-80CA-00AA005B4383}"/>
<comClass clsid="{ECD4FC4D-521C-11D0-B792-00A0C90312E1}"/>
<comClass clsid="{ECD4FC4E-521C-11D0-B792-00A0C90312E1}"/>
<comClass clsid="{22BF0C20-6DA7-11D0-B373-00A0C9034938}"/>
<comClass clsid="{AF604EFE-8897-11D1-B944-00A0C90312E1}"/>
<comClass clsid="{EF8AD2D1-AE36-11D1-B2D2-006097DF8C11}"/>
<comClass clsid="{5E6AB780-7743-11CF-A12B-00AA004AE837}"/>
<comClass clsid="{AF4F6510-F982-11d0-8595-00AA004CD6D8}"/>
</file>
</assembly>