search

tcunit / TcUnit

An unit testing framework for Beckhoff's TwinCAT 3
Other
273 stars 75 forks source link

Unifying visual studio versions across projects #44

Closed Roald87 closed 5 years ago

Roald87 commented 5 years ago

In the CONTRIBUTING.md you mention that we should use the same Visual Studio version number as the original solution file. I found that there are three different visual studio versions used:

I happen to have them all installed. Nevertheless it would be a good idea to use one version for all projects.

sagatowski commented 5 years ago

Good point. Do you know how to downgrade both verifiers to Visual Studio 2013?

Roald87 commented 5 years ago

Not sure, but why would you want to use 2013 and not Visual Studio 2017? I think 2017 also supports all TwinCAT functionality. VS2019 is not officially supported yet I think.

Can't you open the files in the visual studio version you want to have them and then upload that sln file? Not too much should change I think when you open it in another visual studio version.

sagatowski commented 5 years ago

For 3.1.4022 VS2017 is not yet fully supported (only partially). Also, considering VS2013 is the default installation with 4022 it makes the most sense.

Did you try if that works as you suggested?

Roald87 commented 5 years ago

Since a few months we made the switch to VS2017 and use 3.1.4022. So far we haven't noticed any lacking features. Beckhoff indeed mentioned that VS2017 supports ~95% of the functionality, whereas VS2015 is fully supported. They didn't share which features were not supported.

I haven't tried to open the projects with 2013 yet.

sagatowski commented 5 years ago

We tried VS2017 some ~6 months ago, but had several issues where we decided to go for the version that was default included with TwinCAT as it made unifying easier (VS2013, 2015, 21017 and all variants VS community, full, professional etc)

sagatowski commented 5 years ago

I'm working on the conversion now. Was (of course) much easier in theory than in reality. I think the easiest way is to just re-create both projects in VS2013.

sagatowski commented 5 years ago

Solved. All projects are using VS2013 now. Issue was solved by re-creating both projects and painstakingly copying one file at a time and making sure all project properties are correct. TcUnit-Verifier (TwinCAT and .NET) are tested working on a machine with VS2013.

Also updated CONTRIBUTING.md.

Aliazzzz commented 5 years ago

Hi all!

I am glad to hear that the IDE will stay vanilla installed Beckhoff VS2013. Whenever Beckhoff migrates we should migrate with them seamlessly. For now they provide VS2013 per default.

Sent from my Smartphone

From: Jakob Sagatowski notifications@github.com Sent: Tuesday, August 13, 2019 12:09:02 PM To: tcunit/TcUnit TcUnit@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [tcunit/TcUnit] Unifying visual studio versions across projects (#44)

Closed #44https://github.com/tcunit/TcUnit/issues/44.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/tcunit/TcUnit/issues/44?email_source=notifications&email_token=AH4C24HWBXGYG6KKJ2QTWELQEKB35A5CNFSM4IK7CDD2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTAUYOUI#event-2552858449, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH4C24GCKUNIFK6XEO5LLU3QEKB35ANCNFSM4IK7CDDQ.