VSTest Task running v1 when v2 expected, vstestLocation ignored
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm trying to use Azure Pipelines to build a class library. My azure-pipelines.yml looks like this:
variables:
solution: 'MySolution.sln'
buildPlatform: 'Any CPU'
buildConfiguration: 'Release'
pool:
vmImage: 'VS2017-Win2016'
steps:
- task: NuGetToolInstaller@0
- task: NuGetCommand@2
inputs:
command: 'restore'
restoreSolution: '$(solution)'
feedsToUse: 'config'
nugetConfigPath: 'nuget.config'
- task: VSBuild@1
inputs:
solution: '$(solution)'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
- task: VSTest@2
inputs:
vstestLocation: 'C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
codeCoverageEnabled: true
otherConsoleOptions: '/Framework:FrameworkCore10'
However, the task runs from a different location, and judging by that it seems to be Test Platform v1 (TP v1): C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe. Judging from the Github issues for azure-pipelines-tasks, it seems that they shipped TP v2 sometime earlier this year (2018).
How can I make sure I'm actually using TP v2?
Update: I've now opened an issue on the pipelines github repo: Microsoft/azure-pipelines-tasks#8911
visual-studio-2017
azure-devops azure-pipelines azure-pipelines-build-task asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
add a comment |
I'm trying to use Azure Pipelines to build a class library. My azure-pipelines.yml looks like this:
variables:
solution: 'MySolution.sln'
buildPlatform: 'Any CPU'
buildConfiguration: 'Release'
pool:
vmImage: 'VS2017-Win2016'
steps:
- task: NuGetToolInstaller@0
- task: NuGetCommand@2
inputs:
command: 'restore'
restoreSolution: '$(solution)'
feedsToUse: 'config'
nugetConfigPath: 'nuget.config'
- task: VSBuild@1
inputs:
solution: '$(solution)'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
- task: VSTest@2
inputs:
vstestLocation: 'C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
codeCoverageEnabled: true
otherConsoleOptions: '/Framework:FrameworkCore10'
However, the task runs from a different location, and judging by that it seems to be Test Platform v1 (TP v1): C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe. Judging from the Github issues for azure-pipelines-tasks, it seems that they shipped TP v2 sometime earlier this year (2018).
How can I make sure I'm actually using TP v2?
Update: I've now opened an issue on the pipelines github repo: Microsoft/azure-pipelines-tasks#8911
visual-studio-2017
azure-devops azure-pipelines azure-pipelines-build-task asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
1
Did you try using the VSTest platform installer? docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/…
– Daniel Mann
Nov 26 '18 at 18:46
@DanielMann I had not tried that; I assumed TP v2 would be packaged with the hosted VS2017 build agent. However, I did try just now and I don't notice any difference in behavior, including when I remove thevstestLocationproperty
– Ben Collins
Nov 26 '18 at 21:26
add a comment |
I'm trying to use Azure Pipelines to build a class library. My azure-pipelines.yml looks like this:
variables:
solution: 'MySolution.sln'
buildPlatform: 'Any CPU'
buildConfiguration: 'Release'
pool:
vmImage: 'VS2017-Win2016'
steps:
- task: NuGetToolInstaller@0
- task: NuGetCommand@2
inputs:
command: 'restore'
restoreSolution: '$(solution)'
feedsToUse: 'config'
nugetConfigPath: 'nuget.config'
- task: VSBuild@1
inputs:
solution: '$(solution)'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
- task: VSTest@2
inputs:
vstestLocation: 'C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
codeCoverageEnabled: true
otherConsoleOptions: '/Framework:FrameworkCore10'
However, the task runs from a different location, and judging by that it seems to be Test Platform v1 (TP v1): C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe. Judging from the Github issues for azure-pipelines-tasks, it seems that they shipped TP v2 sometime earlier this year (2018).
How can I make sure I'm actually using TP v2?
Update: I've now opened an issue on the pipelines github repo: Microsoft/azure-pipelines-tasks#8911
visual-studio-2017
azure-devops azure-pipelines azure-pipelines-build-task asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
I'm trying to use Azure Pipelines to build a class library. My azure-pipelines.yml looks like this:
variables:
solution: 'MySolution.sln'
buildPlatform: 'Any CPU'
buildConfiguration: 'Release'
pool:
vmImage: 'VS2017-Win2016'
steps:
- task: NuGetToolInstaller@0
- task: NuGetCommand@2
inputs:
command: 'restore'
restoreSolution: '$(solution)'
feedsToUse: 'config'
nugetConfigPath: 'nuget.config'
- task: VSBuild@1
inputs:
solution: '$(solution)'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
- task: VSTest@2
inputs:
vstestLocation: 'C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
codeCoverageEnabled: true
otherConsoleOptions: '/Framework:FrameworkCore10'
However, the task runs from a different location, and judging by that it seems to be Test Platform v1 (TP v1): C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe. Judging from the Github issues for azure-pipelines-tasks, it seems that they shipped TP v2 sometime earlier this year (2018).
How can I make sure I'm actually using TP v2?
Update: I've now opened an issue on the pipelines github repo: Microsoft/azure-pipelines-tasks#8911
visual-studio-2017
azure-devops azure-pipelines azure-pipelines-build-task visual-studio-2017
azure-devops azure-pipelines azure-pipelines-build-task asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
edited Nov 28 '18 at 14:50
Ben Collins
asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
asked Nov 26 '18 at 18:43
Ben CollinsBen Collins
15.4k12110169
15.4k12110169
1
Did you try using the VSTest platform installer? docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/…
– Daniel Mann
Nov 26 '18 at 18:46
@DanielMann I had not tried that; I assumed TP v2 would be packaged with the hosted VS2017 build agent. However, I did try just now and I don't notice any difference in behavior, including when I remove thevstestLocationproperty
– Ben Collins
Nov 26 '18 at 21:26
add a comment |
1
Did you try using the VSTest platform installer? docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/…
– Daniel Mann
Nov 26 '18 at 18:46
@DanielMann I had not tried that; I assumed TP v2 would be packaged with the hosted VS2017 build agent. However, I did try just now and I don't notice any difference in behavior, including when I remove thevstestLocationproperty
– Ben Collins
Nov 26 '18 at 21:26
1
1
Did you try using the VSTest platform installer? docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/…
– Daniel Mann
Nov 26 '18 at 18:46
Did you try using the VSTest platform installer? docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/…
– Daniel Mann
Nov 26 '18 at 18:46
@DanielMann I had not tried that; I assumed TP v2 would be packaged with the hosted VS2017 build agent. However, I did try just now and I don't notice any difference in behavior, including when I remove the
vstestLocation property– Ben Collins
Nov 26 '18 at 21:26
@DanielMann I had not tried that; I assumed TP v2 would be packaged with the hosted VS2017 build agent. However, I did try just now and I don't notice any difference in behavior, including when I remove the
vstestLocation property– Ben Collins
Nov 26 '18 at 21:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53487197%2fvstest-task-running-v1-when-v2-expected-vstestlocation-ignored%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53487197%2fvstest-task-running-v1-when-v2-expected-vstestlocation-ignored%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Did you try using the VSTest platform installer? docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/…
– Daniel Mann
Nov 26 '18 at 18:46
@DanielMann I had not tried that; I assumed TP v2 would be packaged with the hosted VS2017 build agent. However, I did try just now and I don't notice any difference in behavior, including when I remove the
vstestLocationproperty– Ben Collins
Nov 26 '18 at 21:26