Age | Commit message (Collapse) | Author |
|
|
|
|
|
Added unit tests for new public API that the
MonoDevelopMSBuildNuGetProjectSystem now provides.
|
|
Migrate unit tests that were testing the old NuGet v2
MonoDevelopProjectSystem so they are now testing the new NuGet v3
MonoDevelopMSBuildNuGetProjectSystem class.
|
|
Reduce public API down to PackageManagementServices.ProjectOperations
which is used to find packages installed for a project, install
packages into a project and fire events when a package is added
or removed.
Added InternalsVisibleTo attribute for addins that currently still
use the non-public API.
|
|
Fixed bug #19054 - NuGet package MSBuild property files (.props)
should be added to the start of the project file
Installing a NuGet package that included an MSBuild .props file would
add an Import element for the .props at the end of the project file
(.csproj) which is incorrect. Now .props files are added to the
project file as the first child element inside the Project's root
element.
|
|
Switch to using an Action instead.
|
|
Change the namespace from ICSharpCode.PackageManagement to
MonoDevelop.PackageManagement
|
|
|
|
|
|
Previously when updating a NuGet package the references would be
added with Local Copy set to true and the previous value would be
lost. MonoDevelop will generally have Local Copy set to false for
assemblies that are shared across MonoDevelop and since more NuGet
packages are being used in MonoDevelop this makes maintaining the
Local Copy value a lot more work.
Now if a reference is removed and then added during a NuGet update
the Local Copy value will be kept.
Note that currently this only works when updating the NuGet package
from the Solution window. If you add a NuGet package from the Add
Packages dialog then Local Copy is not preserved. This is a problem
for pre-release NuGet packages since you cannot update to a
new version of a pre-release NuGet package from the solution window.
|
|
Port remaining unit tests from SharpDevelop.
|