Comments on: Wiring up View and Viewmodel in MVVM and Silverlight 4 – Blendability included

By: Dorie

Dorie — Wed, 28 Sep 2011 17:31:03 +0000

Thanks for spending time on the comtpuer (writing) so others don’t have to.

By: Hammad

Hammad — Fri, 15 Jul 2011 08:15:11 +0000

can you post some code to open ChildWindow in VM with current pattern using delegate command

By: roboblob

roboblob — Mon, 06 Jun 2011 08:09:22 +0000

Hi Abram,

can you be more specific what kind of problems you have in IE and which version. I tested in IE 8 and it works fine.
thanks!

By: Abram Kukauskas

Abram Kukauskas — Mon, 06 Jun 2011 01:13:31 +0000

Hi, Neat post. There is a problem with your site in internet explorer, would test this IE still is the market leader and a large portion of people will miss your magnificent writing due to this problem.

By: roboblob

roboblob — Tue, 26 Oct 2010 18:44:49 +0000

Hi Serkan,

thanks for your comment!

By the way, I have lately moved away from the concept of ViewModelLocator since i discovered its not good enough for complex MVVM scenarios.
If you want to see my latest take on Silverlight MVVM and Blendability take a look at my latest posts:

http://blog.roboblob.com/2010/10/15/combining-silverlight-navigation-framework-and-prism-to-create-mvvm-applications-introduction/
http://blog.roboblob.com/2010/10/24/introducing-prism-navigation-framework-for-silverlight-mvvm-applications/

By: serkan ayvaz

serkan ayvaz — Tue, 26 Oct 2010 17:14:37 +0000

Hi Rob,

Thanks for such a great article, I thought it was very clear and helpful in explaining the blendability and MVVM.
Of course, a special thanks to Laurent Bugnion for developing the MVVM Light framework, which makes it a lot easier with implementation of ViewmodelLocator.

By: roboblob

roboblob — Wed, 29 Sep 2010 07:14:30 +0000

Hi Geoff,

i found out after this article that ViewModelLocator pattern brings more problems that it solves.
Im planning to write another article on this subject with completely different approach – separate service that will instantiate View and ViewModel and then show them on screen.
Stay tuned, i think you will find this approach much more natural then ViewModelLocator.

Thanks for your feedback!

By: Geoff

Geoff — Sun, 26 Sep 2010 21:17:23 +0000

I Like the ViewModelLocator. The downside I see is that in not having the global, static view model locator the other viewmodels are not instantiated so when I want to use messaging to navigate between the views, I have to send the message from the source ViewModel to a destination page, then back to the destination view model for that page.

http://chriskoenig.net/2010/07/05/mvvm-light-messaging/

By: roboblob

roboblob — Mon, 30 Aug 2010 09:03:06 +0000

Hi,

glad it works for you.
I will definitely try to post more on the INavigationService approach since it turned out to be better than ViewModelLocator and also i get lot of requests to write about it lately…
Thanks for your feedback!

By: Per Åkerberg

Per Åkerberg — Sun, 29 Aug 2010 19:34:01 +0000

Hey there,

I really enjoy all your posts on SL and MVVM. Keep it up!
I was curious to know about the other solution you had and if I could use it. I just got this one working and kind of like it, although I don’t like having to create a new class for each viewmodel to locate it, but I guess thats a trade-off for getting this good thing to work!

By the way, the “d:DataContext” thing only seems nescessary in VS 2010 design mode, not for Blend 4. Blend works fine without it.

Please come back with more info on the other approach, I am really interested!

Thanks alot for your work.