Improve the diagnostics for model binding to include PropertyEditor / ConversionFamily / ModelBinder selection This is here because I think it's necessary to lock down the model binding API
Improved Diagnostics Package
Release HtmlTags 1.0
Nuget-ify and release FubuSpark
Dovetail team to convert “blue” codebase to FubuValidation
Move Dovetail “crud” infrastructure to FubuFastPack
Clean up BehaviorGraph / ObjectDef based on feedback from the FubuFastPack work
Model binding work over. Remove all service location. Enable runtime selection of binders. Eliminate the Lambda model inside value converters. Driven by feedback from writing custom binders and converters in FubuFastPack
Move script manager url from scripts/images to _content/scripts
XSS and anti-forgery token
Moved HtmlTags to a separate repository
Simple Content negotiation support in ObjectResolver. Choose serialization or model binding dependent upon mimetype of request, default to model binding. Not trying to play a fullblown "FubuRest" card ** Jeremy **
Pull Packaging into the new "Bottles" project and repository
Remove Webforms support to a new project
Type scanning for service registrations. Basically putting StructureMap's AssemblyScanner over FubuRegistry for IoC neutral way of registering services
Deal with any ignored tests. Eliminate them if they don't add any value
Sample application(s). FubuMusicStore? FubuNerdDinner just doesn’t work very well
FubuMVC.Validation package. Reusable validation integration “recipes.” Html conventions, BehaviorGraph conventions, pipeline integration. Should be possible to swap other validation engines in later
IoC integration guidelines and acceptance tests
Fubu "Continuous Delivery" recipes based on "Bottles" (the packaging) Team Dovetail (in progress, but not trying to do this for 1.0)
StoryTeller test coverage for all major features. StoryTeller CI build. Possibly switch to WebDriver / Selenium 2 to get browser matrix. Maybe start FubuMVC.StoryTeller for reusable test infrastructure. Not going to happen until StoryTeller is easier to work with -- Jeremy
Flesh out default conventions for routes, html conventions, action selection. FubuRegistry on a new project should be as empty as possible
Script Manager improvements
“PageScript” -- automatically push PageScript("name.js") to the bottom of the dep. graph
Localization script. I.e., use scriptname.en-us.js or scriptname.en-gb.js
option to validate the script graph (make sure files it refers to exist)
Revisit the "FubuContinuation / Redirectable" model. Maybe an "InterceptedActionCall"?
Review of all the Http abstractions
Add StoryTeller tests to the CI build.
Rename the InvokePartial API to eliminate confusion with Partial(). InvokePartial code sucks, but it serves its purpose.
Run FubuMVC via Mono XSP from a console app or embedded DLL. “Fubu in a box” ** Alex **
Redo the Url/Route conventions (???)
Integrate fubu “Bottles” support with either Nuget or OpenWrap
Razor view engine integration
CSS/Script compression recipes
Cdn.google.com (and analogues) integration
Html conventions everywhere
OWIN or OpenHttp support.
Eliminate all coupling to ASP.Net / IIS. Make IIS run in an adapter model to OWIN / OpenHttp.