Services
Support
Store
©2015 Intersoft Solutions. All rights reserved.

Confused about silverlight frameworks

2 replies. Last post: August 25, 2011 8:03 AM by Georgios Diamantopoulos
Tags :
Post Reply
Posted: August 16, 2011 6:17 PM

Hello everyone,

We are new to Silverlight development and although I'm a quick learner, I'm struggling to understand how the various frameworks fit together, if at all.

I've been reading good things about Prism and MS seems to encourage its development which is always good.

My question is - is ClientUI a replacement for Prism? Or can you use them side-by-side? In either case, please include a short intelligible description of how they relate.

Thank you

Answers

Jimmy PetrusAdministrator
Posted: August 23, 2011 8:35 AM in response to Georgios Diamantopoulos
Hello Georgios,

Welcome to Intersoft Community Forum!

Comparing ClientUI and Prism is not apple to apple, because Prism provides only artchitectural and design pattern libraries, while ClientUI provides a multitude of MVVM-ready user interface controls along with advanced frameworks and design pattern libraries.

Based on our experiences in Silverlight project development, we don't require Prism when building apps using ClientUI. That's because ClientUI already has application framework that supports external XAP (on demand download), as well as integration with navigation and windowing framework.

I hope my explanation gives you insights on Silverlight frameworks particularly on ClientUI and Prism. Let me know if you have any questions.

Thanks,
Jimmy

All Replies

Jimmy PetrusAdministrator
Posted: August 23, 2011 8:35 AM in response to Georgios Diamantopoulos
Hello Georgios,

Welcome to Intersoft Community Forum!

Comparing ClientUI and Prism is not apple to apple, because Prism provides only artchitectural and design pattern libraries, while ClientUI provides a multitude of MVVM-ready user interface controls along with advanced frameworks and design pattern libraries.

Based on our experiences in Silverlight project development, we don't require Prism when building apps using ClientUI. That's because ClientUI already has application framework that supports external XAP (on demand download), as well as integration with navigation and windowing framework.

I hope my explanation gives you insights on Silverlight frameworks particularly on ClientUI and Prism. Let me know if you have any questions.

Thanks,
Jimmy
Posted: August 25, 2011 8:03 AM in response to Jimmy Petrus
That's great - it answers my question - ClientUI is a superset to Prism.
WebGrid: How to call the server side BatchUpdate m...
The custom checkbox of the column header of the we...
All times are GMT -5. The time now is 12:02 AM.
Previous Next