Wednesday, May 09, 2012 6:57 PM
I recently upgraded my website (source code here) from 3.5 to 4.0. I changed all the references in web.config to point to 4.0, as discussed here. I have a custom handler written (to deal with web farm scenario on Azure) that looks like this:
<add key="ChartImageHandler" value="handler=ArchivistWeb.Helpers.ChartImageHandler, ArchivistWeb"/>However, when I run the app, the handler does not get picked up and it appears that the .dll just loads the default value for ChartImageHandler. It never finds my handler. Is there something else I need to do in the .NET 4.0 version to register my handler?
Thursday, May 10, 2012 12:50 PMModerator
I've no experience with custom chart image handlers so I'll just throw in a link to this thread.
It looks like you probably should be getting an error if the handler is not found. Also the format of the AssemblyQualifiedName looks slightly different from what the answer in the linked thread suggests.
- Edited by siplaModerator Thursday, May 10, 2012 12:50 PM
Thursday, May 10, 2012 4:15 PMRight, that thread is from .NET 3.5, which works fine. It is 4.0 which doesn't work. Assembly qualified name is fine. Yes, you'd think it would blow up, but instead it is just calling the default setting and never even looking for my ChartImageHandler...
Thursday, May 10, 2012 9:14 PMturns out that this is caused by the somewhat kludgy way I'm using WebForms inside MVC to get the image map (tooltips, etc.) to work. currently exploring no longer doing things that way and using this methodology instead: http://geekswithblogs.net/DougLampe/archive/2011/01/23/charts-in-asp.net-mvc-2-with-drill-down.aspx
- Marked As Answer by rhizohmMicrosoft Employee Thursday, May 10, 2012 9:14 PM