I recently downloaded the trial of the reporting component, and have created a report project in my solution with a couple of reports. Upon running the web site I get the "failed to map path" error, which upon searching I see is a security issue - http://www.telerik.com/community/forums/reporting/telerik-reporting/failed-to-map-the-path.aspx. Are you actually saying that to run your report viewer I have to run as an Administrator, when we should actively be encouraging users to run without elevated rights? Do I, and the rest of the developers, now have to Run as Admin every time, sometimes forgetting, then having to close VS and reopen it?
In the replies to the other thread you state that it's the WebConfigurationManager causing the error and that you can't touch that, which is true, but not helpful. The error is because you loop through the handlers to ensure that Telerik.ReportView.axd is present and it's that and only that, that requires elevated permissions as far as I can see. there really any reason to check that the handler is present? You could easily document the requirements for the handler; I have to add the handler anyway, so why check for its presence? There may be a very good reason why you need to check, and I'd love to hear it, but all I can see is that you throw an exception when initialising the viewer if the handler isn't configured.
I love the reporting framework you've built, but this is causing me to think again about using it.
Dave
In the replies to the other thread you state that it's the WebConfigurationManager causing the error and that you can't touch that, which is true, but not helpful. The error is because you loop through the handlers to ensure that Telerik.ReportView.axd is present and it's that and only that, that requires elevated permissions as far as I can see. there really any reason to check that the handler is present? You could easily document the requirements for the handler; I have to add the handler anyway, so why check for its presence? There may be a very good reason why you need to check, and I'd love to hear it, but all I can see is that you throw an exception when initialising the viewer if the handler isn't configured.
I love the reporting framework you've built, but this is causing me to think again about using it.
Dave