Hey Chris,
I added the additional readregistry item you emailed earlier to the
nant.exe.config file. It should be in the next nightly release that
is being uploaded now. Please test and report any other problems you
guys see.
Thanks,
Ryan
On Thu, Mar 25, 2010 at 3:24 PM, Christopher Brandt
wr
What's the rationale for inclusion in the list of reference assemblies for
each target framework? I'm looking at the NAnt.exe.config file again.
It appears to be a complete list of all the framework libraries. If it is
then the list is missing:
System.DirectoryServices.Protocols.dll
Which I beli
Actually, this is something that keeps coming up because of the way
Microsoft has been organizing the sdk directory structures since 3.0.
We have been just dealing with them as they come in so there may be
other reg keys out there that we don't know about yet.
Please keep these emails comin
Hi,
On Mar 25, 2010, at 3:14 PM, Christopher Brandt wrote:
> This is related to my previous post on Windows 7 & VS2008.
>
> After some help I realized that the target framework on my desktop
> was .Net 3.5 whereas on my build server (Windows 2003 Server) it
> was .Net 2.0. The was causing so
The problem only exists if you have a wonky version of the 6.0 SDK. Most
seemed to be named 6.0A, but on our server it was installed as just 6.0.
---
Chris.
Continuous improvement is better than delayed perfection. - Mark Twain
On Thu, Mar 25, 2010 at 3:22 PM, Bob Archer wrote:
> I use the
I use the latest nightly and it works ok. But, I explicity let the
targetframework property in the scripts.
I also use the msbuild task rather then the csc task.. but I assume it uses the
same mechanism to determine which to use.
BOb
From: Christopher Brandt [mailto:xtopher.bra...@gmail.com]
This is related to my previous post on Windows 7 & VS2008.
After some help I realized that the target framework on my desktop was .Net
3.5 whereas on my build server (Windows 2003 Server) it was .Net 2.0. The
was causing some problems between the two environment in how csc.exe was
importing includ
My Windows 7 desktop and my Windows 2003 build server have pretty similar
configurations. Most importantly, both have csc.exe in the
\Windows\Microsoft.NET\Framework\V2.0.50727 and \V3.5 folders.
How does NAnt determine which version of csc to use? Could this be the
difference between my machines,
Hello Bob,
> I'm not also sure what .Net 4.0 support means. ...
Support for .NET 4.0 means the usual Target and Runtime support, same as what
you see on the for .NET 1.0/2.0/3.0/3.5 on NAnt's homepage.
> Will I be able to move forward and set that value to net-4.0 in .90? How will
> that work?
We use git here and it has worked out incredibly well. Our integration
with NAnt and CC.NET is really tight, and like Bob said, the control
given over branching is so simple yet so powerful. I second the rec.
Stephan
-Original Message-
From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent
I saw the comment about moving away from CVS.
Might I suggest you consider moving to Git? Github is a great resource and free
for Open source projects. It makes branching/forking the project very easy.
BOb
> -Original Message-
> From: Charles Chan [mailto:cchan...@users.sourceforge.net
Wow... that's great news. I also want to thank everyone involved in this
project. It has enabled me to perform automated builds for several years now.
I reviewed the bug fixes and see a few things I reported fixed. That's good to
see.
One concern I have is that .Net 4.0 support is planned for e
12 matches
Mail list logo
