The first blog post I ever wrote was titled “ Turning an ascx user control into a redistributable custom control ”. It was almost exactly five years ago, and it still gets a lot of hits today. And interestingly, this new blog post is about solving essentially the same problem, but with a much nicer Razor based solution than was available at the time. The general issue we’re trying to solve is to encapsulate reusable pieces of UI. Unfortunately, this has typically meant choosing between two approaches, each having their pros and cons (this mirrors the intro from my old post): Custom code in a library project: this makes it easy to produce a binary that can be used in multiple projects without having to keep source files around...
Wow, it’s hard to believe that it’s been less than a week since NuPack went public. We were hoping to get noticed, but the attention we got was way beyond my wildest expectations! The buzz on Twitter has just been phenomenal, and for the most part the feedback has been very positive. Thank you all for that, this is very encouraging for our little NuPack team :) NuPack as a noun for the packages Before I get into the meat, I’ll just say that I want to start using NuPack as a noun that refers to the packages. So rather than saying “There is a NuPack package for Spark”, I’ll say “There is a NuPack for Spark”. Or to use NuPack teammate Rob Reynold’s catch phrase. “ There a NuPack for that! ”. Hmmm...