Ant plans to factor out design support in separate assemblies? Can't deploy your components to .Net Client Profile since your components reference System.Design.dll. I've seen other vendors putting this reference in other dll's so that the core components doesn't need the full framework.

I know this is only a problem for 3.5 and 4.0 Frameworks, as with 4.5 and above there is no Client Framework. But still many of our customers are running on 4.0 Client Framework, so we currently need to address this...

Sorry, forgot to mention that. I'm using EO.WebBrowser. I'm evaluating it now, and will buy a licence since it seems to work very well, and is updated frequently:-)

I have started to log what framework type our users with .Net4 are using, and it seems most actually have the full framework. So I have re-targeted our product (a click-once deployed application) to require the full .Net4 framework. It seems this is a viable solution, since not so many will need to upgrade.

But I'm guessing this might also be a problem for other customers, so it would be nice to be able to target the client framework. The problem is corporate managed machines where the users cannot upgrade themselves...

Hi,

This is just to let you know that we have posted a new build that removed the reference to System.Design.dll. You can download the new build from our download page.

Thanks!