[v3.17.0.2]
I have a legacy solution that does not work well under newer vs versions due to 3rd party version dependencies.
I can go around this when executing NCRunch console at CI server (TC) via the /VS switch to enforce older version of MS build, but I lack this option for grid nodes.
Is it possible to ensure a grid node is running in a similar way as the ncrunch.exe does when /VS is specified?
(I work in vs2017, but tests are failing that depend on the older C# language, so it would be neat also in my dev experience to be able to connect to a "vs2013 capability grid node" which would then run the tests that are failing in vs2017. But I guess when trying to adopt grid nodes with ncrunch.exe it will fail due to the vs version mismatches?)
Thanks.
Remco NCrunch Developer
#12321
13 Jun 2018 09:44 UTC
The grid nodes don't have this switch implemented, because they are designed to use whichever version of VS is being used inside the NCrunch client (whether this is the console tool or the VS plugin).
Note that this will only work correctly if the grid node has the same tool versions installed as are on the client. Otherwise, it will first fall back, then fall forwards if it needs to.
Note that this will only work correctly if the grid node has the same tool versions installed as are on the client. Otherwise, it will first fall back, then fall forwards if it needs to.
FWIW, added related feature request https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/36182221-add-vs-switch-vstudio-version-to-grid-node-s
Post a reply
Log in to reply.