Update README.md

@@ -5,3 +5,8 @@ The Project builds a DLL file (LIL_VSTT_Plugins.dll) which you need to add a ref
 Building
 Building
 
 
 Build the Project using Release config and make sure you build for .NET Framework 4.5 if you want to use the TLS 1.2 features (see the Pages for more details). The solution also contains a Test Project, it is not needed for use of the plugins, it is only used to test the plugins during development.
 Build the Project using Release config and make sure you build for .NET Framework 4.5 if you want to use the TLS 1.2 features (see the Pages for more details). The solution also contains a Test Project, it is not needed for use of the plugins, it is only used to test the plugins during development.
+
+Versioning
+
+Itentionally, the file and build versions are currently being kept at 1.3.0.0. This is order to not break compatibility with web and load test files that make use of the plugin. Unfortunatly, if the file or build version of the DLL is changed, the DLL is no longer loaded  for that web test. Rebuilding does not help, since the version previously used is hard coded in text in the XML file for the web or load test. The plugin needs to be removed, and then added again, in order to work. When doing this, all property settings for the plugin are lost. A workarround if this happens, is to copy paste / drag and drop the plugin with its settings from the old web or load test into a new one, using the new version. This would require a potentialoly high amount of manual work each time a version is changed (even minor version changes that would not actually break compatibilty). For this reason, the file and build versions are no longer updated.
+This means that other mechanisms of versioning need to be used, like changing the name of the file and add a date or the build number. This is not done automatically but is recommended. You can also use diffrent paths and directories containg dates or build numbers to keep track of diffrent versions if you need. The best solution is to add the plugin DLL file to your solution and version control it together with the code that uses it. You can also add the entire DLL project to your project solution, add reference the project instead of a file. This way, your project always has the right "version" of the plugin, and you check out the code of the version that you need from the central GIT repository, and then check it into your own version control system with your test project.
\ No newline at end of file