Ok, that makes sense. I was updating the log4net build files to support 3.0 and
3.5. log4net's build file attempt to build based on the user's current
framework. If someone only has 3.0 installed will the build fail because NAnt
doesn't support 3.0? I suspect it will because when I launched the
I think my point was, you don't specify net-3.0 to nant, nor do you need
to. All of the 3.0 DLL's should be found in the GAC without problem.
BOb
-Original Message-
From: Paul LeBlanc [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26, 2008 4:08 PM
To: Bob Archer; Ron Grabowski; nant-
Yes... System is red bits so its version didn't change for .Net 3.5...
.Net 3.5 is new compiler, new msbuild and additional framework DLLs like
System.Data.Linq will be version 3.5 while System.Workflow.Activites is
3.0 since it was added with the 3.0 framework.
Daniel Moth has some excellent sc
You're correct Paul, the C:\Windows\Microsoft.NET\Framework\v3.0 directory
doesn't have a csc.exe in it like the v2.0 and v3.5 folders do. That makes
sense since v3.0 uses the v2.0 CLR.
My underlying issue is that I'm trying to make a v3.5 compile of an assembly. I
believe I've set this propert
Ron,
We currently do not provide support for targeting .NET Framework 3.0,
although this would be easy to fix.
Gert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ron Grabowski
Sent: dinsdag 26 februari 2008 21:43
To: nant-users@lists.sourceforge.net
S
Bob, where do you think his 3.0 directory (without NetFX3) came from?
I have seen what appears (at top level) to be valid framework roots only
to find that they are mostly empty. I never figured out how those roots
got there unless somebody uninstalled the framework.
P
-Original Message-
.Net 2.0 and .Net 3.0 use the same compilers and msbuild exe. All you
should need is the .NetFX 3.0 installed on your build machine and you
should be good to go.
We didn't change our builds at all when we went to .Net 3.0.
BOb
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL P
Ron, You can inject this into your run target to check programatically:
You can visually look into that 3.0 directory too, and I would bet that
there's nothing there. Why does the top level directory exist then?
Good question. Maybe somebody uninstalled the framework or s
When I run the following command:
nant -t:net-3.0
I get this output:
NAnt 0.86 (Build 0.86.2898.0; beta1; 12/8/2007)
Copyright (C) 2001-2007 Gerry Shaw
http://nant.sourceforge.net
Invalid framework 'net-3.0' specified.
Possible values include:
net-2.0 (Microsoft .NET Framework 2.0)
net
