Comments for My Public Interface http://blog.roboblob.com and ideas for its refactoring... Fri, 03 Sep 2010 19:29:04 +0000 hourly 1 http://wordpress.org/?v=3.0.1 Comment on Custom Silverlight TextBox control that immediately updates DataBound Text property in TwoWay binding by Richard Reukema http://blog.roboblob.com/2010/07/16/custom-silverlight-textbox-control-that-immediately-updates-databound-text-property-in-twoway-binding/comment-page-1/#comment-1785 Richard Reukema Fri, 03 Sep 2010 19:29:04 +0000 http://blog.roboblob.com/?p=385#comment-1785 I found another solution thanks to Laurent of MVVM toolkit - he uses the KeyUp event, which fires each time the key is lifted. I saw this in one of his examples - sorry can't remember which one! I found another solution thanks to Laurent of MVVM toolkit – he uses the KeyUp event, which fires each time the key is lifted. I saw this in one of his examples – sorry can’t remember which one!

]]> Comment on Unit Testable WCF Web Services in MVVM and Silverlight 4 by roboblob http://blog.roboblob.com/2010/04/11/unit-testable-wcf-web-services-in-mvvm-and-silverlight-4/comment-page-1/#comment-1735 roboblob Tue, 31 Aug 2010 13:16:57 +0000 http://blog.roboblob.com/?p=255#comment-1735 no, i could not, because red is my favorite color for attracting people that do not like red color to my blog :D no, i could not, because red is my favorite color for attracting people that do not like red color to my blog :D

]]> Comment on Unit Testable WCF Web Services in MVVM and Silverlight 4 by Nick http://blog.roboblob.com/2010/04/11/unit-testable-wcf-web-services-in-mvvm-and-silverlight-4/comment-page-1/#comment-1734 Nick Tue, 31 Aug 2010 12:42:20 +0000 http://blog.roboblob.com/?p=255#comment-1734 Could not you pick a better color than red? Could not you pick a better color than red?

]]> Comment on Wiring up View and Viewmodel in MVVM and Silverlight 4 – Blendability included by roboblob http://blog.roboblob.com/2010/01/17/wiring-up-view-and-viewmodel-in-mvvm-and-silverlight-4-blendability-included/comment-page-1/#comment-1722 roboblob Mon, 30 Aug 2010 09:03:06 +0000 http://blog.roboblob.com/?p=41#comment-1722 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! 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!

]]> Comment on Wiring up View and Viewmodel in MVVM and Silverlight 4 – Blendability included by Per Åkerberg http://blog.roboblob.com/2010/01/17/wiring-up-view-and-viewmodel-in-mvvm-and-silverlight-4-blendability-included/comment-page-1/#comment-1718 Per Åkerberg Sun, 29 Aug 2010 19:34:01 +0000 http://blog.roboblob.com/?p=41#comment-1718 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. 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.

]]> Comment on Unit Testable WCF Web Services in MVVM and Silverlight 4 by jack http://blog.roboblob.com/2010/04/11/unit-testable-wcf-web-services-in-mvvm-and-silverlight-4/comment-page-1/#comment-1649 jack Wed, 18 Aug 2010 10:29:00 +0000 http://blog.roboblob.com/?p=255#comment-1649 can anyone tell me how to invoke a service that have multiple parameters? can anyone tell me how to invoke a service that have multiple parameters?

]]> Comment on Wiring up View and Viewmodel in MVVM and Silverlight 4 – Blendability included by Mike http://blog.roboblob.com/2010/01/17/wiring-up-view-and-viewmodel-in-mvvm-and-silverlight-4-blendability-included/comment-page-1/#comment-1642 Mike Mon, 16 Aug 2010 22:57:17 +0000 http://blog.roboblob.com/?p=41#comment-1642 Like everyone else, I'm struggling with the ViewModelLocator implementation. I'm definitely interested in your solution and look forward to the write up! Like everyone else, I’m struggling with the ViewModelLocator implementation. I’m definitely interested in your solution and look forward to the write up!

]]> Comment on Wiring up View and Viewmodel in MVVM and Silverlight 4 – Blendability included by How to bind ViewModel to View (part 1) – the Lite toolkit way - Adiel Sharabi http://blog.roboblob.com/2010/01/17/wiring-up-view-and-viewmodel-in-mvvm-and-silverlight-4-blendability-included/comment-page-1/#comment-1536 How to bind ViewModel to View (part 1) – the Lite toolkit way - Adiel Sharabi Tue, 10 Aug 2010 06:57:28 +0000 http://blog.roboblob.com/?p=41#comment-1536 [...] [...] [...] [...]

]]> Comment on Modal dialogs with MVVM and Silverlight 4 by roboblob http://blog.roboblob.com/2010/01/19/modal-dialogs-with-mvvm-and-silverlight-4/comment-page-1/#comment-1503 roboblob Sun, 08 Aug 2010 19:08:12 +0000 http://blog.roboblob.com/?p=109#comment-1503 well i disagree that this should be called IChildWindow since purpose of this entity and the service IModalDialogService is deliberately determined by its name: to show modal dialogs that block UI until user chooses some options or clicks Cancel. I like to call entities in my code with strict names, its a good practice because when entity is called with precise name then he does exactly that and you don't have temptation then to add other features to it. If you start calling classes with general names then its easy to add more functionality to them and then they soon become 'Swiss knife' kind of classes that do everything. If i would need non-modal dialog then i would introduce IDialog and IDialogService same as i did introduce IMessageBoxService etc. All this may sound too strict but practice learned me that strict naming conventions lead to better code. Hope this clarifies why i named the classes as i did. thanks for your feedback! well i disagree that this should be called IChildWindow since purpose of this entity and the service IModalDialogService is deliberately determined by its name: to show modal dialogs that block UI until user chooses some options or clicks Cancel. I like to call entities in my code with strict names, its a good practice because when entity is called with precise name then he does exactly that and you don’t have temptation then to add other features to it. If you start calling classes with general names then its easy to add more functionality to them and then they soon become ‘Swiss knife’ kind of classes that do everything.

If i would need non-modal dialog then i would introduce IDialog and IDialogService same as i did introduce IMessageBoxService etc.

All this may sound too strict but practice learned me that strict naming conventions lead to better code.

Hope this clarifies why i named the classes as i did.

thanks for your feedback!

]]> Comment on Modal dialogs with MVVM and Silverlight 4 by Oliver Weichhold http://blog.roboblob.com/2010/01/19/modal-dialogs-with-mvvm-and-silverlight-4/comment-page-1/#comment-1501 Oliver Weichhold Sun, 08 Aug 2010 16:52:13 +0000 http://blog.roboblob.com/?p=109#comment-1501 Wouldn't it be more appropriate to rename the interfaces from IModalWindow to IChildWindow and from IModalDialogService to IChildWindowService? Technically I don't see anything that would prevent this to be used for non-modal (modeless) dialogs as well. Wouldn’t it be more appropriate to rename the interfaces from IModalWindow to IChildWindow and from IModalDialogService to IChildWindowService? Technically I don’t see anything that would prevent this to be used for non-modal (modeless) dialogs as well.

]]>