You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For more details related to Plugin Framework's background, please see the following [introduction article from InfoQ](https://www.infoq.com/articles/Plugin-Framework-DotNet/).
85
+
80
86
## Main concepts
81
87
82
88
Using Plugin Framework concentrates mainly around two concepts: **Plugins** and **Plugin Catalogs**.
// 1. Uses folder catalog to add calculation operations inside the app. Mimics the WPF-sample.
21
-
awaitAddCalculationOperators();
24
+
// Demonstrates how tags can be used with Plugin Framework.
25
+
// Single _allPlugins catalog is created from multiple different catalogs. All the plugins are tagged.
26
+
awaitCreateCatalogs();
27
+
28
+
// 1. Adds calculation operators using tag 'operator'
29
+
AddCalculationOperators();
22
30
23
-
// 2. Another folder catalog is used to add other forms inside the app. For each form a button is added into the toolstrip
24
-
// Note: WinFormsPluginsLibrary must be manually built as it isn't referenced by this sample app
25
-
// Note: Program.cs contains an initialization code which is required. Without it, we will get an exception about a missing reference. This is something we hope to get around in the future versions of Plugin Framework.
26
-
awaitAddDialogs();
31
+
// 2. Adds dialogs using 'dialog' tag
32
+
AddDialogs();
27
33
28
-
// 3. Lastly, DelegateCatalog is used for creating an exit-button
29
-
awaitAddExitButton();
34
+
// 3. Adds buttons using 'button' tag
35
+
AddButtons();
30
36
}
31
37
32
-
privateasyncTaskAddCalculationOperators()
38
+
privateasyncTaskCreateCatalogs()
33
39
{
40
+
// 1. Uses folder catalog to add calculation operations inside the app. Mimics the WPF-sample.
0 commit comments