This project is read-only.

N2.Extensions Part Definitions not wanted / NuGet Package Updates

Topics: Developer Forum
Jun 12, 2013 at 6:40 PM
I'm building a new Razor 2 MVC site and do not want the parts defined in N2.Extensions on my palette. I do however need the Razor extensions (btw. time to upgrade to Razor 2). Can we please split the project into N2.MVC and N2.PartsLibrary or something like that? This will make it easier to stay in sync with GitHub.

Also there's a number of NuGet Package updates which we should get. Instead of checking-in the various packages I would prefer to enable automated package restore.

Jun 13, 2013 at 2:34 AM
We could do this. I think some number of built-in parts is acceptable though and perhaps we could introduce some web.config options to hide those parts. Which parts specifically do you NOT want, out of curiosity?

Jun 13, 2013 at 4:14 PM
Edited Jun 13, 2013 at 4:16 PM
  • In general I might want to change the Attributes on the part class
  • HTML Raw
    • May be too powerful in some use cases where you want your users to use more structured part types.
  • Slideshow uses N2.Utility.ListFiles(System.Web.Hosting.HostingEnvironment.MapPath(relativeBasePath), filter)
    • Utility is a bad place for this function
    • This implementation does not support virtual FS
  • ContentList - is not needed on my site
Jun 13, 2013 at 10:25 PM