Removing hard-coded references to c:\work in build events #2
Conversation
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
… to fix Excel-DNA nuget install script?)
govert
added a commit
that referenced
this pull request
Mar 31, 2014
Removing hard-coded references to c:\work in build events
Member
|
Those paths are set up when the NuGet package is installed, but I'm not yet sure how to identify the NuGet package path in terms of the $(...) project variables correctly when installing - the package could be under the solution or under the project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Hi Govert
Thanks for pulling the array function registration code. I see you got around the problem I was having reflecting the lambda function directly - not sure why i missed that, but thanks.
This is just a small commit to allow the project to compile cleanly in my environment - there were some hard-coded paths to your working directories which caused post-build failures. I guess that this also needs to be fixed in the Excel-DNA nuget installer script, but I haven't taken a look at that...