Feeds:
Posts
Comments

Posts Tagged ‘framework’

Ext JS is a RIA framework that was highly recommended by my colleagues, and I must admit I was highly impressed by the brief demo they gave. My next question of course is how well it integrates with the .NET web technologies and Visual Studio, answering that will make a big difference in how useful it could be for my immediate projects.

Ext JS: Cross-Browser Rich Internet Application Framework

via Ext JS – Client-side JavaScript Framework.

The next question is what other options are available in this field?

Read Full Post »

Framework for seamlessly offloading processing/memory/storage/etc to the cloud for hardware-limited devices? (Phones) Oh, I like! Looks like they’re trying to cram a smartphone experience onto a featurephone, but what about cramming a much richer experience onto a smartphone?

Who said Microsoft’s mobile strategy has to be limited to Windows Mobile? Redmond has just announced OneApp, a comprehensive framework for delivering apps on a variety of featurephones — largely in emerging markets — where processor horsepower and memory are both at a premium.

via Microsoft delivers OneApp app framework for featurephones.

Read Full Post »

Spring.NET looks to be a great way to implement some best practices such as DI and AOP while letting someone else (Spring.NET) take care of the grunt work. Unfortunately, I can’t seem to find very good sample code, and I’ve read comments about it being “overly complicated”. Then again, that makes it sound just like my sort of thing!

Led and sustained by SpringSource, Spring.NET is an open source application framework that makes building enterprise .NET applications easier. Providing components based on proven design patterns that can be integrated into all tiers of your application architecture, Spring helps increase development productivity and improve application quality and performance.

Please read the overview for additional information.

via Spring.NET – Application Framework.

Read Full Post »

Interesting if somewhat scathing discussion of using the Entity Framework for n-tier applications from the developers/designers of the next version of the Entity Framework. The feedback has inspired me to look at nHibernate again, and makes me wonder if the Entity Framework is really as safe a bet as one would assume Microsoft’s implementation of a technology would be.

The first version of Entity Framework provides convenient ways to load, manipulate and persist objects and relationships. As with many other O/RMs, Entity Framework has a state manager that tracks every change made. Existing objects are typically loaded first from the database, later modified, and finally the changes are saved back to the store.

Another feature, full graph serialization, makes it very easy for developers to ship around object graphs representing snapshots of the current state of the world, across execution boundaries.

The next version of Entity Framework will also support Persistence Ignorance. Therefore object graphs can now be made of POCO instances, which WCF now also supports.

Nonetheless, there is a task that belongs in any N-Tier application that still requires a great amount of work for developers using EF: decoding messages that represent state changes performed by the client, meant to be processed or persisted by the service.

via Entity Framework Design : N-Tier Improvements for Entity Framework.

Read Full Post »