Development, FeatureXavier Decoster
MyGet 2.1 was released on February 12, 2016. Highlights This 2.1 release of MyGet again adds some new functionality to the service. Major highlights of this release are: our new MyGet Symbols Services offering,our new support for building and hosting Visual Studio Extensions,and the implementation of NuGet v3 support. This means, from now on, you can now also use MyGet to host your symbols, publicly or secured. Features MyGet (all plans) The following applies to all MyGet plans: MyGet Symbols...
Feature, NuGetMaarten Balliauw
Every once in a while, our support gets a question that is similar to the following: When requesting the package details for some versions of the NuGet packages in our feed it seems like the service encounters an error preparing the ATOM document, also resulting in NuGet failing to download the package. Here's an example URL: https://www.myget.org/F/chucknorris/api/v2/Packages(Id='MyPackage',Version='1.2.20160209.1-master') Is something wrong with MyGet? Definitely not! Let’s look at the packages for this feed: MyPackage 1.2.20160209.1-master MyPackage...
Bower, Feature, Npm, NuGet, VsixMaarten Balliauw
Wouldn’t it be awesome if creating a NuGet, npm, Bower or VSIX feed was as easy as just copying packages into a Dropbox folder? Awesomeness is here: we’ve added Dropbox as a package source type to MyGet. This allows us to link a Dropbox folder to a MyGet feed and automatically upload packages so they can be consumed with the popular package managers out there. The Dropbox package source makes it easy to move packages...
FeatureXavier Decoster
Many people are using multiple MyGet feeds in their development flow, and have good reasons to do so. Some are pushing packages from one feed to another as they promote them through quality gates. Others are proxying upstream feeds or filtering packages downstream. MyGet supports many types of package sources, and as flexibility is great, configuration can be a little tedious or even error prone. Why would we ask our users to provide us with...
Feature, NuGetXavier Decoster
At MyGet, we live and breath a culture of componentization, and we are very happy to see package authors adopting and sharing these practices within their organizations. One of these practices is the usage of NuGet's localized NuGet packages feature. The adoption of localized satellite packages is a good indicator of package author maturity. Using a better practice should be rewarding and free of friction. One of our Dear Users provided us with great feedback on how he...
Development, Feature, NuGetMaarten Balliauw
Shortly after we launched MyGet, we teamed up with SymbolSource.org to provide support for .NET debugger symbols. Today, we’re happy to announce a second option: integrated MyGet symbols support! MyGet symbols support lets consumers of our NuGet packages step through the source code and integrate with Visual Studio and tools like WinDbg. Additionally, symbols and sources can be consumed from within MyGet as well. Head over to our docs and learn how to get started...
Bower, Development, Feature, Npm, NuGet, VsixMaarten Balliauw
We’re happy to introduce a few user interface enhancements which have been available for all users of npm private feeds on MyGet. We’ve now rolled these out to the package details page for NuGet, npm, Bower and Vsix packages. These pages now display all “at-a-glance” information on the right. Package owners, authors, license information and downloads can be seen from here. The wider part of the package details page now displays the README.md contents retrieved...
Feature, NpmMaarten Balliauw
Using Azure Web Apps, we can deploy and host Node applications quite easily. But what to do with packages the site depends on? Do we have to upload them manually to Azure Web Apps? Include them in our Git repository? None of that: we just have to make sure our app’s package,json is checked in so that Azure Web Apps can install them during deployment. Let’s see how. Installing node modules during deployment In this...