Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/monodevelop.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-06-08[PackageManagement.Tests] Fix warningsMikayla Hutchinson
2017-07-05[NuGet] Update to NuGet 4.3.0.4199Matt Ward
2016-05-09[NuGet] Add more unit tests for MSBuild NuGet project system.Matt Ward
Added unit tests for new public API that the MonoDevelopMSBuildNuGetProjectSystem now provides.
2016-05-09[NuGet] Migrate project system tests.Matt Ward
Migrate unit tests that were testing the old NuGet v2 MonoDevelopProjectSystem so they are now testing the new NuGet v3 MonoDevelopMSBuildNuGetProjectSystem class.
2016-03-30[NuGet] Minimize public API.Matt Ward
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.
2016-03-21[NuGet] Insert MSBuild property files ( .props) at start of project.Matt Ward
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.
2016-01-05[NuGet] No longer using DispatchService MessageHandler.Matt Ward
Switch to using an Action instead.
2015-12-12[NuGet] Change NuGet addin namespace.Matt Ward
Change the namespace from ICSharpCode.PackageManagement to MonoDevelop.PackageManagement
2015-12-12[NuGet] Rename classes named after SharpDevelop.Matt Ward
2015-10-12Bug 33395 - [Roslyn] NuGet package license warning not shown in status barDavid KarlasĖŒ
2015-03-31[NuGet] Keep Local Copy setting when updating a NuGet package.Matt Ward
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.
2014-05-12[NuGet] Add more unit tests.Matt Ward
Port remaining unit tests from SharpDevelop.