Take the 2-minute tour ×  I am thinking about going into .net
framework client profile, but currently I am depending on
System.Design.dll, which is not inside the profile.  I can, of
course, manually distribute them in my application folder
directory, but is there a better strategy?  share|improve this
question add comment  4 Answers  up vote 2 down vote accepted
You have two options:    1. target the full desktop framework
2. refactor your code to remove the System.Design.dll dependency
See also this blog post.  share|improve this answer add comment
I don't think you are legally permitted to distribute individual
.NET Framework DLLs. If you depend on a DLL that's not part of
the client profile, either get rid of the dependency somehow or
don't target the client profile; consider requiring the full
.NET Framework.  share|improve this answer add comment  The
problem with manually distributting your local System.Design.dll
is that if that dll gets patched in the framework later on, your
app will keep using