This is the second version of this application. The previous version will no longer be maintained.
The project simply creates application-manifests that can be written to disk, clipboard, or VB resource files. The project includes a default/dummy manifest with all known options, as of this date. You would select whichever manifest options you want to include and modify those option values as needed. If you wish to view or replace an existing manifest file, you can import it into the project via the clipboard, disk, or VB resource file. The tool will attempt to parse VB vbp project files and create a new manifest, filling in the Identity element from that file.
The major reasons for revision are several
- Previous version was create only. This version can also edit existing manifests.
- Use Microsoft XML in the background to create and modify the XML
- Use XML stylesheets to help transform the manifest based on export options
- More intuitive design and more modular to assist with future updates by you or me
- Will no longer ignore hand-jammed manifests within VB resource files, i.e., #24 custom entries
- Offers ability to update unrecognized (future) manifest entries imported from elsewhere
The manifest is designed to make use of XML qualified names, internally, and is the default mode. However, when exporting the manifest, you can opt to convert to traditional name spaces if you choose.
Caveat: Not 100% of the manifest options available have been fully tested. Some options can't be tested by me because I don't have the system(s) to perform the desired tests. However, all the options should be technically correct and in accordance with the Microsoft schema for application manifests.
Comments, bug reports, and suggested enhancements are always welcomed.
![Name: screenshot.jpg
Views: 28
Size: 48.9 KB]()
Update (already). Will remove/replace the following upon next update...
After countless attempts to definitively determine which options belonged to which WindowsSettings namespace, my registry had it all along. Just didn't know where to look. As a result, much of the 2011 namespace was proven incorrect and current zip has changes made. Removed magicFutureSetting since I could not verify its namespace and found a new setting: forceFocusBasedMouseWheel in the registry. However, could not find any documentation for its values. I got my external VB6 manifest fired up & further validated all settings by getting VB to run without triggering "Activation context generation" failures after including all possible manifest options (except NoInherit). MSDN schema describes all of these options belonging to the 2011 namespace, but only 2 are correct per the registry. Corrections made to the right:
The project simply creates application-manifests that can be written to disk, clipboard, or VB resource files. The project includes a default/dummy manifest with all known options, as of this date. You would select whichever manifest options you want to include and modify those option values as needed. If you wish to view or replace an existing manifest file, you can import it into the project via the clipboard, disk, or VB resource file. The tool will attempt to parse VB vbp project files and create a new manifest, filling in the Identity element from that file.
The major reasons for revision are several
- Previous version was create only. This version can also edit existing manifests.
- Use Microsoft XML in the background to create and modify the XML
- Use XML stylesheets to help transform the manifest based on export options
- More intuitive design and more modular to assist with future updates by you or me
- Will no longer ignore hand-jammed manifests within VB resource files, i.e., #24 custom entries
- Offers ability to update unrecognized (future) manifest entries imported from elsewhere
The manifest is designed to make use of XML qualified names, internally, and is the default mode. However, when exporting the manifest, you can opt to convert to traditional name spaces if you choose.
Caveat: Not 100% of the manifest options available have been fully tested. Some options can't be tested by me because I don't have the system(s) to perform the desired tests. However, all the options should be technically correct and in accordance with the Microsoft schema for application manifests.
Comments, bug reports, and suggested enhancements are always welcomed.
Update (already). Will remove/replace the following upon next update...
After countless attempts to definitively determine which options belonged to which WindowsSettings namespace, my registry had it all along. Just didn't know where to look. As a result, much of the 2011 namespace was proven incorrect and current zip has changes made. Removed magicFutureSetting since I could not verify its namespace and found a new setting: forceFocusBasedMouseWheel in the registry. However, could not find any documentation for its values. I got my external VB6 manifest fired up & further validated all settings by getting VB to run without triggering "Activation context generation" failures after including all possible manifest options (except NoInherit). MSDN schema describes all of these options belonging to the 2011 namespace, but only 2 are correct per the registry. Corrections made to the right:
Quote:
Originally Posted by msdn
<!-- WindowsSettings elements from XML namespace http://schemas.microsoft.com/SMI/2011/WindowsSettings -->
<ElementType name="autoElevate" /> [really 2005]
<ElementType name="disableTheming" /> [really 2005]
<ElementType name="disableWindowFiltering" /> [correct]
<ElementType name="dpiAware" /> [really 2005]
<ElementType name="highResolutionScrollingAware" /> [really 2013]
<ElementType name="magicFutureSetting" /> [unknown]
<ElementType name="printerDriverIsolation" /> [correct]
<ElementType name="ultraHighResolutionScrollingAware" /> [really 2013]
<!-- WindowsSettings elements from XML namespace http://schemas.microsoft.com/SMI/2016/WindowsSettings -->
<ElementType name="dpiAwareness" [correct] />
<ElementType name="autoElevate" /> [really 2005]
<ElementType name="disableTheming" /> [really 2005]
<ElementType name="disableWindowFiltering" /> [correct]
<ElementType name="dpiAware" /> [really 2005]
<ElementType name="highResolutionScrollingAware" /> [really 2013]
<ElementType name="magicFutureSetting" /> [unknown]
<ElementType name="printerDriverIsolation" /> [correct]
<ElementType name="ultraHighResolutionScrollingAware" /> [really 2013]
<!-- WindowsSettings elements from XML namespace http://schemas.microsoft.com/SMI/2016/WindowsSettings -->
<ElementType name="dpiAwareness" [correct] />