NuGet improvements. #896
Closed
NuGet improvements. #896
Conversation
This file contains 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
* Adds a new project to the solution for building a native NuGet package. * The package ends up in `bin\<configuration>`. * When the package is installed, a build target file is imported into the target project that will cause the binaries to be copied to `$(TargetPath)` after build (if necessary). * Versioned as the last version of the LibGit2 that was pulled into this repository. * Do not be fooled, this is not actually a .csproj. In order to get Visual Studio to load it so that it shows up in Solution Explorer you have to tag it as one of a known list of project file types (http://msdn.microsoft.com/en-us/library/vstudio/ms171468(v=vs.110).aspx). If you try to view the properties on it, Visual Studio will add a bunch of stuff to the underlying project file. I don't *think* anything will break, but if it adds back the imports I believe it will break. Be aware, best to just not open the properties on the project and instead open it in a text editor. * Changes NuGet package to be generated on successful build of the class library. * The package ends up in `bin\<configuration>`. * Depends on the Native NuGet package (see above). * Only installs the one library and the one dependency, nothing fancy. * Adds dependency on `NuGet for MSBuild`. * Both projects have a `.targets` file added to them that utilizes `NuGet for MSBuild`. * Take care in updating `NuGet for MSBuild`, it will add some post-build tasks to your project when you install/update it. I have removed these but they will come back if you update. They may have undesired side effects. * I have committed the dependency to the repo, I would encourage you (project owners) to `.gitignore` `packages/` though since Visual Studio will restore them on first build automatically (since VS2012 Update ? I believe).
Closed
|
Re-create of PR #778. |
…lds and updates mono version. I couldn't figure out how to get Travis CI to do a package restore on Linux.
|
Currently failing due to a bug in xbuild. It looks exactly like the previous one I reported https://bugzilla.xamarin.com/show_bug.cgi?id=22981 but that is supposedly fixed in Mono 3.10. I have not spent much time investigating further. |
|
By the looks of it, mono/mono@7439e99 doesn't seem to be in 3.10. |
|
See this for reference. |
|
You are correct, my mistake. I'll go back to waiting then. |
|
The fix is in 3.12 mono, so if this can wait until then, it's all perfect. |
|
Superseded by #984 |
|
Cheers! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
bin\<configuration>.$(TargetPath)after build (if necessary).bin\<configuration>.NuGet for MSBuild..targetsfile added to them that utilizesNuGet for MSBuild.NuGet for MSBuild, it will add some post-build tasks to your project when you install/update it. I have removed these but they will come back if you update. They may have undesired side effects..gitignorepackages/though since Visual Studio will restore them on first build automatically (since VS2012 Update ? I believe).