Coordinating Enterprise Website Development in .NET

make money on computer

make money on computer — Thu, 26 Jun 2008 03:07:05 GMT

The biggest drawbacks are: The noticeable“ Big Head” of The Rich Jerk The segment relating to online ventures (small one indeed) a bit off subject Outcome for The Rich Jerk“ Making Money on the Bad Credit Credit Cards is Easy” If you’ re a greenhorn to

Coordinating Enterprise Website Development in .NET

Coordinating Enterprise Website Development in .NET — Mon, 26 Nov 2007 22:53:48 GMT

Pingback from Coordinating Enterprise Website Development in .NET

re: Coordinating Enterprise Website Development in .NET

Manny A. — Tue, 21 Aug 2007 11:09:15 GMT

I agree with you completely, JS. The model you've proposed above is exactly what I believe is needed when developing for Enterprise websites. I also think the Provider model, introduced in Asp.net 2.0 also goes a long way in enabling this - one can see where each of these black box "embedded applications" (that's the name i've been calling them since I started developing in precisely that way) simply consume their services via providers for that specific service from the site. <p>The main website simply becomes a loose "glue" for the several embedded applications</p>