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
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]
