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.

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

Dependency node does not handle configuration switches #3642

Closed
davkean opened this issue Jun 12, 2018 · 8 comments · Fixed by #9008
Closed

Dependency node does not handle configuration switches #3642

davkean opened this issue Jun 12, 2018 · 8 comments · Fixed by #9008
Assignees
Labels
Feature-Dependency-Node "Dependencies" node in Solution Explorer that display project, binary & package references Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed. Triage-Approved Reviewed and prioritized
Milestone

Comments

@davkean
Copy link
Member

davkean commented Jun 12, 2018

  1. File -> New -> Console App (.NET Core)
  2. File -> New -> Class Library (.NET Standard)
  3. Switch from Debug -> Release
  4. Add a reference from Console App -> Class Libary

Expected: No warning icons
Actual: Warning icon on reference

@davkean
Copy link
Member Author

davkean commented Jun 12, 2018

Exactly the same issue as #2733 except that this is the dependency node which has the same code, but duplicates it.

@Pilchie Pilchie added Area-New-Project-System Feature-Dependency-Node "Dependencies" node in Solution Explorer that display project, binary & package references labels Jun 12, 2018
@Pilchie Pilchie added this to the 16.0 milestone Jun 12, 2018
@davkean
Copy link
Member Author

davkean commented Jul 31, 2018

@tmeschter
Copy link
Contributor

@davkean Will this bug be fixed "for free" when you fix #2733 or will we need to make further changes?

@davkean
Copy link
Member Author

davkean commented Sep 10, 2018

@tmeschter I'll need to make additional work, it will basically need to copy the pattern I've used for language service. I have this work on the back of my mind.

@davkean davkean assigned davkean and unassigned etbyrd Sep 10, 2018
@jjmew jjmew modified the milestones: 16.0, 16.X Feb 13, 2019
@davkean davkean assigned drewnoakes and unassigned davkean Jan 27, 2020
@davkean
Copy link
Member Author

davkean commented Jan 27, 2020

@drewnoakes This will be covered in the dependency node rewrite- can you move to appropriate milestone or dup against existing bugs.

@davkean davkean added the Triage-Approved Reviewed and prioritized label Jan 27, 2020
@davkean davkean added this to the 16.6 milestone Jan 27, 2020
@drewnoakes drewnoakes modified the milestones: 16.6, 16.7 Mar 21, 2020
@drewnoakes drewnoakes modified the milestones: 16.7, 16.8 May 4, 2020
@drewnoakes
Copy link
Member

@lifengl identified a leaked ProjectCatalogSnapshot after changing configurations due to this bug. When we fix this, we should verify the leak is also addressed.

@drewnoakes
Copy link
Member

Another repro:

<Project Sdk="Microsoft.NET.Sdk">

    <PropertyGroup>
        <TargetFramework>netcoreapp3.1</TargetFramework>
    </PropertyGroup>

    <ItemGroup Condition="'$(Configuration)' == 'Debug'">
        <PackageReference Include="Newtonsoft.Json" Version="9.0.1" />
    </ItemGroup>

    <ItemGroup Condition="'$(Configuration)' == 'Release'">
        <PackageReference Include="Newtonsoft.Json" Version="12.0.3" />
    </ItemGroup>

</Project>

Switch between release and debug configurations and the tree will not update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature-Dependency-Node "Dependencies" node in Solution Explorer that display project, binary & package references Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed. Triage-Approved Reviewed and prioritized
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants