1 / 20

LightSwitch 2011 Simple on the outside – rich on the inside

LightSwitch 2011 Simple on the outside – rich on the inside. c ircles of insight. m icrosoft lightswitch 2011 r ich on the inside, simple on the outside…. p aul v an b ladel – october 2011. w ho a m i ?. IT  technophile  @KBC with strong emphasis on Microsoft .NET

jemima
Download Presentation

LightSwitch 2011 Simple on the outside – rich on the inside

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LightSwitch 2011Simple on the outside – rich on the inside

  2. circles of insight microsoftlightswitch 2011 rich on the inside, simple on the outside… • paulvan bladel– october2011

  3. who am i ? • IT technophile @KBC with strong emphasis on Microsoft .NET • educated as : • musician (royal conservatory brussels) • economist (kuleuven) • no-nonsense IT • works for competence center of  .net development department: internal head-quarter non core-banking apps • paul.vanbladel@gmail.com paul van bladel

  4. overview • part 1: what is lightswitch? a demo is worth a thousand slides... • part 2: key success factors for a LOB framework • part 3: build/deploy something

  5. part 1 • what is lightswitch? • show me the money...

  6. quick intro • history : I’m involved in lightswitch as early adopter from • beta 1: august 2010 • Version 2011: 28 July 2011 • quick demo of a canonical example • architectural overview: • full blown 3 tier: • silverlight client (in and out of browser) • IIS • sql server (or other persistence store) • extension framework brand new microsoft framework/RAD tool for building LOB apps

  7. part 2 • key success factors for a LOB framework • is lightswitch ok?

  8. enterprise apps • what is an enterprise application (a LOB app), a software factory approach? • predictability • better cost/benefit ratio • uncovering/canalizing the hidden cost of 'creativity' • separation of duties: building software / building framework. • assures that certain patterns are followed • assures that a certain security implementation is in place. • takes care of cross-cutting concerns

  9. build your own framework • Good luck ... • Entity Framework  - Ria Services - MVVM - MVC3 - Dependency Injection - Boiler plate code - Code generation - T4 - Transaction Management - State Management - Authentication - Identity – Authorization – Unity – MEF - PRISM ...

  10. is lightswitch something for you? • when is lightswitchdefinitely nothing for you? • observe the two sides of the spectrum: • access/Excel (mind hidden cost : macros/vb/convention) • full blown DDD/CQRS (see martin fowler: http://martinfowler.com/articles/lmax.html • how much room is left ? • probably a lot • generates more business.

  11. how does it fit in ALM? • scrum • customers get already a working software in a very early analysis phase • the customer can test, enter data, play… very early. • V1 has some alm limitations: • no test driven development possible • using TFS is possible, but working with more than 3 people on same software is cumbersome. (one big model file)

  12. adopt it • taking into account only the view of software architects does not necessarily leads to a good cost/benefit ratio. • some architects tend to choose for over-engineered frameworks. (bazooka mosquito) • I like: • value chain approach: mind the value-adding to the customers of your customers (Michael Porter) • eco-system thinking (stakeholders-approach) • recognizes strong dynamic relations between stakeholders how do you like to think about a strategy for adopting a LOB framework?

  13. a framework should... • make things as simple as possible but no simpler • …albert einstein • similarities between scientific model and software (both model of reality)

  14. time dilatation • E the twin paradox Castor: stays home  100 year older Pollux: travels at 0,999 c  4,5 year older

  15. faster than c • particles with imaginary mass m tachyons travel faster than c

  16. albert is great • E • {make things as simple as possible...} • F {... but no simpler} •  Newtonian Paradigm

  17. a framework should... • be simple and transparent on the outside and rich on the inside • simple things should be possible in a simple way, more complicated requirements must be possible • but... making possible complex requirements should never hinder simple things in a simple manner • convention over configuration • it should exhibit "evolutionary disclosure"

  18. a framework should... • be friendly

  19. part 3 • build something.... now !

  20. features • 3 key words: Data - Querying - Screens ("naked object" approach) • Web deploy • explore some extensions • query filter extension • excel importer extension • bing map control extension (show how it is hooked up) • http://demo.componentone.com/LightSwitch/OLAP/ • LightSwitch future: • the future is bright • The under-the-hood design could allow other application types as well: Metro style - Htlm5

More Related