FeatureXavier Decoster
Ever wondered where the “Report Abuse” link in Visual Studio navigated to? Or where it comes from? This link is available for every package, and on MyGet feeds, it will typically point to a dummy URL. The reason for that is it’s your feed, and you are the one who should respond to any messages that come in through it. But with a dummy URL, that obviously does not work… So we made it configurable!...
Development, FeatureMaarten Balliauw
We are happy to announce that MyGet partnered with Microsoft to be included in the Microsoft Azure Store. This is our second partnership with them, since we also integrate with Visual Studio Online. The Microsoft Azure Cloud is widely used to build and deliver applications to end-users. Developing these applications could greatly benefit from using a package management solution to streamline development, and that’s where MyGet comes in. Having MyGet available in the Microsoft Azure...
Development, FeatureMaarten Balliauw
We’ve supported the “Push upstream” workflow for quite a while now. This workflow allows you to promote packages from one feed to another, ideal when you are pushing prerelease packages on one feed and pushing them as stable packages to another feed after testing them.’ So far, it has been only possible to push individual packages upstream, or all “latest” packages. We realized this was painful for one scenario: if you’re usign Build Services, it...
FeatureMaarten Balliauw
When you create a MyGet feed, chances are you want to keep the packages up to date. This can be done automatically by enabling auto-update on the package sources for your feed, but that is not always desired. Some people prefer updating individual packages manually, which makes perfect sense: only packages you approved will be available on the feed. To help detecting package updates, we’re now showing a notification on the package details page whenever...
FeatureMaarten Balliauw
When managing your dependencies using MyGet, it may be important to have a view on which licenses are used on your feeds and in your software projects. Which licenses are your NuGet packages using? Many teams would love to know which (open source) licenses are being used by their teams, so they can be inspected and managed. It feels good to finally tackle one of those items that have been on our backlog for almost...
Development, FeatureMaarten Balliauw
Any service can experience a brief moment of downtime. This is also true for any upstream package source you configure in MyGet. That’s why we have the package mirroring feature: when uploading or adding a package to your feed, the added package (and its dependencies) are stored into MyGet’s own storage system and they remain available in the event of an upstream service outage.<div><div><div>This package mirroring checkbox used to be disabled by default. Why? Because...
FeatureMaarten Balliauw
We are really excited to announce that as of today, MyGet enables new scenarios for all users of Visual Studio Online! Microsoft just announced Visual Studio Online Extensions at TechEd, so we can finally disclose these new scenarios and toggle the feature-switch for all of you. In short, these are the new scenarios we've just enabled for you: Serve NuGet packages from a Visual Studio Online drop location Add a VSO Git repository as a...
Feature, NuGetMaarten Balliauw
Since NuGet 2.8, the NuGet Package Manager Console’s Install-Package command comes with support for specifying the dependency version resolution process using the –DependencyVersion switch. If you have never used it before, what it does is it allows you to specify how NuGet should resolve package dependencies. It can resolve dependencies to the lowest possible version (default behavior), the highest possible version, or the highest minor or patch version. This feature is useful because it gives...