I think I would still prefer NAnt because it is cross-platform and open-source, but
found this little blurb interesting. I wonder if it is in the preview stuff being
passed out at the PDC this week? I guess I'll have to order up my copy and see (I get
it as part of my companies solution provid
NAnt code can only do what the machine administrator allows because code
access security is checked by the CLR against the framework no matter
what you do. The only reason we've never run into it is that with the
default .NET configuration assemblies on the local machine are fully
trusted and can
That's correct behavior that also happens when compiling from VS.NET; referenced DLLs
get copied to the executable folder. You can change this behavior from VS.NET if you
go to the properties of the reference and set copy local to false. Unless you are
putting probing directives into your conf
sproj";
path="c:\inetpub\wwwroot\TestJDP\TestJDP.csproj"/>
http://localhost/OaiLicense/OaiLicense.csproj";
path="c:\inetpub\wwwroot\OaiLicense\OaiLicense.csproj"/>
-
Tom Cabanski, President
Objective Advantage,
For c-sharp, get the nowarn settings from the project file and pass on to the
compiler. The patch is inline below my signature.
Thanks in advance for posting it.
-
Tom Cabanski, President
Objective Advantage, Inc.
http://www.oai.cc
Phone: +1-281-348-2517x15
Solution task sometimes puts two dots in resource names where there should only be
one. This patch fixes the problem.
Can someone apply it for me?
The patch is inline below my signature.
Thanks
-
Tom Cabanski, President
Objective Advantage, Inc.
http
t for me?
Thanks
-----
Tom Cabanski, President
Objective Advantage, Inc.
http://www.oai.cc <http://www.oai.cc>
Phone: +1-281-348-2517x15
cvs diff (in directory C:\cvsroot\nant\src\NAnt.VSNet\)
cvs server: Diffing .
Index: NAnt.V
Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 16, 2003 4:41 AM
To: Tom Cabanski; [EMAIL PROTECTED]
Hi Tom,
I'll look into committing your patch later today.
I'll probable change your WebMap class to be a strongly typed
collection,
and remove your WebMapAttribute class as
I've cleaned up a variety of little bugs in the solution task as follows:
Leaks temp files under some circumstances (e.g. read-only files cannot be deleted).
Fixed.
Define settings are not read from project file (e.g. TRACE;DEBUG). Fixed.
Resource compiles blow up under some circumstances beca
A couple weeks ago I submitted a patch that added webmap to
the solution task and fixed a couple of bugs including the issue in Resource.cs
that made resource compilations failed. I just finished getting latest from
the anonymous source forge and none of this has been applied. Should I be
ugh my religion has always
been braces under the if :-) ). Was there anything else that did not
fit the guidelines?
-
TFC
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 10:50 PM
To: Tom Cabanski
Cc: [
eanly encapsulated by the WebMap class, I may leave it alone.
-----
Tom Cabanski, President
Objective Advantage, Inc.
http://www.oai.cc
Phone: +1-281-348-2517x15
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 12:18
way. I am planning to contribute a bit more time next week so I
can look at it then if nobody picks it up in the interim.
I'll be interested to see if my first contribution to this project can
be integrated successfully as well :-).
Thanks
-----
Tom Cab
I've attached the diff generated by WinCVS for the NAnt.VSNet folder. I have also
pasted it below if that is better. I've also attached two new files, which I added to
the proper folders under the project - WebMap.cs (types) and WebMapAttribute.cs
(attributes).
Per Matthew's suggestion, the w
source-controlled project and the source was not checked
out (i.e. was read-only). My new code wraps things in a try...finally
and fixes up read-only attributes before deleting.
I will look at the webmap element thing this morning.
Thanks
-
Tom Cabanski
applications
that we only want to build as part of the release and this was a handy way to
set it all up.
My changes are restricted to the NAnt.VSNet project.
How do I go about contributing all of this?
Thanks
-
Tom Cabanski, President
Objective
applications that we only want to build as part of the release and this was a
handy way to set it all up.
My changes are restricted to the NAnt.VSNet project.
How do I go about contributing all of this?
Thanks
-
Tom Cabanski, President
Objective
17 matches
Mail list logo
