Creating a DotNetNuke Private Assembly with Crystal Reports - Part 3
page 1 of 5
Published: 06 Jan 2006
Unedited - Community Contributed
In this 3rd of a four-part series, Eric shows how to display the Crystal parameters dynamically in a private assembly for DNN.
by Eric Landes
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 24041/ 51


As mentioned in Part 1 of this series, DotNetNuke is a great Open Source Portal tool that many in the ASP.NET world use.  Please refer to Part 1 for more information about DotNetNuke.  In Part 2, we explored the DNN Data Access architecture for our application.  Then, we created our own DAL and BLL based on the DNN architecture.  Finally, we created the administrative interface to allow users to add and edit where reports are located.  The data entered from this interface is used in this part of the series in helping to display a report’s parameters.

In Part 3, we will utilize a helper class (based on a previous article of mine) to display reports that have been stored via the Report Manager app.  Then, the application will display the parameters for a report and display the report.  Part 3 specifically details how to display the parameters of a crystal report. 

System Requirements

I created this project using Visual Studio 2003, DotNetNuke 3.1.1, SQL Server 2000, Crystal Reports 10, and Windows XP SP2.

View Entire Article

User Comments

Title: Wrong Source code   
Name: Jesse
Date: 2006-02-07 10:41:45 AM
The source code available here contains no more that a buggy DNN module with only a single form to store a list of files, but nothing about displaying the reports. Wrong version/ manipulation?

Product Spotlight
Product Spotlight 

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024  |  Page Processed at 2024-07-24 7:11:53 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search