nuget package now available!

the gist

i've deployed the xos.mvc.framework nuget package which offers base model classes, controllers, and commonly used attribute filters for mvc projects as well as some nifty jquery and css plugins/helpers aimed to speed up asp.net mvc application development. the framework can be found on nuget.org. the source code is also available on github.

 

this was long awaited.

as it goes with development, i found myself doing a lot of xcopy code-sharing where i had a folder full of "development tools" that i would drag and drop to each new project. the problem is, if i added or modified the code for a particular project, then i would have to remember to manually copy and work the changes back into the core project along with the other projects that used the framework. the net result being various versions of the code with no way to truly know which folder had the latest version of the code.

 

so, i've finally gotten around to creating a nuget package containing this common code. while this initial release isn't the complete library (i had to pretty much gut it for mass consumption), i plan to continue expanding on it not only for personal use and convenience but also for anyone else who might benefit from an unobtrusive set of code snippets.

 

organic code...no additives or dependencies.

the goal behind the xos mvc framework is to be an unobtrusive, only use what you want, mvc application toolkit. xos-mvc is not intended to be a configuration heavy, dependency riddled swiss army knife.

 

there may be code overlap that is more comprehensively provided by another framework, in which case i likely chose not to implement it because after years of chasing down broken dependencies, i've become a proponent for organic code. organic code is any code that is pure to its original language such that it is widely compatible within its domain. an example of this being a website written in pure html, css, and javascript.

 

organic code strives to be ide agnostic. organic code strives to be platform agonistic. organic code strives to be configuration free.

 

it isn't always possible.

note that the sentences read "organic code strives to be...". this is because it isn't 100% possible and that's fine. so use jquery or knockout or angular, use the html5shiv or the polyfill, or use twitter bootstrap. these modules are still organic in that by incorporating any one module into your project does not introduce a third-party dependency. jquery is pure javascript. the html5shiv is pure javascript. and lastly, the polyfill is pure javascript. an example of what isn't organic is castle.windsor. i like windsor and boo and rhino and on and on. there are even scenarios where ioc containers, orm tools, and config files are the way to go; especially for larger more complex applications that have been modularized. it's just that sadly, i've seen these frameworks implemented in simple single-domain applications, making them unnecessarily complex and difficult to maintain. applications that are ide dependent because that"|version|" of the ide was compatible with the components used in development. These are applications that may have benefitted from simply adding a package that contains extension methods written in the core language and a base set of classes implementing some common properties.

Comments


Comments are closed