This doesn't say you shouldn't use it in an ASP.NET application. This
says you shouldn't use it in a service. It includes Windows services.
It also doesn't say it'll blow up if you do, just reduce the performance
of the service and cause runtime exceptions.
Typically services are light code that need to do a job fast and
efficiently. To increase performance services are often excluded from
using graphic resources although you can create a service which has
access to the desktop which then enables it to use such services.
If your service is excluded from using the desktop then any graphics
usage will throw an exception.
The message is perhaps a bit strong for a caution warning but no big deal.
--
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting
http://www.ramuseco.com
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
Djm181 wrote:
Quote:
According to this page: http://msdn2.microsoft.com/en-us/lib...m.drawing.aspx - System.Drawing
shouldn't be used from an ASP.NET application. For a start this seems mad,
but plenty of people (including me) are doing this. Does this documentation
mean something other than what I am reading?
Cheers
David |