Ignore:
Timestamp:
06/26/14 17:59:50 (5 years ago)
Comment:

--

### Legend:

Unmodified
 v14 === New plugin with Visual Studio === * Open a new instance of Visual Studio 2012 or later * Select "File > New > Project..." or press * In the dialog on the top select ".NET Framework 4" * On the right choose "Other Project Types > Visual Studio Solutions" and select the "Blank Solution" template or alternatively type "Blank Solution" in the search box on the right * Use "GreatIdea" as Name and click "Browse..." to select the extension folder and click Ok * In the Solution Explorer right-click the "GreatIdea" solution and select "Add > New Project..." * On the right choose "Visual C#" and select the "Class Library" template * As name pick "HeuristicLab.GreatIdea.ThePlugin" You're presented with a minimal project set up for developing a new class library (dll). Before we continue we want to adjust the project configuration to make development convenient. * Open the project properties and go to "Build" * Change the first box from "Active (Debug)" to "All Configurations" * Enter ..\..\..\stable\bin in the output path * Then click on "Debug" on the left, choose "Start external program" and select HeuristicLab.exe inside StableRoot\bin - this setting is stored in the .csproj.user file * Then click on "Signing" on the left, activate "Sign the assembly" and create a new key * Call it "TheKey", but deselect the password option * Save the project and close the properties This ensures that the generated plugin is automatically added as a plugin to the HeuristicLab build and that we can use our solution to start a debugging session (shortcut ). Now, we want to make this class library a HeuristicLab plugin. This requires that we include a special class that designates this dll to be a plugin. * For the project add a reference to HeuristicLab.PluginInfrastructure.dll in StableRoot\bin * Open the properties of the reference and set "Copy Local" to false Later on in your developments you will have to add additional plugins as references, but the procedure is always the same. * Rename Class1.cs to Plugin.cs by selecting it and pressing * Replace the code in the file with the following code snippet {{{ #!csharp using HeuristicLab.PluginInfrastructure; namespace HeuristicLab.GreatIdea.ThePlugin { [Plugin("HeuristicLab.GreatIdea.ThePlugin", "Provides an implementation of a great idea", "3.3.9.0")] [PluginFile("HeuristicLab.GreatIdea.ThePlugin.dll", PluginFileType.Assembly)] public class Plugin : PluginBase { } } }}} '''Important''': The plugin class needs to derive from HeuristicLab.PluginInfrastructure.PluginBase so that the dll is realized as a plugin. The attributes specify the details of the plugin and which files it provides. The filename given in PluginFile has to be the same as the assembly output filename in the "Application" tab of the project's properties. '''Important''': Version numbers for plugins can be specified in the style major.minor.build.revision. In the official HeuristicLab repository the revision part is synchronized with the SVN revision number, it can be simply set to 0 in our case. Changing major or minor version numbers in the course of development marks a breaking change to previously saved files. If HeuristicLab's persistence comes across an item of a plugin with version 3.3.8 it will accept the same plugin in version 3.3.9 to open it. However, it will reject the plugin when its major.minor is different (e.g. 3.2.7, 3.4.3 or 4.0.1). For this reason HeuristicLab plugin assemblies are always marked with major and minor numbers at the end, e.g. HeuristicLab.Core-3.3.dll. This allows to have the same assembly in two conflicting versions. * Build the project and press to start it without a debugger attached * You will see the starter window again, but you already know the switches to hide it * Inside the starter open the "Plugin Manager" and see that it is correctly loaded Now we have created an empty plugin that we can use to implement our great idea. Please refer to the [[Documentation]] pages and the various HowTos on how to write views, operators, algorithms, etc. * Follow the instructions on how to [[Documentation/DevelopmentCenter/CreateNewPluginWithVS|create HeuristicLab plugins with Visual Studio]] === New plugin with SharpDevelop === We can now build HeuristicLab and extends it with own plugins. Below are some remarks for experienced developers. * Follow the instructions on how to [[Documentation/DevelopmentCenter/CreateNewPluginWithSD|create HeuristicLab plugins with SharpDevelop]] == For the experienced ==