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: 160
Size: 48.9 KB]()
Update History
9 Apr 17: Realigned several elements to their correct namespace
10 Apr 17: Three minor mods
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 History
9 Apr 17: Realigned several elements to their correct namespace
10 Apr 17: Three minor mods
1) Fixed error noted in post #5 below
2) Fixed logic flaw that would only allow max of one <file> element imported
3) Added more detailed help when editing some attribute values via InputBox()
2) Fixed logic flaw that would only allow max of one <file> element imported
3) Added more detailed help when editing some attribute values via InputBox()