Hello Rajesh!
Quote:
We have purchased a thrid party silverlight controls. We have some
framework and this framework is consume by web applictions (more than
one) We dont want each of these client applications to refer this
thrid party controls assembly instead we want to wrap it. Problem is
there are more than 150 class whihc we have to wrap to make it work
that way. is there any wayout for this problem.
Thanks in advance. |
If you can't define a "simple" contract with a few Methods it will not be
worth to warp 150 types. What will you gain from it?
* If you wrap at the level of individual types and behaviour of the control,
it will be nealy impossible to implement the same interface for another
control.
* You have a binary dependency, so the Assembly must be available anyway.
GP