This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
Build dependencies should be configurable not fall back to NuGet when missing. #619
Comments
Eilon
changed the title
|
Related to #438 |
davidfowl
added a commit
that referenced
this issue
Sep 25, 2014
- 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the build system will check nuget feeds for missing dependencies. This is undesirable from a security perspective.
The build system needs a way to be told "This must come from the local 'GAC', a local project or this must come from this nuget feed only"
The text was updated successfully, but these errors were encountered: