Create tests for TEST_FINISHED_NAMED in verifier

[sagatowski]

According to issue #38 in TcUnit: #38
a new function has been added called TEST_FINISHED_NAMED.

Add tests in the TcUnit-Verifier to verify that this works as expected

[slacAWallace]

@sagatowski I tried using this today, and I am afraid to say I ran into issues. Are there any installation requirements, packages, or other things I need to add to an environment before this will work?

When I run this in power-shell I get:
.\TcUnit-Verifier.exe -v "C:\Users\...\Documents\Source\TcUnit-Verifier\TcUnit-Verifier_TwinCAT\TcUnit -Verifier_TwinCAT.sln" 2019-08-12 23:57:52 - Starting TcUnit-Verifier... 2019-08-12 23:57:52 - Loading the Visual Studio Development Tools Environment (DTE)... 2019-08-12 23:57:52 - Error loading VS DTE. Is the correct version of Visual Studio installed? 2019-08-12 23:57:52 - Closing the Visual Studio Development Tools Environment (DTE), please wait... 2019-08-12 23:58:12 - Exiting application... PS C:\Users\...\Documents\Source\TcUnit-Verifier\TcUnit-Verifier_DotNet\TcUnit-Verifier\bin\Release>

[sagatowski]

@slacAWallace the problem was that TcUnit-Verifier_TwinCAT required you to have VS2015 installed (as this was the version used to develop it). The visual studio DTE (development tools environment) couldn't find it in your machine and thus you got the error.
An issue was recently created regarding this topic, Issue #44, which I just solved.
Now all software in TcUnit (TcUnit + TcUnit-Verifier_TwinCAT and TcUnit-Verifier_DotNet) is developed using VS2013. The contributing.MD has been updated and should answer any remaining questions regarding this.

[slacAWallace]

@sagatowski I am worried about this. I just tried a bit to get VS 2013 community and had trouble.

Do we simply need VS-shell 2013 to make this work and we can continue to work in 2017/19 or whatever?

[sagatowski]

@slacAWallace What was the problem with the download? I downloaded it yesterday and it went smooth.

The problem is that it's not possible to mix versions of Visual Studio for the three different projects. It's not possible to open a project made in a newer version in an older. It should work to open in a newer, but the risk is that VS overwrites the solution version information (xyz.sln), and then it won't be possible to open in an older again. You can try to see if this happens though. If VS leaves the sln-file alone it should be fine.