Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PowerShell Tools for Visual Studio 2017 pulls in incompatible assembly references #844

Closed
spati2 opened this issue Jun 7, 2017 · 2 comments
Closed

PowerShell Tools for Visual Studio 2017 pulls in incompatible assembly references #844

spati2 opened this issue Jun 7, 2017 · 2 comments
Assignees
@Faizan2304

Comments

@spati2
Copy link

spati2 commented Jun 7, 2017

I am using a netcore project and I noticed that the Powershell extension pulls in reference to log4net (v2.0.3) which is incompatible with netcore for a a Xunit test case

Steps to reproduce

Please follow steps in #632
Use the test repo https://github.com/ddrinka/aws-sdk-net-log4net-bug

Expected behavior

The XUnit test case should execute without issues

Actual behavior

Test fails

Environment

Visual Studio 2017 (with the PowerShell component installed)
Operating system, Build version of vstest.console
@codito
Copy link
Contributor

codito commented Jun 8, 2017

Likely same root cause as #632.

@Faizan2304 Faizan2304 self-assigned this Jun 13, 2017
Faizan2304 pushed a commit to Faizan2304/vstest that referenced this issue Jun 13, 2017
Fix for issue:
1f70d32 
1) microsoft#632
2) microsoft#844
Faizan2304 added a commit that referenced this issue Jun 15, 2017
@Faizan2304
Clear extensions cache after discover/execution complete. (#853)
0eef86b 
* Clear cache after discover/execution complete.

* Sort usings

* Fix for issue:
1) #632
2) #844

* nitpick: Spelling

* Addressed PR comment

* spelling correction

* nitpick: function name

* Removed unused usings
@Faizan2304
Copy link
Contributor

Fix will come in next preview of visual studio, most probably visual studio 2017 update3 preview3 will have it.

Faizan2304 added a commit to Faizan2304/vstest that referenced this issue Jun 15, 2017
@Faizan2304
Clear extensions cache after discover/execution complete. (microsoft#853
eb6ff3f 
)

* Clear cache after discover/execution complete.

* Sort usings

* Fix for issue:
1) microsoft#632
2) microsoft#844

* nitpick: Spelling

* Addressed PR comment

* spelling correction

* nitpick: function name

* Removed unused usings

(cherry picked from commit 0eef86b)
Faizan2304 added a commit that referenced this issue Jun 15, 2017
@Faizan2304
Port changes from master (#868)
53b0d95 
* Clear extensions cache after discover/execution complete. (#853)

* Clear cache after discover/execution complete.

* Sort usings

* Fix for issue:
1) #632
2) #844

* nitpick: Spelling

* Addressed PR comment

* spelling correction

* nitpick: function name

* Removed unused usings

(cherry picked from commit 0eef86b)

* Add portable pdb support for net46. (#856)

(cherry picked from commit c70c0c8)

* Install shared farmework compatible with particular version of CLI (#857)

(cherry picked from commit 322bf71)
@Faizan2304 Faizan2304 mentioned this issue Jun 18, 2017
Merged
livarcocc added a commit to dotnet/cli that referenced this issue Jun 20, 2017
@livarcocc
Merge remote-tracking branch 'dotnet/release/2.0.0' into merges/relea…
9258d7c 
…se/2.0.0-to-master-20170620-070043

* dotnet/release/2.0.0: (34 commits)
  Simple clean up to the store tests
  Updating xlf files for the Configurer.
  Removing NuGetConfig from the first run experience and replacing the sentinel with the FirstUseNoticeSentinel when needed.
  Moving the expanding fallback folder to the dotnet folder hive. The folder will be expanded at sdk/NuGetFallbackFolder.
  Fixing CRLF issue.
  Updating xlf and fixing line ending problems with one file.
  Add rhel and Debian download link
  Fix race in telemetry msbuild arg tests
  Avoid repeating the first-run message if lzma archive is missing
  Use fluent helper for line-end normalization
  Update CoreSetup to preview3-25419-01
  Updating Roslyn to 2.3.0-beta3-61816-04
  Update CoreSetup to preview3-25418-01
  insert new tpv2 which fixes following issue microsoft/vstest#632 microsoft/vstest#844 microsoft/vstest#847 microsoft/vstest#840 microsoft/vstest#843
  Windows installer refresh
  Update SDK to 1.1.0-alpha-20170615-3
  Updating NuGet to 4.3.0-preview3-4168
  MSBuild 15.3.388
  Make dotnet-sln-add.Tests pass on localized setup
  Make dotnet-sln-list.Tests pass on localized setup
  ...
livarcocc added a commit to dotnet/cli that referenced this issue Jun 21, 2017
@livarcocc
Merge remote-tracking branch 'dotnet/release/2.0.0' into merges/relea…
5cab325 
…se/2.0.0-to-master-20170621-070039

* dotnet/release/2.0.0: (35 commits)
  Fixing an issue in the RepoDirectoriesProvider where it assumed that the only directory under SDK was the SDK directories. This is no longer true now that we moved the NuGet fallback folder there.
  Simple clean up to the store tests
  Updating xlf files for the Configurer.
  Removing NuGetConfig from the first run experience and replacing the sentinel with the FirstUseNoticeSentinel when needed.
  Moving the expanding fallback folder to the dotnet folder hive. The folder will be expanded at sdk/NuGetFallbackFolder.
  Fixing CRLF issue.
  Updating xlf and fixing line ending problems with one file.
  Add rhel and Debian download link
  Fix race in telemetry msbuild arg tests
  Avoid repeating the first-run message if lzma archive is missing
  Use fluent helper for line-end normalization
  Update CoreSetup to preview3-25419-01
  Updating Roslyn to 2.3.0-beta3-61816-04
  Update CoreSetup to preview3-25418-01
  insert new tpv2 which fixes following issue microsoft/vstest#632 microsoft/vstest#844 microsoft/vstest#847 microsoft/vstest#840 microsoft/vstest#843
  Windows installer refresh
  Update SDK to 1.1.0-alpha-20170615-3
  Updating NuGet to 4.3.0-preview3-4168
  MSBuild 15.3.388
  Make dotnet-sln-add.Tests pass on localized setup
  ...
@Faizan2304 Faizan2304 mentioned this issue Aug 14, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Faizan2304 Faizan2304

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@codito @spati2 @Faizan2304