Is there any support in MVVMLight for input validation?
Thanks,
Juan Carlos Galvez
So if you are asking if the MVVM light framework itself has any custom built functions for validation outside of WPF/silverlight, the answer is no.
Related
I am developing web form equivalents of paper based forms.
On the paper form people get the option to sign the form with their signature.
In ASP.NET what are the options for a digital equivalent.
I can suggest some pages, if we talking for the same think.
http://msdn.microsoft.com/en-us/magazine/cc163434.aspx
http://msdn.microsoft.com/en-us/library/aa480189.aspx
http://www.microsoft.com/uk/msdn/nuggets/nugget/224/Using-CardSpace-with-ASPNET.aspx
It may be too late, but for the sake of others who are looking for the same thing as me - try JSignature JavaScript plugin. Here is the ReadMe from github. Hope it helps.
I had gone through many documents, no where mentioned how cairngorm framework works internally, means, how cairngorm Event, frontController, BusinessDelegate,ServiceLocator,Commands works and why we are extending or implementing cairngorm class like ICommand, IResponder and cairngormEvent.
Thanks,
Ravi
For the love of GOD, don't use Cairngorm (2) as a framework. Use either RobotLegs or Parsley. Both of which has awesome documentation and a very active community.
Is there a guide somewhere showing an example of using ViewModels in a WP7 application?
You could check out Laurent Bugnion's EX14 - Understanding the MVVM Pattern - from Mix 10.
Laurent is the author of the popular MVVM Light Toolkit with support for WP7
Here's another couple of posts that may be of interest.
C#er : IMage: Model-View-ViewModel (MVVM) Explained
.NET by Example: Using MVVM Light to drive a Windows Phone 7 / Silverlight 4 map viewer
And this post gives you an overview of some of the MVVM Frameworks available.
JAPF » Blog Archive » Discover and compare existing MVVM frameworks !
While MVVM is really a great pattern (and will be even more important with Silverlight 5!), I would really consider twice if this is appropriate for your WP7 application.
Reasons:
No "Command" property for ButtonBase (it's SL3! Command was new in SL4). Therefore no easy use of Commanding-Pattern. You need to use RelayCommands, DelegateCommands or similar.
No Commanding-Pattern at all for items in the Application Bar (ApplicationBarButton or ApplicationBarMenueItem). Not even with RelayCommands, as the ApplicationBarItems do not derive from DependencyObject. :( (see http://blog.galasoft.ch/archive/2010/04/09/using-commands-with-applicationbarmenuitem-and-applicationbarbutton-in-windows-phone-7.aspx)
Dealing with Background-Threads, Dispatcher, etc. can be really cumbersome together with MVVM.
That doesn't mean, you shouldn't use MVVM!
But check out carefully, whether MVVM is a benefit for your project or an additional burden that makes depelopment over-complicated.
HTH
Just wondering should I be going on using MVVM light to buidl enterpside product? I read somewher MVVM is good for starting of small apps and Prism is good for composite apps. Can you please explain what does this mean? I just don't want to have dependency on huge framework like prism as sometimes it takes over the control from you leaving with you the option of following its development methodology. I think MVVM Light is simple and handy but jsut wanted to know whether it can be used in building composition based application or is there something out there where we can extend it to add composition to build modules of the product.
I hope my question is clear
First of all MVVM light is suitable for enterprise apps. However, it is a toolkit and not a full fetched framework, so if you need composition you will have to build it yourself. You could draw on MEF for support.
Prism on the other side is a fameworkthat builds on the MVVM model and the MEF. It has composition on board and you do not have to implement it on your own.
So it depends non then scope and the properties of your enterpise application which one you choose.
There are a couple of misconceptions in your question.
First of all none of the technologies you've mentioned are mutually exclusive. An appliction could be built using Prism, MEF and the MVVM Light toolkit.
Secondly, if you're developing a WPF application then you should be using the MVVM design pattern regardless of which technologies you decide to incorporate.
have dependency on huge framework like
prism
Prism actually has a relatively small footprint in an applications design. The features and components are essentially opt-in. Use the bits you need and ignore the stuff you dont need. Indeed, compared to the monstrosity that was SCSF, Prism is actually well designed.
There are arguably some overlapping goals of both Prism and MEF but this has been discussed here
I need to use the Surface project template for the application that I am working on but I also want to use the MVVM Light Toolkit too. I see that I can "Add | New Item..." and choose an MVVM teamplate for a view, view model, or locator but there seems to be a few more things I need to do to wire this up beyond adding one of those and making sure I have added the reference to the mvvm assemblies.
I am in the process of trying to figure this out by studying what's gets generated when I create a MVVM Light project but I was hoping someone already had this all figured out and documented. I know that Laurent mentioned that he was going to write this up in a blog post but I looked and could not find it. If someone knows where I can find that post that would be killer. Thanks in advance.
It's not too bad adding MVVM Light to an existing project. I finally wrote up the blog post I've been meaning to, just for this situation:
http://chriskoenig.net/2010/07/02/adding-mvvm-light-toolkit-to-an-existing-project/
Enjoy!