Lines Matching refs:policy
44 policy.x.y.cli_uretypes.dll
45 policy.x.y.cli_basetypes.dll
46 policy.x.y.cli_ure.dll
47 policy.x.y.cli_cppuhelper.dll
48 policy.x.y.cli_oootypes.dll (build in unoil)
50 The "x" and "y" in the names of the policy assemblies are to be replaces by version numbers. At the
53 policy.1.0.cli_uretypes.dll
54 policy.1.0.cli_basetypes.dll
55 policy.1.0.cli_ure.dll
56 policy.1.0.cli_cppuhelper.dll
57 policy.1.0.cli_ootypes.dll (build in unoil)
67 and policy assemblies. See step 1 for the names of those assemblies. Take down the version number a…
76 to the policy assembly. For example:
77 CLI_URETYPES_POLICY_VERSION refers to the policy assembly for cli_uretypes which is named
78 policy.1.0.cli_uretypes.dll
96 XYZ_POLICY_VERSION: change the version according to the version of the policy assembly from the
156 CLI_URETYPES_POLICY_ASSEMBLY=policy.1.0.cli_uretypes
164 cli_uretypes.config XML file which is part of the policy assembly. This is done automatically.
166 the policy file.
168 CLI_URETYPES_POLICY_VERSION represents the version of the policy file.
170 CLI_URETYPES_POLICY_ASSEMBLY represents the name of the policy file.
177 "old version" and the policy version must be changed as well. Using the former example,
182 CLI_URETYPES_POLICY_ASSEMBLY=policy.1.0.cli_uretypes
188 CLI_URETYPES_POLICY_ASSEMBLY=policy.2.0.cli_uretypes
191 redirect old client code to the new assembly. Actually we would not need a policy file here.
192 The name of the policy file has changed as well so as to refer to the new version. Since
193 the name is new and refers to the version 2 auf cli_uretypes, we can start with the policy version
200 CLI_URETYPES_POLICY_ASSEMBLY=policy.2.0.cli_uretypes
253 cli_uretypes.dll. Now the version of cli_uretypes.dll changes to version 2 and its policy assembly …
264 Neither assemblies nor policy assemblies may be rebased. This would