7 Answers, 1 is accepted
0
Hello Randy,
Telerik Reporting does work in applications targeting .NET4 framework. The only thing you should change if you're using web application is the http handler registration, namely the preCondition attribute so that it targets the correct framework i.e.:
If this is not what you're after, please elaborate so we can advise you accordingly.
Kind regards,
Steve
the Telerik team
Telerik Reporting does work in applications targeting .NET4 framework. The only thing you should change if you're using web application is the http handler registration, namely the preCondition attribute so that it targets the correct framework i.e.:
<
system.webServer
>
<
handlers
>
<
add
name
=
"Telerik.ReportViewer.axd_*"
path
=
"Telerik.ReportViewer.axd"
verb
=
"*"
type
=
"Telerik.ReportViewer.WebForms.HttpHandler, Telerik.ReportViewer.WebForms, Version=x.x.x.x, Culture=neutral, PublicKeyToken=a9d7983dfcc261be"
preCondition
=
"integratedMode,runtimeVersionv4.0"
/>
</
handlers
>
<
validation
validateIntegratedModeConfiguration
=
"false"
/>
</
system.webServer
>
If this is not what you're after, please elaborate so we can advise you accordingly.
Kind regards,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Randy
Top achievements
Rank 1
answered on 29 Jun 2010, 03:03 PM
Thanks for the reply.
I tried to move to .Net 4 and everything worked except the reporting. I double checked the system requirements here
http://www.telerik.com/products/reporting/resources/system-requirements.aspx
And it shows it compatible with only 2 and 3.x
I will make the changes you suggested and retry.
Thanks Again
Randy
I tried to move to .Net 4 and everything worked except the reporting. I double checked the system requirements here
http://www.telerik.com/products/reporting/resources/system-requirements.aspx
And it shows it compatible with only 2 and 3.x
I will make the changes you suggested and retry.
Thanks Again
Randy
0
Hi Randy,
Thank you for bringing this to our attention - we've updated the system requirements page. If you are still having problems under .NET4 please elaborate on them - what errors/exceptions do you receive, providing stack trace and as much details as possible.
Kind regards,
Steve
the Telerik team
Thank you for bringing this to our attention - we've updated the system requirements page. If you are still having problems under .NET4 please elaborate on them - what errors/exceptions do you receive, providing stack trace and as much details as possible.
Kind regards,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Randy
Top achievements
Rank 1
answered on 29 Jun 2010, 03:44 PM
I noticed that it says integrated mode. My app pool is runningin Classic mode. We couldn't get the WCF service for our silverlight app running correctly and Microsoft suggested that we try Classic. That cleared everything up and got it running. They said they have had some problems with WCF and integrated.
Is that going to be a problem with the reports, or will I have to change the config file?
Thanks
Randy
Is that going to be a problem with the reports, or will I have to change the config file?
Thanks
Randy
0
Hello Randy,
The http handlers registration is only needed for the web report viewer and not relevant to the Silverlight counterpart. The Telerik Reporting service is a standard WCF service and thus would act like a normal WCF service in your app. If they admitted problems with Integrated mode, you should use classic as suggested.
Sincerely yours,
Steve
the Telerik team
The http handlers registration is only needed for the web report viewer and not relevant to the Silverlight counterpart. The Telerik Reporting service is a standard WCF service and thus would act like a normal WCF service in your app. If they admitted problems with Integrated mode, you should use classic as suggested.
Sincerely yours,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Randy
Top achievements
Rank 1
answered on 29 Jun 2010, 04:15 PM
That seems to have taken care of it.
Thanks for you help.
I am a little curious, I had the same line, but didn't include anything from the version on. So the version was blank. And it didn't work. Not too concern because it is working now, but do you have an easy explanation off the top of your head?
Thanks
Randy
Thanks for you help.
I am a little curious, I had the same line, but didn't include anything from the version on. So the version was blank. And it didn't work. Not too concern because it is working now, but do you have an easy explanation off the top of your head?
Thanks
Randy
0
Hello Randy,
The type in the http handler should always contain the assembly qualified name.
Best wishes,
Steve
the Telerik team
The type in the http handler should always contain the assembly qualified name.
Best wishes,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items