| Age | Commit message (Collapse) | Author |
|---|
|
For .NET Core 3.0 and .NET Standard 2.1 projects a Frameworks folder
is now displayed under the Dependencies folder. This shows the
FrameworkReferences used by those projects. The SDK folder is hidden
for these projects since they do not have SDKs.
|
|
Remove local variable in node builder after code review. The local
variable is not needed in the method.
|
|
Previously multi-target framework projects would show the framework
nodes under Dependencies - NuGet and Dependencies - SDK. Now the
framework nows appear directly under the Dependencies folder. Note
that currently the Assemblies and Projects folders do not support
multi-target frameworks and just show all assemblies and projects
referenced directly in the project ignoring any conditions.
|
|
Refactored the dependency node tests so they test the node builders
themselves. Previously the data object classes were being tested.
This is in preparation for new tests for multi-target projects.
|
|
Fixes VSTS #798085 - Double clicking Dependencies folder in Sdk
projects does not open nuget dialog
|
|
The NuGet folder in the Dependencies folder is now removed if the
project has no NuGet package references.
|
|
The Dependencies folder now has a SDK folder displayed in the
Solution window. This shows package dependencies that are imported
and not part of the project. The NuGet folder shows package
dependencies that in the project file itself.
|
|
|
