Last post Jun 08, 2007 04:47 PM by dkh
Jun 08, 2007 12:35 PM|dkh|LINK
The MSDN documentation for the System.Drawing namespace now contains the following warning:
"Classes within the System.Drawing namespace are not supported for use within a Windows or ASP.NET service. Attempting to use these classes from within one of these application types may produce unexpected problems, such as diminished service performance
and run-time exceptions."
We've done some dynamic image generation in our own ASP.Net applications and were very surprised that this warning had been added to the documentation. Apparently, this means that we are now doing this at our own risk and microsoft won't support any problems
we run into?
Does anyone know what is really going on with this? ASP.Net 2 originally contained an image handler web control but it got pulled from the final version -- are there some serious (e.g. memory leaks, etc.) issues that all of us should know about if we continue
to use system.drawing classes within ASP.Net?
Jun 08, 2007 02:19 PM|shados|LINK
There isn't any known issues with it. However, the classes within the namespace were designed with Windows form in mind, and were only officially tested within that context, and the Microsoft support staff is trained to help with issues that only happen
in that context.
What that means is, it should work fine, you just can't call microsoft support helplines about issues you have with it. It will still work fine and tons of people, including large software development companies use the System.Drawing namespace in ASP.NET environment
all over the place without any issues, so I wouldn't worrie about it.
Jun 08, 2007 04:47 PM|dkh|LINK
Thanks for the quick reply.
What are the chances that the necessary testing will take place in the future so it is fully supported under ASP.Net down the road?