It really depends on the control. Many controls you can simply deploy
as flat files (i.e. just include the dll in the build output); and
depending on the vendor there may be some "licx" stuff going on in the
background. Or some other controls may need to be installed on the
machine that will be running it, which (for a client app) you might do
via pre-reqs or an msi.

You will probably have to install it on any development machines and
your central build server (if you have one); I would hope that servers
just pick up the dll from the bin folder.

Also check that you are licenced to install it where you want to ;-p
(just a general advisory; I don't know anything about supergoo's
license...)

If it is your ASP.NET web application that will be generating the PDF's then
yes of course the component must be in the /bin folder of the IIS Application
in order for it to be used.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short Urls & more: http://ittyurl.net