Custom Query Designer from VS2003 to VS2005

Hello,

I have a Data Processing Extension (DPE) that worked quite well in VS2003 with MSSQL2000 RS. I'm trying to port it to VS2005 with MSSQL2005 RS and I'm having the following problem.

In 2003 I used Microsoft.ReportDesigner.Interfaces.IQueryDesigner to define the query designer inside of VS2003. In 2005, that line does not compile; I get “The type or namespace ‘interfaces’ does not

exist in the namespace ‘Microsoft.ReportDesigner’ (Are you missing an Assembly

reference?)”

What is the 2005 equivalent of that interface? What's the best way to port an 2003 DPE to 2005?

Thanks

The IQueryDesigner interface has been renamed to Microsoft.ReportingServices.Interfaces.IQueryDesigner and you should add a reference to Microsoft.ReportingServices.QueryDesigners.dll.

-Albert

|||Thanks, that was it.

Custom DPE Permission Set

Hi All,
I created a custom data processing extension wrapping calls to the .Net
System.Data.OLEDB classes. I don't want to give the DPE FullTrust
permissions in the rssrvpolicy.config file.
I noticed that there is a SecurityClass entry for SQLClientPermission in
rssrvpolicy.config file. However, it doesn't seem obvious to me how to
create a similar entry for the System.Data.OLEDB classes.
Any ideas, or does everyone simply use FullTrust?
Thanks in advance for help!FullTrust permissions are required for custom data processing extensions at
this point.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dand" <Dand@.discussions.microsoft.com> wrote in message
news:024D777F-6401-4714-9817-10852BF6189A@.microsoft.com...
> Hi All,
> I created a custom data processing extension wrapping calls to the .Net
> System.Data.OLEDB classes. I don't want to give the DPE FullTrust
> permissions in the rssrvpolicy.config file.
> I noticed that there is a SecurityClass entry for SQLClientPermission in
> rssrvpolicy.config file. However, it doesn't seem obvious to me how to
> create a similar entry for the System.Data.OLEDB classes.
> Any ideas, or does everyone simply use FullTrust?
> Thanks in advance for help!
>

Custom assembly or DPE?

Hi im writting a new report engine, but i need to have some advice about when
is highly recommended Custom Assemblies or DPE?
Thanks1.- Create a DPE will help you if you require more than a plain stored
procedure.
2.- Custom Assembly will help you for granular items, for example: calculate
or agregate, mask for values per field.
The main differences apparte of the deployment stuff, is the scope, if you
want to address, the whole recordset use DPE or some fields use custom
assemblies.
Thanks
Jerry
--
Call webservices from SQL RS
http://www.rdlcomponents.com/DTE/Default.aspx
Call webservices from SQL Server 2000
http://www.rdlcomponents.com/EXSP/default.aspx
"Andrew" wrote:
> Hi im writting a new report engine, but i need to have some advice about when
> is highly recommended Custom Assemblies or DPE?
> Thanks
>

Custom Assembly not Executing

I have both a custom assembly and a data processing extension. The DPE I
have successfully integrated into RS. But, I have written a custom assembly
that I use for creating a barcode image. I run it fine in ReportDesigner and
believe I have given it and the Barcode.dll (3rd party) "FullTrust" in the
rssrvpolicy.config file.
The problem is when I run I do not even get an error. I integrated the
EventLog to try to trace the problem but it never gets called by Reporting
Services and just renders the image empty.
If anyone has any suggestions on this I would greatly appreciate it. I have
a custom assembly that uses a 3rd party (Pegasus SmartExpress Barcode) dll.
I can execute perfectly in VS.Net design mode. But, cannot in ReportManager.
Thanks
TomTom,
Possibly the registered Assembly has the incorrect Assembly version in
Report Designer (see report Properties ... References)
I avoid having to delete and re-define the refernece to the newly compiled
assembly by stopping version incrementation in the AssemblyInfo.cs file ie:
[assembly: AssemblyVersion("1.0.0.0")]
regards,|||Simon
Thanks for the idea it makes sense...but it didn't work either. Not sure
what's going on here.
Tom
"Simon" wrote:
> Tom,
> Possibly the registered Assembly has the incorrect Assembly version in
> Report Designer (see report Properties ... References)
> I avoid having to delete and re-define the refernece to the newly compiled
> assembly by stopping version incrementation in the AssemblyInfo.cs file ie:
> [assembly: AssemblyVersion("1.0.0.0")]
> regards,
>