Table of contents
- 1. Overview
- 2. Documentation
- 3. C# Command Line Example
- 4. ASP.NET Example
- 5. Visual Basic Example
- 6. C++ Example
- 7. Custom Functions Example
- 8. Supported Formats
- 8.1.1. Template Formats
- 8.1.2. Datasources
- 8.1.3. Output Formats
Overview
Useful examples for the .NET Engine.
Documentation
- General tutorial videos.
- Sample templates.
- Sample databases connection information.
C# Command Line Example
While you generally will not call Windward from the command line, this provides the simplest illustration of how to call Windward. All of these examples assume you have created a report template using AutoTag and now want to use the engine to generate a report from that template.
These files can be used to create a command-line .exe which is equivalent to the runreport.exe located in the /test folder of the .NET Engine installation. The RunReport application will accomodate a variety of datasource types while the RunReport XML is limited to .xml datasources.
ASP.NET Example
This is a basic example on how to use the Windward Reports .NET Engine in a web application. This example is a pure ASP.NET implementation. There are two front-end sites for this example.
- BasicReportForm.aspx - This page displays inormation on a specific employee. There is a single button to generate a leave of absence letter to send to a manager. The letter is a PDF file.
- ReportForm.aspx - The second page is more dynamic. You choose which leave request number you want the report to be on and the output format.
You are free to use this example in any way you wish.
Visual Basic Example
This is a simple VB forms app to show how to use our engine with VB. It includes one vb file called VBexample.vb, this includes 2 functions, SqlReport and XmlReport, which generate a report using MS Sql and Xml respectivley.
C++ Example
While you generally will not call Windward from the command line, this provides the simplest illustration of how to call Windward from Visual C++. The Visual C++ API provides an API for unmananged C++ to call the Windward engine. It is implemented using a C++ wrapper built with /cli that then calls the underlying .NET Windward engine. Your C++ code is unaware of .NET and you do not need to do anything special to build your code. You do need to have .NET 3.5 and J# 2.0 installed to run the code. The C++ wrapper is included with the .NET Engine install.
Custom Functions Example
This example allows you to create and edit custom functions to be used with the Engine and/or AutoTag. These files can be used to create a WindwardCustomFunctions.dll file containing your own custom functions, to be used with the Windward .NET engine and AutoTag, version 10.0.0.0 or newer.
Note: This project can only be opened in Visual Studio 2005 since it is written in J#.
Supported Formats
Windward supports the following formats/datasources. The examples above may not include all of the below if they were written before some of these formats were added to Windward Reports.
Template Formats
-
Word DOCX
-
Excel XLSX
-
PowerPoint PPTX
-
HTML (limited to a subset of tags and styles and straightforward layout)
-
Word XML (WordML)
-
Word RTF (limited support on input side - not recomended)
-
Excel XML (SpreadsheetML) (limited support on input side - not recomended)
Datasources
-
XML (file, URL, REST, etc.)
-
SQL (any ADO.NET, ODBC, or Ole-DB datasource)
-
You can write your own datasource in about 900 lines of code.
Output Formats
-
Word DOCX
-
Excel XLSX
-
PowerPoint PPTX (only from PPTX templates)
-
HTML (full support on output)
-
Adobe PDF
-
Direct to Printer
-
Word XML (WordML)
-
Word RTF (full support on output)
-
Excel CSV
-
Excel XLS (limited support - not recomended)
-
Excel XML (SpreadsheetML) (limited support - not recomended)
-
ASCII Text


Comments