Custom Rules Reference - Novell ADMINSTUDIO 9.5 User Manual

Chapter 9: Converting Windows Installer Packages to Virtual Applications
Testing Windows Installer Packages for Virtualization Compatibility
</Action>
5. Save the XML file. The final results should look similar to this example:
<?xml version="1.0" encoding="utf-8"?>
<AdminStudioRules xmlns="http://adminstudio.com/AdminStudio.Rules.xsd"
xmlns:xsi="http:www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=
"http://adminstudio.com/AdminStudio.Rules.xsd AdminStudio.Rules.xsd">
<Rule title="My Rule Title" description="My Rule Description"
author="Author" provider="Any">
</Rule>
</AdminStudioRules>
6. Build any virtual package and you will see your Warning message.

Custom Rules Reference

This section includes descriptions of the Rule elements that you can use to create a custom Rule for use in virtual
package testing and conversion using Windows Installer Converter.
•
Rule Element
•
Fingerprint Element
•
Registry Element
•
File Element
•
Shortcut Element
•
Action Element
•
Message Element
•
Exclude Element
•
FullyIsolate Element
•
PunchThrough Element
•
Create Element
Rule Element
A Rule element is the basic definition for a rule. It is a child element of the
to define multiple rules, you would simply create multiple Rule elements. Here is an example of a Rule element:
<Rule title="MyRuleTitle" description="MyRuleDescription" author="Author" provider="Any">
</Rule>
The Rule Element has both attributes and child elements.
674
<Fingerprint name="Always Satisfied" description=""> </Fingerprint>
<Action description="My First Action">
<Message id="12000" text="I will automate my knowledge" severity="Warning"/>
</Action>
element. If you wanted
AdminStudioRules
ADS-0950-UG00 AdminStudio 9.5 User Guide