Skip to main content

Posts

Showing posts with the label silverlight

Advantages of Prism

Reusability : Prism allows building component in one framework (WPF) and reusing it in other platforms (Silverlight, Windows Phone). Project architecture should design in such a way. Modularity : As everything is break down into modules, Prism supports modularity due to this PRISM is flexible, extensible . Extensibility : Due to Prism design patterns nature new functionality that is to be added is easily extensible for future purpose. Maintainability : The large scale complex applications developed using Prism are maintenance friendly. Flexibility : Prism is flexible to develop large complex applications. Team Collaboration : Simultaneous module development is possible and Multiple teams can work on different modules simultaneously. Fault Tolerance : It allows components to be thoroughly and completely tested thus results in error free application development of better quality.  

What is Prism?

Prism is a framework or the set of guidelines which is used to develop  Composite or Complex applications specific to WPF , Silverlight or Windows Phone .   It's a kind of Design Pattern to develop XAML based applications.  Prism mainly helps to design the Loosely Coupled components which can be easily integrated with other components of the application. It uses modularity and allows to break application into pieces can be called as Modules.   Prism uses design patterns like MVVM , Command Pattern , Dependency Injection (DI) and Inversion of Control (IoC) and Separation of Concerns to achieve Loosely Coupling. Prism has the following advantages over other frameworks. Reusability, Extensibility, Flexibility, Team Collaboration, Fault Tolerance, Maintainability and Modularity. Prism has 5 main components: 1) Shell: Template that Defines structure of the UI. Shell can contains several regions. 2) Regions: Regions are used to specify specific portion o...

Large Volume of Dataset Transfer from WCF to Silverlight

Most of the times the developers, architects have the problem to retrieve large volume of data from WCF Service to Silverlight client applications. It’s a big head ache for developers. But it’s not up to that much problematic one. We can solve this problem by changing some property’s values in Web.config of WCF Service host, Silverlight application’s ServiceReference.clientconfig and Silverlight XAP hosted ASP.Net Applications. Here I’m going to explain the Web.config changes we need to retrieve large volume of data from WCF Service and also uploading large size of files to the Server. Last week, I was trying to figure out why my WCF service call always threw the generic NotFound exception when trying to retrieve large datasets. Even though, I set buffer limits to 2147483647 (int.MaxValue) in the Silverlight ServiceReferences.ClientConfig file and WCF Service configuration Section under web.config the problem was persisting. I tried so many things from Data Access Layer and UI....