question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Microsoft.NET.Test.Sdk is out of date, not flowing properly via darc

See original GitHub issue

5.0 has v16.3

https://github.com/dotnet/sdk/blob/release/5.0.1xx-preview1/eng/Versions.props#L60

https://github.com/dotnet/sdk/blob/bbff20c1e2a293835d0fcef16e55ff14bed7c72f/eng/Versions.props#L60

while 3.1.200 has v16.5

https://github.com/dotnet/toolset/blob/release/3.1.2xx/eng/Versions.props#L63

https://github.com/dotnet/toolset/blob/820400bd23e930ac7816c26fc085c1945977a240/eng/Versions.props#L63

image

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:10 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
wli3commented, Mar 1, 2020

@nohwnd Please set automated insertion to high priory. In the meanwhile, you team is responsible to manually tracking test sdk and templates etc to be in right version of SDK and VS. Our team try to keep up, however, as you can see, we could easily miss a release.

1reaction
mmitchecommented, Mar 2, 2020

Looks like this is pushing to the wrong channel?

Microsoft.NET.Test.Sdk @ 16.5.0
Repository:    https://github.com/microsoft/vstest
Branch:        master
Commit:        fd0fe3df347a081b56c4da89f85a3e1ff463a4e7
Build Number:  20200205-01
Date Produced: 2/4/2020 9:05 PM
Build Link:    https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=3444183
BAR Build Id:  41910
Released:      False
Channels:
- .NET Core Tooling Dev
Locations:
- https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json (NugetFeed)

I did notice that I got a Microsoft.NET.Test.Sdk when I took the eng feed to get an arcade.

Tooling is for general, non-version specific tools (e.g. symreader). It does not some seem like VSTest would fall into that category.

Read more comments on GitHub >

github_iconTop Results From Across the Web

The SDK 'Microsoft.NET.Sdk' specified could not be found. ...
NET.Sdk' specified could not be found." But if the project was opened in version 17.4, the project was loaded successfully. Visual Studio.
Read more >
Why is Microsoft.NET.Test.Sdk not added by default to an ...
1 Answer 1 ... That Microsoft.NET.Test.Sdk package is not needed by legacy .NET Framework projects (which are not migrated to the new SDK...
Read more >
How To Resolve Issue Of Test Project Not Running The ...
This article describes the scenario of unit test project not running the test cases in .NET project and the solution to this issue...
Read more >
The SDK 'Microsoft.Net.Sdk.Web' specified could not be ...
This article describes how to fix "The SDK 'Microsoft.Net.Sdk.Web' specified could not be found" when creating ASP.NET Core 2.0 projects in ...
Read more >
Msbuild get directory name. props imported, or something ...
NET SDK. Project project = new Microsoft. ... I my experience I would not recommed using the Nant MSBuild task, instead the easiest...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found