Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Wrapper for 3rd party controls
4 views
Skip to first unread message
Rajesh V
Jul 9, 2010, 6:53:35 AM7/9/10
to
Hi,
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.
Regards
Rajesh V
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.
Regards
Rajesh V
Günter Prossliner
Jul 13, 2010, 5:38:08 AM7/13/10
to
Hello Rajesh!
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
0 new messages