.NET Architectonics - All Comments

re: A lovely couple (of architecture books)

Dave — Sun, 01 Nov 2009 23:01:34 GMT

Thanks so much for all the work you put into Architecting Applications for the Enterprise. It is a book i refer to often, and always keep by my side. I highly recommend this book to junior and seasoned developers. Thanks again and I look forward to your other books!

effects 20th

effects 20th — Sat, 31 Oct 2009 22:54:10 GMT

hypothesis vectors human 1960 during windows external shop

re: Web Forms vs. ASP.NET MVC

Austin — Thu, 22 Oct 2009 20:05:11 GMT

Renso, in ASP.NET (regardless of whether you're using web forms or MVC), the embedded code does get compiled, just like the code in the code behind file does. Any change you make to the aspx code will cause a recompile of the application.

So no loss of performance there.

re: Web Forms vs. ASP.NET MVC

Renso — Tue, 20 Oct 2009 12:08:47 GMT

We are using ASP.Net Mvc for a large scale in house CRM (customer Relationship Management) web-based app. We have about 300 actions scattered across many controllers and testing is very well supported. Since MS is a bit slow with giving us smart controls for Mvc (like GridView, etc) we decided to use the jQuery JavaScript library and supported plug-ins to help with that, for example the jqGrid plug-in that we use for all our lists and their CRUD operations. I personally don't like the fact that the HTML page now contains code again as in the old classic ASP days, but at least you get intellisense with it. I also don't like the fact the the embedded code in the HTML clutters the page, and is not compiled but interpreted at run-time.

I agree you can write well organized code to support SoC but testing is problematic for the UI.

In Mvc styling via external CSS files is great, no more issues with the custom prefixes for HTML tag ids as in ASP.NET.

It is worth mentioning that the examples on the MS site for Mvc are very simple and do not address the design pattern challenges we face for large scale apps. You will need to figure that our for yourself. For example how to handle errors across actions, plugging into another test framework, etc. It is not as simple as you may think and can get complicated. So maybe you don't have to deal with ViewState and the event hierarchy of ASP.NET like On_Load, etc, but now you are going to have to deal with mapping the HTTP request object to your entities, deal with TempData and ViewData as well as the boilerplate code embedded in your HTML pages to suport more complex controls like ListView.

I can honestly say the Mvc is a great approach, although not necessarily the silver bullet, you need to way your requirements.

re: Silverlight Coding Contest

wahyu — Mon, 05 Oct 2009 19:36:49 GMT

i just saw the contestants gallery of that competition, my conclusion: developer should let designer design the application. I know this is a coding competition, but it is hard to find nice looking silverlight or wpf applications.

re: The dead-end of Web Forms

Ryan Roberts — Mon, 05 Oct 2009 13:50:58 GMT

>Our App is built out of many User Controls that are resused all across the page

This can be supported per-project using partial views, and you can transfer them between projects using good old fashioned file copy, or by compiling and loading them from resources.

>Once MVC has the quantity and quality of the current commercial server controls, more people will adapt it

It is very unlikely that MVC will ever support a third party market in server side controls. The component model is just not there and attempting to implement one would end up reinventing webforms. Client side components are a more viable option for MVC.

RAD/scaffold support for data driven models is very possible with the MVC pattern however, as things like the Django admin system generator demonstrate. Out of the box ASP .NET MVC has a silent 'M' which unfortunately means that you don't get the instant productivity of the various opinionated OSS MVC frameworks.

re: The dead-end of Web Forms

Estevez — Mon, 05 Oct 2009 07:19:29 GMT

Darth helge: you must be right. My wishes were just teoretic.

As I use MVC.Net I like it's structure better than WebForms. I just had to write a form with thousend lines where javascript, server scripts and HTML were mixed. Maybe just I should structure my code better way.

(And ... while it is illegal or Out Of Pattern, we can still use codebehind, or use just pure classes for background operations)

re: The dead-end of Web Forms

Alex James — Fri, 02 Oct 2009 16:22:24 GMT

Dino,

Completely agree. As always 'it depends' is the answer. I rail against people who see things in black and white. As we become wiser we see more depth and color in every decision...

Alex

Interesting Finds: October 2, 2009

Jason Haley — Fri, 02 Oct 2009 12:04:50 GMT

Interesting Finds: October 2, 2009

re: The dead-end of Web Forms

Darth_helge — Fri, 02 Oct 2009 09:55:03 GMT

Estevez: It seems to me that you are in fact satisfied developing with webforms. Simulating state is one of the best arguments using webforms. My guess is that you are curious about this MVC platform and want to try it out, but you can't force MVC to become like webforms.