Feasibility of using Silverlight for web and windows client with common code base for data intensive
- by Kabeer
Hello. Recently in a conversation, someone suggested me to make use of Silverlight if I am targeting a web client and a windows client for the same application. This will cut down my effort for supporting the contrast in both presentation layers.
Mine is a product, that will be deployed in enterprises. Both web and windows clients are desirable.
With the above context, I have few queries:
Is it advisable to adopt the recommended approach and whether this approach is becoming a trend?
Besides, some configuration & deployment tweaking, will this significantly reduce effort on the presentation layer?
Is there a possibility that my future prospects (for this product) will resist Silverlight footprint?
Will I be able to make use of the ASP.Net MVC pattern?
Will there be any performance implication for the web client?
Will Silverlight support incremental load of controls?
If my back-end includes SSRS, will I be able to harness all its front end features with Silverlight?
Will I be able to support additional devices with same code base in future?
Mine is a very data intensive application from both, data entry and reporting perspective. Is it advisable to use 3rd party controls (like Telerik) for improved user experience and developer productivity?
Are their any professional quality open source Silverlight controls (library) available?
Further, I seek information of best practices in the context I shared above.