Free cookie consent management tool by TermsFeed Policy Generator

Changes between Version 11 and Version 12 of Documentation/DevelopmentCenter/CreateNewPluginUsingVS


Ignore:
Timestamp:
06/26/14 18:36:51 (10 years ago)
Author:
abeham
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/DevelopmentCenter/CreateNewPluginUsingVS

    v11 v12  
    2525== Configuring the project ==
    2626
    27 === !AssemblyInfo ===
    28 Optionally you can change your {{{AssemblyInfo.cs}}} file. This is useful is you want to publish multiple version of your plugin later.
    29 We set the !AssemblyVersion to the same value as the current !HeuristicLab major version by convention. The assembly version should be incremented if you use the HL serialization mechanism and want to signal a persistence break between two versions. The !AssemblyFileVersion is not used by !HeuristicLab and can be set without any restrictions:
     27=== Project properties ===
     28In the project's properties we configure: Assembly information, build, debug, and signing.
    3029
    31 [[Image(assembly_info.png)]]
     30Assembly information:: [[Image(assembly_info.png, align=right)]]
     31  We set the assembly version to the same value as the current HeuristicLab version by convention. 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 wants to load 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 or minor is different (e.g. 3.2.7, 3.4.3 or 4.0.1). The "Assembly file version" is not used by HeuristicLab and can be set without any restrictions.
    3232
    3333=== References ===