I also use the two assembly info file solution and it works great. I
keep all of the project specific info in "AssemblyInfo.cs" and the
shared info in "CommonAssemblyInfo.cs".
For example, the common file looks like:
using System.Reflection;
using System.Runtime.CompilerServices;
using Syst
I have an nant script which contains the following statements
(fragment):
When the script runs, it successfully checks out the file, but leaves it
in a read only state.
Log fragment:
NAnt 0.85 (Build 0.85.2478.0; release; 10/14/2006)
Copyright (C) 2001
Or more simply, add use the resultproperty and failonerror attributes of
to get the result code and behave appropriately.
See http://nant.sourceforge.net/nightly/latest/help/tasks/exec.html
- Tony
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Roger
Li
Title: task - Fails on VC++ project (vcproj)
This is probably not an NANT issue as
there are a whole reange of errors associated with the message "Could not access 'CDO Message' object"
I had
similar problem recently at a web site belonging to a client. (I was directly
calling the .Net "sys
