![]() ![]() After all, the app is in the best position to determine if they're in a hosted environment and/or want to risk the GDI+ issues.īut, if you want to automagically detect your environment, I suppose there's worse answers than are offered right here on SO for a service. Personally, I'd probably just leave it up to the hosting app to set a non-interactive flag somewhere or other. If you want something supported, then you need to know if you're running interactively or not. A few of them have been bitten, but there's alot more success than failure stories. So, what are you options? Well, if you don't need a completely supported route, and you don't expect extreme load - a lot of folks have disregarded the MSDN caveat and used System.Drawing with success. ![]() ![]() But, if/when you have a problem, don't expect to be able to call PSS and ask for a fix. Testing will take care of the latter, and monitoring will alert you to the former. ![]() There can be issues with high load (running out of unmanaged resources), memory or resource leaks (badly implemented or called dispose patterns) and/or dialogs being popped when there's no desktop to show them on. To clear up any confusion, System.Drawing does work under ASP.NET and Services, it's just not supported. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |