Skip to content
This repository was archived by the owner on Dec 18, 2017. It is now read-only.

Added frameworkAssemblies support #660

Merged
merged 1 commit into from
Sep 25, 2014
Merged

Added frameworkAssemblies support #660

merged 1 commit into from
Sep 25, 2014

Conversation

davidfowl
Copy link
Member

/cc @blowdart @GrabYourPitchforks

- The frameworkAssemblies section is specific to a target framework
- Refactored BuildContext to call into the ProjectReferenceDependencyProvider.
This means that only a single place actually uses the project class directly
(which is nice).
- GetLibraryDescription now takes a Library instead of name and version
(we may need to revisit this and create a different poco). When @lodejard finishes
dependency types we'll see how this ends up
- Preserve the backwards compatibility of declaring frameworkAssemblies in
dependencies temporarily
- Added tests for parsing frameworkAssemblies

#640
#619
@davidfowl davidfowl merged commit 6d499dc into dev Sep 25, 2014
@Praburaj
Copy link
Contributor

is this also applicable in the top level dependencies node?

@davidfowl
Copy link
Member Author

I chose not to make it top level since then future of these are a transitional thing. Nuget packages are the future

@davidfowl davidfowl deleted the frameworkAssemblies branch January 19, 2015 07:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants