Skip to content

Products / VSTT-Plugins

Go to a project
Toggle navigation
Toggle navigation pinning
Commit 52310a19 52310a195eef59914ea4328469532ac0d5c78933 by Christian Gerdes
Options

Update README.md

1 parent 5cf07184
Inline Side-by-side
Showing 1 changed file with 9 additions and 2 deletions
1 Visual Studio Load and Web Test plugins by LIL 1 Visual Studio Load and Web Test plugins by LIL
2 2
3 The Project builds a DLL file (LIL_VSTT_Plugins.dll) which you need to add a reference to in your Test Project in order to use the plugins. The file will by default be distributed to agents during a loadtest. If you want easy access to this DLL for all users, you can copy the file to the PublicAssemblies folder in VS install directory (C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PublicAssemblies for VS2015). This way VS will be able to automatically find the file for Projects already containing a reference, unless you place a copy of the dll file in each Test Project (create a lib directory and copy the dll to it, add a reference by browsing to the dll file). 3 The Project builds a DLL file (LIL_VSTT_Plugins.dll) which you need to add a reference to in your Test Project in order to use the plugins. Either copy the project into your Test Project's Solution, and reference the project in your Test Project, or place a copy of the built dll file in each Test Project (create a lib directory and copy the dll to it, add the DLL file as an existing item, and add a reference in your test project by browsing to the dll file). The DLL will be deployed automatically to all agents in your test rig.
4 4
5 Building 5 Building
6 6
7 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. 7 Pre build versions of the DLL and the PDB Debug symbols files are available in the project wiki home page for download. Please remember to remove the blocking of the file that windows does for downloaded executable files, otherwise it will not load. Most windows setups also block executable files on shared filesystems, so you might want to place the file local.
8
9 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 Wiki 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.
8 10
9 Versioning 11 Versioning
10 12
11 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. 13 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.
12 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. 14 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.
15
16 Project Gitlab
17 https://git.lightsinline.se/products/VSTT-Plugins
18
19 This project is maintained on a GitLab server, where you can find the latest code, builds, issues and documention. Register an account (for free) if you want to fork clone the project and get a personal repository and project home and maintain your own version, get support or create issues. If you create code you want to share, you are welcome to create a merge request to get it added to the master branch.
...\ No newline at end of file ...\ No newline at end of file
......