Changes between Version 3 and Version 4 of PlugIns

Timestamp:

2018-05-30 01:04:19 (6 years ago)

Author:

jeroens

Comment:

--

PlugIns

@@ -8 +8 @@
  * Start a new Class Library project with the same .NET framework dependencies and compiler model as the EwE software. For obtaining and running the code, see the [wiki:TechnicalFAQ Technical FAQ]
  * Make sure your plug-in targets the same .NET framework version that the project !ScientificInterface uses
- * Make sure your plug-in compiles for x86 and x64 solution platforms. Because of Microsoft Office reliance and its fixed bitness, the !EwE code does not use !AnyCPU
- * Add references to the !EwE assemblies !EwECore, !EwEUtils and !EwEPlugIn
- * Create one or more plug-in classes that implement one or more !EwE plug-in interfaces. Available plug-in interfaces are provided in Assemby !EwEPlugin, folder "Plugin Templates". The code that is placed in the implementation of these interfaces will be invoked when the EwE6 software encounters a plug-in point during its execution.
+ * Make sure your plug-in compiles for x86 and x64 solution platforms. Because of Microsoft Office reliance and its fixed bitness, the EwE code does not use AnyCPU
+ * Add references to the !EwE assemblies EwECore, EwEUtils and EwEPlugIn
+ * Create one or more plug-in classes that implement one or more EwE plug-in interfaces. Available plug-in interfaces are provided in Assemby EwEPlugin, folder "Plugin Templates". The code that is placed in the implementation of these interfaces will be invoked when the EwE6 software encounters a plug-in point during its execution.
  * Compile the plug-in, and place the compiled DLL beside the EwE6 executable.
- * Run !EwE.
+ * Run EwE.
 
 During development time it is advisable to reference your plug-in assembly from the EwE Scientific Interface project. This means that whenever EwE6 is compiled, your plug-in will be compiled and deployed with it.