I was wondering if anyone had any links or examples of using devforce with asp.net mvc 3 (Razor)?

I have so far used devforce in 2 apps (with great success) and want to use it in a couple of new projects.

 

I don't know if all of this is relevant to just devforce. Sorry if some of the info is not relevant.

 

Out of the items you have listed, here are my responses:

If you have any other questions I will see if I can help

 

I am also creating for a customer of mine, an information management system that will also need the facility to add new/update modules easily, as it will be setup as an initial version used by my customer and the ones they sell to other companies ideally need to be the same basic codebase, with new customer specific features solely by new modules, or extended versions of existing modules.

Any bug fixes and patches are then simpler to rollout (hopefully).

 

Later I want to support phone browsers and understand that it is simpler to have it running as a separate set of layouts due to the amount of realestate available on screen.

 

I have done apps in asp.net, silverlight and windows forms, but this is my first foray into ASP.NET MVC as ASP.NET does not seem to give me what I want.

 

I also use Telerik controls as well and have an active subscription, but prefer the DevExpress reporting tools.

Also, DevExpress controls seem to be happier with the touch screens, especially the asp.net/asp.net mvc controls.

 

I would have normally looked to Silverlight, but need these two sites to work on non-windows platforms as well, such as ipads and android tablets.

 

 

 

Cheers

Ade

 

 

 

But the biggest thing I can tell you is not to over architect. One of my largest MVC apps has about 300 controllers with about 500-600 views. Many of the controllers inherit from a single abstract base controller that provides things like Index, Search, Grid, Dashboard actions. Many of these actions are handled by the base controller. I also have a few generics defined on the base class for things like EntityType, GridType. Based on the entitytype and grid type I can make the appropriate EF calls to return the data. This made it very simple to basically just have to define the views and extend the controllers that I needed. But when you look at the code it is not a grand "architecture" but very simple. 

When moving to design the UI for mobile site and leverage your current view, I suggest a combination of responsive views via CSS and custom mobile views. The big question in the design world is responsive UI vs custom mobile UI, with MVC you can structure it well enough that you can do both. Essentially build your partial views as responsive while building a shell that is either for mobile or computer. In most projects I have found it easier to just do a complete responsive UI where it can adapt to the screen size. Just google "responsive css" and you will see there are several css frameworks that can assist with this.

When it comes to 3rd party controls, I would also suggest looking at telerik's kendoUI specially if you are going to want it to work on mobile. Kendo is still fairly new and has some kinks to work out but in a lot of cases it can get the job done and is much lighter. Also some of the jquery mobile stuff is good but with any control suite you will find quirks on every platform so there is no real perfect solution. Many are getting there but you always will find that case where one device will drive you nuts.

I have done a ton of Silverlight consulting over the past few years and most of my clients have moved to mvc or other technologies that have a HTML5 front end. Many people may say MS killed Silverlight but the reality is the iPad and such killed Silverlight.