| Groups | Blog | Home |
dotnet drawing api : Dot Net 2.0 Restrictions???
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. And if that is the case then this sucks. We have applications that are Windows service and perform image processing. So far we have not had issues and if 2.0 has problems then we will not be able to migrate to it. Please advise... Thanks in Advance!
From MSDN Web Site System.Drawing help at
http://msdn2.microsoft.com/en-us/library/xs6ftd89(en-US,VS.80).aspx [quoted text, click to view] "Lloyd Dupont" wrote:
> Where did you get this idea from? > > > Is it true that from Dot Net 2.0 onwards >> > > 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. > > > > And if that is the case then this sucks. We have applications that are > > Windows service and perform image processing. So far we have not had > > issues > > and if 2.0 has problems then we will not be able to migrate to it. > > > > Please advise... > > > > Thanks in Advance! > > > >
Interesting.
I have no idea what problems this will create. However, I have some things that I wanted to do in a service, but had been waiting for .NET 2.0 before I started coding them. If this really does not work, then my plans are now shot! I suspect I desired to do something similar to what "JK" might want to do. Basically, I had planned to use a service to generate graphics for my CAD application and feed them down to a web browser and/or other client. Gerald [quoted text, click to view] "JK" <JK@discussions.microsoft.com> wrote in message news:C5601BEF-52E9-4D97-B4F6-E3BC606055B2@microsoft.com... > From MSDN Web Site System.Drawing help at > http://msdn2.microsoft.com/en-us/library/xs6ftd89(en-US,VS.80).aspx > > > "Lloyd Dupont" wrote: > > > Where did you get this idea from? > > > > > Is it true that from Dot Net 2.0 onwards >> > > > 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. > > > > > > And if that is the case then this sucks. We have applications that are > > > Windows service and perform image processing. So far we have not had > > > issues > > > and if 2.0 has problems then we will not be able to migrate to it. > > > > > > Please advise... > > > > > > Thanks in Advance! > > > > > > > > >
allright...
I would think that's just a new warning and that GDI+ is no less compatible in 2.0 than it was in 1.0 & 1.1. It's just that are some issues and they are warning people before hand.. I assume.. -- Regards, Lloyd Dupont NovaMind development team NovaMind Software Mind Mapping Software <www.nova-mind.com> [quoted text, click to view] "JK" <JK@discussions.microsoft.com> wrote in message news:C5601BEF-52E9-4D97-B4F6-E3BC606055B2@microsoft.com... > From MSDN Web Site System.Drawing help at > http://msdn2.microsoft.com/en-us/library/xs6ftd89(en-US,VS.80).aspx > > > "Lloyd Dupont" wrote: > >> Where did you get this idea from? >> >> > Is it true that from Dot Net 2.0 onwards >> >> > 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. >> > >> > And if that is the case then this sucks. We have applications that are >> > Windows service and perform image processing. So far we have not had >> > issues >> > and if 2.0 has problems then we will not be able to migrate to it. >> > >> > Please advise... >> > >> > Thanks in Advance! >> > >> >> >>
Where did you get this idea from?
[quoted text, click to view] > Is it true that from Dot Net 2.0 onwards >> > 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. > > And if that is the case then this sucks. We have applications that are > Windows service and perform image processing. So far we have not had > issues > and if 2.0 has problems then we will not be able to migrate to it. > > Please advise... > > Thanks in Advance! >
[quoted text, click to view]
> From MSDN Web Site System.Drawing help at > http://msdn2.microsoft.com/en-us/library/xs6ftd89(en-US,VS.80).aspx Well, if you think about it, everytime you use a chart control in your asp.net application how do you think they are generating the graphics for display? They're using GDI+ I'm certain, especially since they proudly announce it is written in fully managed code... it must be System.Drawing.*. True, it might impact performance. But even if you write the graphics manipulation routines yourself in assembly language and call them from your web application it is impacting performance... because it has to consume clock cycles to do its thing. Its always going to be slower than if it wasn't there in the first place. However, GD+ isn't hardware accelerated like GDI was. Thus, everytime you call something in System.Drawing.* it is actually using software logic and that is definately slower than if it was hardware aceelerated (a la GDI classic) or if it wasn't there at all. I wouldn't worry about it. Thanks, Shawn
System.Drawing/ GDI+ was designed to work in a user process on the
desktop, in a forms environment etc. My feeling on this that System.drawing relies heavily on the graphics object which in turns wraps a windows handle, and in that service applications you may have reduced permissions, especially in upcoming vista/ windows server products which may prevent some of these functions working correctly... Also creating 1 or more handles on a web site per session with many users at the same time will cause problems, and so ms will add this disclaimer to absolve themselves from having to deal with these scalability issues. Im sure all component vendors use gdi+ on some kind of handle to perform processing like this for asp.net charting/diagramming components, but if they are smart im sure they will use a singleton or thread pool solution to handle graphics rendering. If it keeps you awake at night you could look into the SVG standard which creates graphics through xml markup, much like the new Windows Presentation Framework classes will do, but its a lot of work and the browser needs a plugin for it to work correctly. James www.crainiate.net [quoted text, click to view] JK wrote:
> Is it true that from Dot Net 2.0 onwards >> > 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. > > And if that is the case then this sucks. We have applications that are > Windows service and perform image processing. So far we have not had issues > and if 2.0 has problems then we will not be able to migrate to it. > > Please advise... > > Thanks in Advance!
I interpret that wording in the same way. I think that they are just warning
people that services are not well adapted to lengthy or memory intensive operations. I'd go ahead as before I think. -- 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. [quoted text, click to view] "Lloyd Dupont" <net.galador@ld> wrote in message news:u2J5H7uIGHA.984@tk2msftngp13.phx.gbl... > allright... > I would think that's just a new warning and that GDI+ is no less > compatible in 2.0 than it was in 1.0 & 1.1. > It's just that are some issues and they are warning people before hand.. I > assume.. > > -- > Regards, > Lloyd Dupont > > NovaMind development team > NovaMind Software > Mind Mapping Software > <www.nova-mind.com> > "JK" <JK@discussions.microsoft.com> wrote in message > news:C5601BEF-52E9-4D97-B4F6-E3BC606055B2@microsoft.com... >> From MSDN Web Site System.Drawing help at >> http://msdn2.microsoft.com/en-us/library/xs6ftd89(en-US,VS.80).aspx >> >> >> "Lloyd Dupont" wrote: >> >>> Where did you get this idea from? >>> >>> > Is it true that from Dot Net 2.0 onwards >> >>> > 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. >>> > >>> > And if that is the case then this sucks. We have applications that are >>> > Windows service and perform image processing. So far we have not had >>> > issues >>> > and if 2.0 has problems then we will not be able to migrate to it. >>> > >>> > Please advise... >>> > >>> > Thanks in Advance! >>> > >>> >>> >>> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |