-- onlinedev
> if you keep your actual business logic and data access functions seperate
> from the view then you have actually achieved the MVC architecture.
Not quite. The Web Client Software Factory (WCSF) attempts to lighten the burden that classic web-form programming imposes on the view, but it is still MVP, albeit with a twist.
You can read more about WCSF on this page:
http://www.codeplex.com/websf
If you're tempted to explore WCSF, two pieces of advice:
1. It doesn't work in VS2k8.
2. Make sure your VS2k5 has both C# and VB installed before you install WCSF. Otherwise you will have to take post-installation corrective steps that aren't well-documented.
-- onlinedev
> tell me whether we can use the server controls (GridView, Formview,
> Objectdatasource etc.) or any other third party controls
I don't know your third-party controls. In all likelihood, you won't be able to use many AspNet built-in controls. They inject funky JavaScript, emit funky identifiers, perform funky postbacks and utilize funky <form runat="server">.
None
0 Points
11 Posts
Re: MVC Architecture - Sample
Dec 19, 2007 02:47 PM|foobar123|LINK
-- onlinedev
> if you keep your actual business logic and data access functions seperate
> from the view then you have actually achieved the MVC architecture.
Not quite. The Web Client Software Factory (WCSF) attempts to lighten the burden that classic web-form programming imposes on the view, but it is still MVP, albeit with a twist.
You can read more about WCSF on this page:
http://www.codeplex.com/websf
If you're tempted to explore WCSF, two pieces of advice:
1. It doesn't work in VS2k8.
2. Make sure your VS2k5 has both C# and VB installed before you install WCSF. Otherwise you will have to take post-installation corrective steps that aren't well-documented.
-- onlinedev
> tell me whether we can use the server controls (GridView, Formview,
> Objectdatasource etc.) or any other third party controls
I don't know your third-party controls. In all likelihood, you won't be able to use many AspNet built-in controls. They inject funky JavaScript, emit funky identifiers, perform funky postbacks and utilize funky <form runat="server">.