One thing I have learned from a past client I have worked for, it can be a problem to put too many Silverlight web resources into a solution. The solution can quickly grow to huge sizes and can make the solution non-portable.
If you feel you need a lot of Silverlight embedded in your CRM app, a better way might be to stick to the SOAP service and host your Silverlight apps separately from CRM and expose them through an Iframe.
- I hope this helps!
What is your thought on using multiple solutions to keep the solution file sizes down but still have it in a solution based framework?
ReplyDeleteThat is fine in many cases and that is how we got around the problem of exporting the base solution. The problem arises when you can no longer export and import your solutions due to their size.
ReplyDeleteSo that is another valid way to deal with this issue.
useful experience.Thanks Jamie
ReplyDeleteHi Jamie,
ReplyDeleteI bumped into this article and I think it is a great solution for the problem you describe in the post. What do you think?
http://blogs.msdn.com/b/crminthefield/archive/2012/01/19/building-multi-purpose-silverlight-web-resources-in-dynamics-crm-2011.aspx
That's funny actually. Notice Austin's blog was written one day after mine. We were both out at the same client at the time actually so not only is he talking about the same problem. Both blog posts actually came from the same situation at the same client. :)
Delete