Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / October 2007

Tip: Looking for answers? Try searching our database.

Windows Forms library in an ASP code behind

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
justin - 17 Oct 2007 22:01 GMT
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
the best one required the Windows.Forms class to be used in the C#
code-behind. When I tested the library, this worked fine in Visual
Studio 05.

What I was wondering was, are there performance concerns or security
concerns in using the Windows.Forms library in an ASP.NET website?
Will using it impact my scalability? All thoughts are welcomed, thank
you.
bruce barker - 18 Oct 2007 04:46 GMT
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.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.