[dba-VS] Part I: Cross-posted from dba-OT: MVVM explained - looking for English language heavy review/revision, and technical review

[Gustav Brock]

Hi Shamil

Thanks for the links.

So you did reinvent the wheel ...? (Just wondering - not that I expect a deep explanation, that would pull time from your project).

/gustav

-----Oprindelig meddelelse-----
Fra: dba-VS [mailto:dba-vs-bounces at databaseadvisors.com] På vegne af Salakhetdinov Shamil
Sendt: 8. september 2015 00:50
Til: Development in Visual Studio <dba-vs at databaseadvisors.com>
Emne: Re: [dba-VS] Part I: Cross-posted from dba-OT: MVVM explained - looking for English language heavy review/revision, and technical review

 Hi Gustav at Al --

If you'll ever try to study MVVM - start here

https://rachel53461.wordpress.com/2011/12/18/navigation-with-mvvm-2/

Try to understand what is done here.
I missed this page a few days ago and I have been planning today to add something like that as an "extension" of my "light app framework" but luckily I have got at the referred in this post web page.

MVVM seems to be a ubiquitous solution for quite a few tough everyday UI development tasks - and everything, I'd outline *everything*, looks so simple and straightforward when MVVM is properly applied as in the sample referred above.

Well, here is some criticism for balance:

Never In Doubt
http://neverindoubtnet.blogspot.ru/2011/05/mvvm-backlash.html
The MVVM Pattern Is Highly Overrated
http://thatextramile.be/blog/2010/07/the-mvvm-pattern-is-highly-overrated/
MVVM criticism
http://blogs.msdn.com/b/davihard/archive/2010/04/26/mvvm-criticism.aspx
A lot of MVVM is junk! 
https://social.msdn.microsoft.com/Forums/vstudio/en-US/3bced3ea-4a97-4456-bfe5-828289bcf971/a-lot-of-mvvm-is-junk?forum=wpf
Rules of MVVM??
http://michaelsync.net/2010/02/03/rules-of-mvvm

And this is probably something, which covers my light MVVM app framework but I currently do not have tome to investigate it:

MVVM Light Toolkit
http://www.mvvmlight.net/
http://mvvmlight.codeplex.com/
Thank you.

-- Shamil

>Monday, September  7, 2015 8:05 PM +03:00 from Salakhetdinov Shamil <mcp2004 at mail.ru>:
>
>Hi Gustav --
>
>Thank you for your comment.
>
>The "light SL/WPF aplication framework" is done. I have tested it a few time using both SL and WPF technologies - with VS2012, Silverlight 5 and WPF the XAML/C# code solutions look very similar: a few differences are solved mainly by generic code. I have happened to borrow and to adapt this generic code from the open sources, I have had to filter through a lot during a few last days...
>
>I'm now starting to apply this "light application framework" to the customer main application code base Im developing here from scratch so there will be no need to "fight" with legacy "spaghetti code"... 
>
>Thank you.
>
>-- Shamil
>
>>Monday, September  7, 2015 8:50 AM UTC from Gustav Brock < gustav at cactus.dk >:
>>
>>Hi Shamil
>>
>>Thanks for the details. I didn't mean to imply that you were reinventing anything, just wondering why it was needed to create a framework. If it is to modularize the project, I get the idea. 
>>
>>It really sounds like an outstanding project. Silverlight is great as is and, of course, the client has the final word.
>>
>>/gustav
>>
>>-----Oprindelig meddelelse-----
>>Fra: dba-VS [mailto:dba-vs-bounces at databaseadvisors.com] På vegne af Salakhetdinov Shamil
>>Sendt: 7. september 2015 10:14
>>Til: Development in Visual Studio <  dba-vs at databaseadvisors.com >
>>Emne: Re: [dba-VS] Part I: Cross-posted from dba-OT: MVVM explained - looking for English language heavy review/revision, and technical review
>>
>> Hi Gustav --
>>
>>Thank you for your comment.
>>
>>"Light" means really light here - a couple of days, with clear goals, all but one are already achieved/solved, last one - I have  found its solution in a sample project and I'm now adapting it to my "light" framework. Most of actual work hasn't been spent on this "light" framework but on other tasks in this project...
>>
>>I'm using ICommand, INotifyPropertyChaged interfaces and nested properties binding in WPF and SilverLight, the latter is actually the target deployment technology requested by the customer - they don't mind it "has been left in the dark by Microsoft". Well, I'm trying to explain the customer this issue but they wanted the first version in SilverLight...
>>
>>This "light" framework - actually is a small set of generic classes + nested application logic classes - they allow to keep WPF/SilverLight XAML forms/pages/controls' code behind 100% clean of any not even business but also UI navigation, updates etc, logic/code. And I'm not "inventing the wheel" (AFAIS from the Net quite a few devs do similar things but I haven't seen any info with all the technical details posted - so I have to make these details "reinvented" here by myself) - the "magic" comes from WPF/SIlverlight native binding features. This "code behind cleanness" + nested "architecture" of custom business logic classes allows to modularize the whole development code base - the goal is to work on such projects in a team not alone...
>>
>>Once again, I'm not inventing anything here, I'd even suppose there could be somewhere already done something like that but it's not easy to filter out so much information to find this solution when working on an urgent project..
>>
>>>>> Even "light", isn't that a major task?
>>I do realize your concerns, Gustav.
>>
>>I hope I will have free time in a couple of weeks to share my findings here.
>>
>>Thank you.
>>
>>-- Shamil