Difference between revisions of "CUSTOMIZING"
m |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
| purpose = Manage customizing versions | | purpose = Manage customizing versions | ||
| version = 2+ | | version = 2+ | ||
| + | | runtimetype = | ||
| + | | typestring = | ||
}} | }} | ||
| Line 53: | Line 55: | ||
== See also == | == See also == | ||
* [[HowTo:Register_additional_Assemblies_at_the_UBIK_Compiler]] | * [[HowTo:Register_additional_Assemblies_at_the_UBIK_Compiler]] | ||
| + | |||
| + | [[Category:Metaclasses|CUSTOMIZING]] | ||
Latest revision as of 15:14, 2 May 2016
The Customizing object gives information about one version of the compiled customized assemblies. Every time the user executes a compilation (both local and released) a new instance of customizing is created.
 Customizing |
|
|---|---|
| Name | CUSTOMIZING |
| Namespace | System.Main.Base |
| Internal Name | SystemObjects.CUSTOMIZINGVERSION |
| TypeString | |
| RuntimeType | |
| Purpose | Manage customizing versions |
| Version | 2+ |
Contents
Properties
Version number
The version number of a customizing consits of 3 numbers: Major.Minor.Revision
Major and Minor are linked to Major and Minor of the UBIK® Kernel version the customizing was compiled with. The Revision is increased by 1 with every compilation.
Kernel Version
The kernel Version number for which the current customizing was compiled for.
Comment
Additional comment describing the customizing.
Assembly and AssemblyUI File
Gives information about the filenames of the assemblies of the customizing.
Released
Indicates as the customizing is currently the released one. Only one customizing can be released per Kernel Version. Setting it to true will mark all other customizings (with the same Kernel Version) as not released.
Original Version
The Customizing Version which was active once the new once was compiled.
Methods
AddSystemAssemblies
Gives the possibility to define assemblies (by their name) which must be added to the UBIK Compiler every time it is asked to compile either the customizing or debugging code in the debugging test environment (Whobert).
Example:
{
List<string> assemblies = new List<string>();
string[] baseAssemblies = base.AddSystemAssemblies();
if (baseAssemblies != null)
{
assemblies.AddRange(baseAssemblies);
}
assemblies.Add( "System.Data.dll" );
return assemblies.ToArray();
}
