Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7
This is the forum to discuss the Wrox book Professional SQL ServerReporting Services by Paul Turley, Todd Bryant, James Counihan, George McKee, Dave DuVarney; ISBN: 9780764568787
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
 
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old December 3rd, 2004, 06:52 PM
Registered User
 
Join Date: Jul 2004
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Using Custom Assemblies


I will be heavily using custom assemblies to generate queries for my reports. I have been able to call static members of my C# .NET classes, and am now starting with instance members. However, some of my classes have paramaterized constructors and initializers that I need to call before accessing the methods. How do I make a plain function call in my RDL? If this were ASP I'd just write <%call namespace.class.foo()%>, but I don't see the equivalent in RDL.

Thanks,
Daniel Williams
  #2 (permalink)  
Old December 23rd, 2004, 05:27 PM
Authorized User
 
Join Date: Dec 2004
Location: Phoenix, AZ, USA.
Posts: 13
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via AIM to bsullins
Default

I'm not very familiar w/ C# but I know you can edit the XML of the RDL file, you might be able to accomplish this there...

To view the XML code of the RDL file simply open the report project, in the solutions explorer right click on the RDL file you wish to edit, and select View Code from the pop up menu.

Question:

Why not just write the query in SQL?

Hope this helps!

--
Ben Sullins
Sql Developer - Our Vacation Store
  #3 (permalink)  
Old December 27th, 2004, 01:36 PM
Registered User
 
Join Date: Jul 2004
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for the input BSullins. The reason I need to use real custom assemblies (not just static members) is because I have a ton of existing code which encompasses the business logic of our system. This logic is too complex for simple SQL, so I would like to re-use the existing classes that I have in C# and VB.NET
If I can code to RDL as easily as I do with ASP, then the Reporting Services will be tremendously useful to my company. (BTW: I do edit the RDL directly, as this is often the fastest way to edit the reports.)

Thanks,
Daniel Williams

 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Where are the custom assemblies? johnperez BOOK: Expert SQL Server 2005 Integration Services ISBN: 978-0-470-13411-5 0 December 20th, 2007 06:50 PM
Assemblies smashingpravin .NET Framework 1.x 1 January 2nd, 2007 02:10 AM
Datasets and Custom Assemblies Rendered in Report dillig BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7 0 August 11th, 2004 08:39 AM
Assemblies leeperm C# 2 April 29th, 2004 08:23 AM
Decompilation of assemblies jacob Classic ASP Components 0 July 5th, 2003 07:31 AM



All times are GMT -4. The time now is 04:10 PM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.