RE: [Nant-users] Using NAnt to Run Visual Studio.NET Custom Tools

[Hart, Leo]

Title: Message

I'll submit a bug report as you requested for Crystal Reports, but does the same solution apply to the MSDataSetGenerator for DataSets?

 

Thanks,

Leo

-----Original Message-----
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 10, 2004 2:56 AM
To: Hart, Leo; [EMAIL PROTECTED]
Subject: RE: [Nant-users] Using NAnt to Run Visual Studio.NET Custom Tools

Leo,

 

There's no support for this right now, but can you submit a bug report for this and a sample that just relies on the crystal reports that ships with VS.NET (as I don't have a license for the full Crystal Reports application). I'll see if we can add support for this somehow (post 0.85).

 

Gert

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hart, Leo
Sent: dinsdag 9 november 2004 16:26
To: [EMAIL PROTECTED]
Subject: [Nant-users] Using NAnt to Run Visual Studio.NET Custom Tools

Hello,

 

I have a Windows Forms project that contains:

Build file (Loan.Build) in root

Forms (.resx, .vb) in folder Dataset

Crystal Reports (.rpt, .vb) in folder Form

DataSets (.vb, .xsd, .xsx) in folder Report

My .vb files are being compiled as expected and I'm loading my resource files using the <resources> sub-task of vbc.

 

My question is in regards to the Crystal Report and DataSet files.  My understanding of how things work is:

 

For DataSets, the .xsd and .xsx files serve as the source files for a DataSet.  Visual Studio runs a custom control (MSDataSetGenerator) on them and generates a vb file that is then included in the project DLL. 

 

For Crystal Reports, the .rpt file serves as the source file for a Crystal Report.  Visual Studio runs a custom control (CrystalDecisions.VSShell.CodeGen.ReportCodeGenerator) on them and generates a vb file that is then included in the project DLL. 

 

I want to be able to use NAnt to do a complete build of my project, starting from the DataSet and Crystal Report source files and resulting in a DLL library.  Is there some task to do this?  If not, is there a custom task I need to build to do this?

 

My .Build file looks like this:

<?xml version="1.0"?>
<project name="Loan.Build" default="build">
 <target name="DefineProperties">
  <property name="build.dir" value="Build"/>
  <property name="build.debug" value="true"/>
  <property name="current.build.defines" value=""/>
  <property name="assembly.net.framework.dir" value="C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322"/>
  <property name="assembly.crystal.dir" value="c:\Program Files\Common Files\Crystal Decisions\1.1\Managed"/>
  <echo message="Framework Assembly Directory= ${assembly.net.framework.dir}"/>
  <echo message="Crystal Assembly Directory= ${assembly.crystal.dir}"/>
 </target>
 <target name="build" depends="DefineProperties">
  <vbc target="library"
     define="${current.build.defines}"
     warnaserror="true"
     nowarn=""
     debug="${build.debug}"
     output="${build.dir}/bin/Loan.dll"
     doc="${build.dir}/bin/Loan.xml"
     imports="Microsoft.VisualBasic,System,System.Collections,System.Data,System.Diagnostics,System.Drawing,System.Windows.Forms">
   <sources failonempty="true">
    <includes name="**/*.vb"/>

 

    <!-- common assembly-level attributes -->
    <includes name="AssemblyInfo.vb"/>
   </sources>
   <resources basedir="">    
    <includes name="Form/*.resx"/>
   </resources>
   <references basedir="lib">
    <!--Crystal Assemblies-->
    <includes name="${assembly.crystal.dir}/CrystalDecisions.CrystalReports.Engine.dll"/>
    <includes name="${assembly.crystal.dir}/CrystalDecisions.ReportSource.dll"/>
    <includes name="${assembly.crystal.dir}/CrystalDecisions.Shared.dll"/>
    <includes name="${assembly.crystal.dir}/CrystalDecisions.Windows.Forms.dll"/>
    
    <!--.NET Framework Assemblies-->
    <includes name="${assembly.net.framework.dir}/System.dll"/>
    <includes name="${assembly.net.framework.dir}/System.Data.dll"/>
    <includes name="${assembly.net.framework.dir}/System.Design.dll"/>
    <includes name="${assembly.net.framework.dir}/System.Drawing.dll"/>
    <includes name="${assembly.net.framework.dir}/System.Web.Services.dll"/>
    <includes name="${assembly.net.framework.dir}/System.Windows.Forms.dll"/>
    <includes name="${assembly.net.framework.dir}/System.XML.dll"/>

 

    <!--Local Assemblies-->
    <includes name="*.dll"/>
   </references>
  </vbc>
 </target>
</project>

What do I need to add to this to get the desired results?

 

Thanks,

Leo Hart