Fix for #670, inter project dependencies without matching package id - #671
Merged
Conversation
ascjones
changed the title
forki
added a commit
that referenced
this pull request
Mar 3, 2015
Fix for #670, inter project dependencies without matching package id
Member
|
thank you! |
Contributor
|
Thanks. Does it do what you want now? |
Contributor
Author
|
Indeed it does, project references with corresponding paket.templates files are included as dependencies |
Contributor
|
Awesome :). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix for #670
Use the project name (without extension) to uniquely identify projects when determining inter project dependencies.
For this I added a new property on the ProjectFile for getting the project name without extension, so I've also used this in a couple of other places from some previous work I did.