How SharpDevelop uses MyGet and NuGet

This is a guest post by Matt Ward, working on SharpDevelop, an open source Integrated Development Environment (IDE) for .NET applications which supports the development of applications written in C#, Visual Basic.NET, F# and IronPython. It is and written in C#. In this post, Matt shares their story on using MyGet to host and discover add-ins for SharpDevelop. If you would like to share your story too, let us know! We love to hear good...

Automatically mirror packages from other feeds (or: keep working during NuGet outages)

Many of our users have created their own NuGet feed on MyGet and are uploading their own packages to that hosted feed. Some of our users have been asking for a good way to make their MyGet feed the only feed in their team, the reason for introducing MyGet package source proxy which can include packages from upstream package sources such as the official NuGet Gallery in search results. Up until recently, package source proxies...

MyGet is running over HTTPS only

A couple of weeks ago we've informed you that from July 1st, 2013, MyGet would be switching to HTTPS traffic only. We have just deployed these changes and from now on, your feed URL should be prefixed with https:// instead of http://. Haven't made the switch yet? No problem: we will be redirecting most traffic to the new HTTPS endpoint. However this may add a little latency to your requests. Hence it's best to switch...

Build services: patching AssemblyVersion attribute

It already was possible to work with true incremental build numbers for packages produced using Build Services through the build source settings. A build counter starts with zero and increments with 1 on every build. You can also specify a version format (use '{0}' as a placeholder for the build counter) which will be generated during build. Build Services recently got an update where the AssemblyVersion attribute can be patched with this version number. This...

Switching to full HTTPS on July 1st, 2013

Important: a change is coming to URLs of MyGet. Please read through this post carefully as there may be some actions required on your side. Protecting the security and privacy of our users is one of our most important tasks at MyGet. The fact that you can safely store your intellectual property on our servers is the best proof of that. Currently, MyGet supports both http as well as https to communicate with our applications....

A Glimpse into our toolbox

Every now and then, we like to give you some insight in our development and the tools we use. This time, let’s have a look at Glimpse. Glimpse gathers and presents detailed diagnostic information about the behavior and execution of your web application. It’s like Firebug, but for the server. Glimpse can be installed by installing the Glimpse.Mvc4 package. Different packages exist for different frameworks. Once installed, we can navigate to the /glimpse.axd file to...

Build services: you decide if symbols are pushed or not

By default, when MyGet Build Services creates a build and produces packages, symbols packages (if any) are pushed to SymbolSource.org. In some scenarios, it may make sense to not push symbols packages, for example when creating early versions of a package or during prerelease phases. Since our latest release, it’s now possible to change this default behavior. When creating or editing a build source, the Push symbols to symbol server option specifies if symbols should...

Automatically trigger a MyGet build using an HTTP POST hook

In addition to manually triggering a build within MyGet, it’s also possible to automatically trigger a build every time code is committed to your source control repository, by making use of HTTP POST hooks. Once you have fully configured a build source for your MyGet feed, you will be able to manually trigger a build whenever you like. However, if you are trying to adopt the Continuous Integration Software Development Practice, then automatically triggering a...