it depends.
asp.net server code can not create actual window.forms controls as these
is no desktop to create a window on. if you control tries to create a
window it will fail, but it may not need to.
a dll used in asp.net should be thread safe, this is not an issue for a
windows application, so you may run into problems here.
-- bruce (sqlwork.com)
> Hello, recently I was working on a project where I needed to automate
> PDF generation. I found two open source libraries that I liked, but
[quoted text clipped - 6 lines]
> Will using it impact my scalability? All thoughts are welcomed, thank
> you.
justin - 18 Oct 2007 19:13 GMT
> it depends.
>
[quoted text clipped - 17 lines]
> > Will using it impact my scalability? All thoughts are welcomed, thank
> > you.
Thank you very much for your help.
The API I'm using for PDF creation was meant for Windows.Forms but
doesn't actually create any forms or windows. If I import the
Windows.Forms library in my C# code-behind it works fine. I just
wasn't sure if the functions in the Windows.Forms library scale to the
level needed for a web application. I'm looking at up to 200 users,
but probably no more than 30-40 at peak usage. I would like the
application to be much more scalable however and wasn't sure how
Windows.Forms would impact that.