Hi all,
Have been sucessfully using Nant to compile c# project for month now with no issues. However I now have a need to compile a VB project, so I was hoping it would be just as simple as C# Nant build process. However. I've stumbled across the following error during the vbc compile:
Chris,
Are you sure you've imported the System namespace ?
Gert
- Original Message -
From: Chris Hill [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, July 16, 2004 11:03 AM
Subject: [nant-dev] Compiling vbproj getting a CLSCompliant error from vbc -
have
Troy Laurin wrote:
Matthew,
The new behaviour more closely follows the documentation, and as you say
this becomes consistent with handling of files... but any build files
relying on the old behaviour will of course break.
The fix is simple, to replace **/* with */**/*, but it may be hard
to
Managed to reproduce this issue by building on a different drive with
the path "Z:\cvs\nant\..."
Looks like the "**/CVS/**" pattern is matching the \cvs\ bit in the
pathname. There's an implicit rule in NAnt that the include/exclude
patterns only apply to the part of the path added after
After short consideration, I suppose the following rules apply (and
should be documented):
If a pattern is not rooted, it implicitly applies only to files and
directories gathered from non-rooted include patterns and only to
the segment of the path after the base directory segment. For
Any help with this?
Target(s) specified: self-userdoc
self-userdoc:
BUILD FAILED
INTERNAL ERROR
NDoc.Core.DocumenterException: Error reading in project file
C:\DOCUME~1\ROONEY~
1.8VL\LOCALS~1\Temp\tmpC5.tmp.
Object reference not set to an instance of an object.
---
All,
Im trying to create an MSI using the msi
task. I got the most recent nightly nant build (7/17/2004).
The build generated this exception:
System.ArgumentException:
Version conflict with ResourceManager .resources files! Expected version:
1 but got: 2
Besides the exception that
