UBIK Wiki / Augmensys - User contributions [en]

HowTo:Inject UI into UBIK Studio

2026-06-17T13:17:43Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will explain how to inject the desired UI. 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time an instance is dragged to a new tab header.
[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]]
 
=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module.
# Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project.
# Implement the interface IUBIKEnvironmentControl for the control.
# For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control.
#;<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
# The user control now has a property Description and Image.
# Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
#;<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
# Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder.
# After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls.

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window.
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]]
 

=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module.
# Add the designated window as a class deriving from System.Windows.Window to the project.
# Create a new class.
# Implement the inferface IUBIKWindowFactory for the new class.
# For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class.
#;<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.MyImage;

public string Label => Properties.Resources.MyLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
# The class now has a Icon and Label property.
# Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values.
# In the GetWindow method, return your window (step 2).
# Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder.
# After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu.
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T13:15:30Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will explain how to inject the desired UI. 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time an instance is dragged to a new tab header.
[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]]
 
=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module.
# Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project.
# Implement the interface IUBIKEnvironmentControl for the control.
# For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control.
#;<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
# The user control now has a property Description and Image.
# Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
#;<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
# Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder.
# After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls.

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]]
 

=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module.
# Add the designated window as a class deriving from System.Windows.Window to the project.
# Create a new class.
# Implement the inferface IUBIKWindowFactory for the new class.
# For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class.
#;<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.MyImage;

public string Label => Properties.Resources.MyLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
# The class now has a Icon and Label property.
# Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values.
# In the GetWindow method, return your window (step 2).
# Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder.
# After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu.
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T13:11:01Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI. 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new tab header.
[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]]
 
=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module.
# Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project.
# Implement the interface IUBIKEnvironmentControl for the control.
# For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control.
#;<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
# The user control now has a property Description and Image.
# Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
#;<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
# Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder.
# After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls.

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]]
 

=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module.
# Add the designated window as a class deriving from System.Windows.Window to the project.
# Create a new class.
# Implement the inferface IUBIKWindowFactory for the new class.
# For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class.
#;<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.MyImage;

public string Label => Properties.Resources.MyLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
# The class now has a Icon and Label property.
# Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values.
# In the GetWindow method, return your window (step 2).
# Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder.
# After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu.
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T12:05:50Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
[[File:InjectedUserControl.png|thumb|300px|Extended user control list]]
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new tab header.
=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
# Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
# Implement the interface IUBIKEnvironmentControl for the control. 
# For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
# The user control now has a property Description and Image. 
# Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
# Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
# After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
# Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
# Add the designated window as a class deriving from System.Windows.Window to the project. 
# Create a new class. 
# Implement the inferface IUBIKWindowFactory for the new class. 
# For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.MyImage;

public string Label => Properties.Resources.MyLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
# The class now has a Icon and Label property. 
# Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
# In the GetWindow method, return your window (step 2). 
# Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
# After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:38:33Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new tab header.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3. Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a vs .NET library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.MyImage;

public string Label => Properties.Resources.MyLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:28:22Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3. Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.MyImage;

public string Label => Properties.Resources.MyLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:26:50Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3. Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your user control in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:26:08Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3. Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:25:53Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the user control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:24:11Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed with the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:23:22Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:22:27Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will then display the values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your window in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new window can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:16:25Z

DAK:

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The values will then be displayed by the button and the menu entry. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:15:43Z

DAK: /* See also */

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The values will then be displayed by the button and the menu entry. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection Management]]
*

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:15:09Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The values will then be displayed by the button and the menu entry. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

==See also==
* [[Injection_Management#Injection_Folder.28s.29|Injection]]
*

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:13:45Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the desired window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The values will then be displayed by the button and the menu entry. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T11:13:09Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Goal ===
The goal is to extend the toolbar by injecting a button that opens the target window. 
In addition, the “View” menu will be extended with a new entry that also opens the window. 
[[File:InjectedButton.png|thumb|left|298px|Injected button]]
[[File:InjectedMenuEntry.png|thumb|left|508px|Injected menu entry]] 

=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The values will then be displayed by the button and the menu entry. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the toolbar as well as under the "View" menu. 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

File:InjectedMenuEntry.png

2026-06-17T10:56:48Z

DAK: File uploaded with MsUpload

File uploaded with MsUpload

HowTo:Inject UI into UBIK Studio

2026-06-17T07:58:26Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The values will then be displayed by the button and the menu entry. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the tool bar aswell as under menu entry "View". 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T07:56:39Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will then display these values. 
8. In the GetWindow method, return your window (step 2). 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the tool bar aswell as under menu entry "View". 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T07:52:38Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will then display these values. 
8. In the GetWindow method, return the window from step 2. 
9. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
10. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the tool bar aswell as under menu entry "View". 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T07:51:08Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources (example above). The button and the menu entry will then display these values. 
4. In the GetWindow method, return the window from step 2. 
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the tool bar aswell as under menu entry "View". 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T07:44:52Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated window as a class deriving from System.Windows.Window to the project. 
3. Create a new class. 
4. Implement the inferface IUBIKWindowFactory for the new class. 
5. For automatic injection, add the "Export" Attribute with the "IUBIKWindowFactory" type parameter to the designated class. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon =>Properties.Resources.IntelligentAtelierImage;

public string Label => Properties.Resources.IntelligentAtelierLabel;

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
6. The class now has a Icon and Label property. 
7. Set the values for both properties. The icon and label can be loaded directly from the .NET project's resources. The button and the menu entry will then display these values.
4. In the GetWindow method, return the window from step 2. 
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by the new button in the tool bar aswell as under menu entry "View". 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-17T06:18:15Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
The mentioned list pops up every time you drag an instance to a new window.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the User Control's constructor. The image and description can be loaded directly from the .NET project's resources. These values will then be displayed in the User Control list.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = Properties.Resources.Description;
Image = Properties.Resources.MyImage;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Paste your Window in the plugin solution. 
2. Create a new class that implements IUBIKWindowFactory.
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon => Image;

public string Label => "Test";

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
3. Assign values to the "Icon" and "Lable" properties they will be used for the button. 
4. In the GetWindow Method return the window that you moved to the solution. 
5. After making the changes, make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new button will show up in the tool bar. 
{{Template:HowTo/End}}

=See also=
tbd.

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-16T13:53:48Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
Every time you drag an instance to a new window, the mentioned list pops up.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the constructor of the User Control. The text of description and the image will show up in the User Control List.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = "test control";
Image = image;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [[Injection_Management#Injection_Folder.28s.29|Injection]] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Paste your Window in the plugin solution. 
2. Create a new class that implements IUBIKWindowFactory.
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon => Image;

public string Label => "Test";

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
3. Assign values to the "Icon" and "Lable" properties they will be used for the button. 
4. In the GetWindow Method return the window that you moved to the solution. 
5. After making the changes, make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new button will show up in the tool bar. 
{{Template:HowTo/End}}

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-16T13:52:43Z

DAK:

{{UnderConstructionStart}}

Since version 5.2 {{Version/ServerSince|5.2}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
===Goal===
The goal is to extend the existing user control list with the injected user control. 
Every time you drag an instance to a new window, the mentioned list pops up.

[[File:InjectedUserControl.png|thumb|left|735px|Extended user control list]] 
=== Implementation ===
1. Create or reuse a .Net library (DLL) project - it doesn't have to be a {{UBIK}} Module. 
2. Add the designated control as a class deriving from System.Windows.Forms.UserControl to the project. 
3.Implement the interface IUBIKEnvironmentControl for the control. 
4. For automatic injection, add the "Export" Attribute with the "IUBIKControl" type parameter to the designated control. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
5. The user control now has a property Description and Image. 
6. Set the properties in the constructor of the User Control. The text of description and the image will show up in the User Control List.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = "test control";
Image = image;
}
</syntaxhighlight>
7. Provide the updated DLL containing your UserControl in UBIK® Studio's [Injection_Management#Injection_Folder.28s.29|Injection] folder. 
8. After connecting to a database with UBIK® Studio, the new control can be accessed by right-clicking or dragging a UBIK® object on a tab header - it should appear in the list of possible controls. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Paste your Window in the plugin solution. 
2. Create a new class that implements IUBIKWindowFactory.
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon => Image;

public string Label => "Test";

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
3. Assign values to the "Icon" and "Lable" properties they will be used for the button. 
4. In the GetWindow Method return the window that you moved to the solution. 
5. After making the changes, make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new button will show up in the tool bar. 
{{Template:HowTo/End}}

[[Category:How-To|Inject UI into UBIK Studio]]
[[Category:Injecting|Inject UI into UBIK Studio]]
[[Category:Plugin|Inject UI into UBIK Studio]]
[[Category:Studio|Inject UI into UBIK Studio]]

HowTo:Inject UI into UBIK Studio

2026-06-16T13:44:07Z

DAK:

File:InjectedUserControl.png

2026-06-16T13:17:51Z

DAK: File uploaded with MsUpload

File uploaded with MsUpload

HowTo:Inject UI into UBIK Studio

2026-06-16T08:05:55Z

DAK:

HowTo:Inject UI into UBIK Studio

2026-06-16T07:56:31Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 {{Version/ServerSince|5.1}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
=== Overview ===
The existing User Control list can be extended to provide additional controls. 
[[File:ControlDropDown.png|thumb|left|220px|Extended user control list]] 
=== Implementation ===
1. Paste your UserControl in the plugin solution. 
2. Make your UserControl implements IUBIKEnvironmentControl and add the export. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
3. The user control now has a property Description and Image. 
4. Set the properties in the constructor of the User Control. The text of description and the image will show up in the User Control List.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = "test control";
Image = image;
}
</syntaxhighlight>
5. After making the changes make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new user control will show up in the list. 

= Window =
=== Overview ===
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Paste your Window in the plugin solution. 
2. Create a new class that implements IUBIKWindowFactory.
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon => Image;

public string Label => "Test";

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
3. Assign values to the "Icon" and "Lable" properties they will be used for the button. 
4. In the GetWindow Method return the window that you moved to the solution. 
5. After making the changes, make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new button will show up in the tool bar. 
{{Template:HowTo/End}}

[[Category:How-To]]
[[Category:Injecting]]
[[Category:Studio]]
[[Category:Plugin]]

HowTo:Inject UI into UBIK Studio

2026-06-16T07:51:33Z

DAK:

HowTo:Inject UI into UBIK Studio

2026-06-16T07:50:30Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 {{Version/ServerSince|5.1}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
The existing User Control list can be extended to provide additional controls. 
[[File:ControlDropDown.png|thumb|left|220px|Extended user control list]] 
=== Implementation ===
1. Paste your UserControl in the plugin solution. 
2. Make your UserControl implements IUBIKEnvironmentControl and add the export. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
3. The user control now has a property Description and Image. 
4. Set the properties in the constructor of the User Control. The text of description and the image will show up in the User Control List.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = "test control";
Image = image;
}
</syntaxhighlight>
5. After making the changes make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new user control will show up in the list. 

= Window =
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|290px|Injected button]] 
=== Implementation ===
1. Paste your Window in the plugin solution. 
2. Create a new class that implements IUBIKWindowFactory.
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon => Image;

public string Label => "Test";

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
3. Assign values to the "Icon" and "Lable" properties they will be used for the button. 
4. In the GetWindow Method return the window that you moved to the solution. 
5. After making the changes, make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new button will show up in the tool bar. 
{{Template:HowTo/End}}

HowTo:Inject UI into UBIK Studio

2026-06-16T07:48:54Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 {{Version/ServerSince|5.1}} it is possible to inject UI into {{UBIK}} Studio. 
The injected UI can be displayed inside a User Control and or Window. 
This article will help you to inject your UI! 
{{Template:HowTo/Begin}}
= User Control =
The existing User Control list can be extended to provide additional controls. 
[[File:ControlDropDown.png|thumb|left|220px|Extended user control list]] 
=== Implementation ===
1. Paste your UserControl in the plugin solution. 
2. Make your UserControl implements IUBIKEnvironmentControl and add the export. 
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKControl))]
public partial class TestUserControl: UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
3. The user control now has a property Description and Image. 
4. Set the properties in the constructor of the User Control. The text of description and the image will show up in the User Control List.
<syntaxhighlight lang="csharp">
public TestUserControl()
{
InitializeComponent();
Description = "test control";
Image = image;
}
</syntaxhighlight>
5. After making the changes make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new user control will show up in the list. 

= Window =
A additional button can be added to the tool bar
[[File:InjectedButton.png|thumb|left|298px|Injected button]] 
=== Implementation ===
1. Paste your Window in the plugin solution. 
2. Create a new class that implements IUBIKWindowFactory.
<syntaxhighlight lang="csharp">
[Export(typeof(IUBIKWindowFactory))]
public class TestWindowFactory : IUBIKWindowFactory
{
public Bitmap Icon => Image;

public string Label => "Test";

public Window GetWindow(UBIKEnvironment env)
{
return new TestWindow(env);
}
}
</syntaxhighlight>
3. Assign values to the "Icon" and "Lable" properties they will be used for the button. 
4. In the GetWindow Method return the window that you moved to the solution. 
5. After making the changes, make sure to update the plugin in the injection folder. 
6. When starting {{UBIK}} Studio the new button will show up in the tool bar. 
{{Template:HowTo/End}}

HowTo:Inject UI into UBIK Studio

2026-06-16T07:25:36Z

DAK:

HowTo:Inject UI into UBIK Studio

2026-06-16T07:12:57Z

DAK:

HowTo:Inject UI into UBIK Studio

2026-06-16T06:44:00Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 {{Version/ServerSince|5.1}} it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.

{{Template:HowTo/Begin}}

= User Control =
The existing User Control list can be extended to provide additional controls.
==== Implementation ====
Paste your User Control into your plugin solution.
Make your plugin implement IUBIKEnvironmentControl and add the export.
<syntaxhighlight lang="python">
[Export(typeof(IUBIKControl))]
public partial class CtrlAtelierHost : UserControl, IUBIKEnvironmentControl
</syntaxhighlight>
The user control now has a property Description and Image.
The text of description and the image will show up in the User Control List.
After making the changes make sure to update the plugin in the injection folder.

[[File:ControlDropDown.png|thumb|220px|Extended user control list]]

= Window =
A new button can be added to the UI and open the injected UI
[[File:InjectedButton.png|thumb|280px|Injected button]]

{{Template:HowTo/End}}

HowTo:Inject UI into UBIK Studio

2026-06-15T17:42:18Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 {{Version/ServerSince|5.1}} it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.

{{Template:HowTo/Begin}}

= User Control =
The existing User Control list can be extended to provide additional controls.
==== Implementation ====
It is enough to add the following code to your UserControl

<syntaxhighlight lang="python">
[Export(typeof(IUBIKControl))]
public partial class CtrlAtelierHost : UserControl, IUBIKEnvironmentControl
</syntaxhighlight>

[[File:ControlDropDown.png|thumb|220px|Extended user control list]]

= Window =
A new button can be added to the UI and open the injected UI
[[File:InjectedButton.png|thumb|280px|Injected button]]

{{Template:HowTo/End}}

HowTo:Inject UI into UBIK Studio

2026-06-15T16:33:25Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.

{{Template:HowTo/Begin}}

= User Control =
The existing User Control list can be extended to provide additional controls
[[File:ControlDropDown.png|thumb|220px|Extended user control list]]

= Window =
A new button can be added to the UI and open the injected UI
[[File:InjectedButton.png|thumb|280px|Injected button]]

{{Template:HowTo/End}}

HowTo:Inject UI into UBIK Studio

2026-06-15T16:31:40Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.

{{Template:HowTo/Begin}}

= User Control =
The existing User Control list can be extended to provide additional controls
[[File:ControlDropDown.png|thumb|220px|{{UBIK}} Studio]]

= Window =
A new button can be added to the UI and open the injected UI
[[File:InjectedButton.png|thumb|280px|{{UBIK}} Studio]]

{{Template:HowTo/End}}

File:InjectedButton.png

2026-06-15T16:30:41Z

DAK: File uploaded with MsUpload

File uploaded with MsUpload

File:ControlDropDown.png

2026-06-15T16:29:04Z

DAK: File uploaded with MsUpload

File uploaded with MsUpload

HowTo:Inject UI into UBIK Studio

2026-06-15T15:33:29Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.
[[File:UI_Studio.png|thumb|220px|{{UBIK}} Studio]]
[[File:UI_Studio.png|thumb|220px|{{UBIK}} Studio]]

=== User Control ===
The existing User Control list can be extended to provide additional controls

=== Window ===
A new button can be added to the UI and open the injected UI

{{Template:HowTo/Begin}}

= User Control =
Control

= Window =
Window

{{Template:HowTo/End}}

HowTo:Inject UI into UBIK Studio

2026-06-15T15:25:20Z

DAK:

{{UnderConstructionStart}}

Since version 5.1 it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.

=== User Control ===
[[File:UI_Studio.png|thumb|220px|{{UBIK}} Studio]]
The existing User Control list can be extended to provide additional controls

=== Window ===
[[File:UI_Studio.png|thumb|220px|{{UBIK}} Studio]]
A new button can be added to the UI and open the injected UI

{{Template:HowTo/Begin}}

= User Control =

==== USER CONTROL ====

= Window =

==== WINDOW ====

{{Template:HowTo/End}}

==See also==

{{UnderConstructionEnd}}

HowTo:Inject UI into UBIK Studio

2026-06-15T15:18:19Z

DAK: Created page with "{{UnderConstructionStart}} Since version 5.1 it is possible to inject UI into {{UBIK}} Studio. The injected UI can be displayed inside a User Control and or Window. === User..."

{{UnderConstructionStart}}

Since version 5.1 it is possible to inject UI into {{UBIK}} Studio.
The injected UI can be displayed inside a User Control and or Window.

=== User Control ===
The existing User Control list can be extended to provide additional controls

=== Window ===
A new button can be added to the UI and open the injected UI

{{Template:HowTo/Begin}}

= User Control =

==== USER CONTROL ====

= Window =

==== WINDOW ====

{{Template:HowTo/End}}

==See also==

{{UnderConstructionEnd}}

Import Runs

2025-11-25T13:29:38Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Blinding Operation Import =

To import Blinding Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* BlindingLocation (Text)
* Type (Text)
* BlindingPackage (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* Joint_Location_Number (Text)
* Name (Text)
* Remark (Text)
* Tag_Number (Text)
* Gasket_Type (Text)
* Flange_Spec (Text)
* Flange_Size (Text)
* Flange_Rating (Text)
* Bolt_Size (Text)
* Bolt_Number (Text)
* Bolt_Material (Text)
* Torque_Value (Text)
* Pressure (Text)
* Assembled_By (Text)
* Assembled Date (TT/MM/JJJJ hh:mm)
* Inspected_By (Text)
* Inspected_Date (TT/MM/JJJJ hh:mm)
* Equipment (Text)

= Blinding Location Import =

To import joint locations following columns are required:
* BlindingLocation_ID (Text)

Columns that can be imported additionally:
* No (Text)
* Equipment (Text)
* SOP (Text)
* Description (Text)
* BlindingNumber (Text)
* PID (Text)
* Size (Text)
* Type (Text)
* LocationType (Text)
* NormalPosition (Text)
* OnSite (Text)
* ICCNumber (Text)
* BlindSapNumber (Text)
* BlindQuantity (Number)
* GasketSAPNumber (Text)
* GasketQuantity (Number)
* Stage (Text)
* Height (Text)
* Scaff (Text)
* Insul (Text)
* Crane (Text)
* Remarks (Text)

[[Category:MaTaP|Import Runs]]

Import Runs

2025-11-25T13:24:42Z

DAK:

Import Runs

2025-11-17T14:22:58Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* Joint_Location_Number (Text)
* Name (Text)
* Remark (Text)
* Tag_Number (Text)
* Gasket_Type (Text)
* Flange_Spec (Text)
* Flange_Size (Text)
* Flange_Rating (Text)
* Bolt_Size (Text)
* Bolt_Number (Text)
* Bolt_Material (Text)
* Torque_Value (Text)
* Pressure (Text)
* Assembled_By (Text)
* Assembled Date (TT/MM/JJJJ hh:mm)
* Inspected_By (Text)
* Inspected_Date (TT/MM/JJJJ hh:mm)
* Equipment (Text)

[[Category:MaTaP|Import Runs]]

Import Runs

2025-11-17T14:22:32Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

[[Category:MaTaP|Import Runs]]

Import Runs

2025-11-17T14:17:48Z

DAK:

Import Runs

2025-11-17T14:17:39Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Blinding Operation Import =

To import Blinding Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* BlindingLocation (Text)
* BlindingPackage (Text)
* Type (Text)

= Joint Operation Import =

To import Joint Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Blinding Location Import =

To import Blinding Locations following columns are required:
* BlindingLocationID (Text)

Columns that can be imported additionally:
* No

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* No
* Equipment
* SOP
* Description
* BlindingNumber
* PID
* Size
* Type
* LocationType
* NormalPosition
* OnSite
* ICCNumber
* BlindSapNumber
* BlindQuantity
* GasketSAPNumber
* GasketQuantity
* Stage
* Height
* Scaff
* Insul
* Crane
* Remarks

[[Category:MaTaP|Import Runs]]