The Optimizely Nuget Feed Explorer allows users to explore packages on the Optimizely Nuget Feed and filter out packages that are Optimizely or Community contributed along with other options such as filtering on updated date. However with the release of Optimizely CMS 12 / Commerce 14 it's not simple to find packages that are compatible due the dependency on NET 5.
This now has the capability to filter on packages that are NET 5 / CMS 12 compatible:
Optimizely posts all updates for it's products to the Optimizely Nuget feed. This feed is an invaluable resource if you are an Optimizely developer and is the same feed where community submitted packages can be found too. Heck I even created a Optimizely Nuget Feed Explorer to explore what's on the feed. Optimizely encourages community contributions and appreciates all the effort that goes into the packages. However it's worth nothing that when uploading a package it is moderated before being released onto the feed to ensure the quality of the package. So there are things to bear in mind when creating a package I have summarised below.
For a while I've wanted to explore the Episerver Nuget Feed in a little more detail than was available on the standard http://nuget.episerver.com page. For example I would like to filter by community submitted versus Episerver packages and also know when packages have been updated and/or submitted, in particular recently updated or added packages. So I decided to put a an Episerver Nuget Feed Explorer tool together that allows users to look at the data available on the Episerver Nuget feed, filter it and facet it:
In my previous posted some default web.config files for running under ASP.net 4.0.In the comments @frederikvig talked about the potential of a NuGet package to make the changes.