Title: Message
furthermore, because <solution> does call csc.exe directly, the csc.exe of interest should be the 1st one on the PATH.  those struggling with this over the past week have said they had to change the order in the PATH environment variable, so that .net framework 1.1 is found first.  that was the fix of the <solution> problem (!) in the end.
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erv Walter
Sent: Tuesday, June 17, 2003 22:44
To: Carlo Poli; [EMAIL PROTECTED]
Subject: RE: [Nant-users] Solution incorrectly compiled against .NET version 1.0 (bug?)

The <solution> task does not seem to respect the defaultframework setting.  Several messages to this list in the past couple days suggested that the <solution> task works by calling the csc.exe directly and it appears to choose the wrong one in the case you’re describing.  I think someone suggested that you could force nant to run under the 1.1 framework which would force the <solution> task to call the correct csc.exe.

 


From: Carlo Poli [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2003 10:55 AM
To: [EMAIL PROTECTED]

 

Hi,

I'm trying to figure out the following problem. I'm using the new <solution> task from the daily build of 20030605 to build a project that's perfectly building in Visual Studio on the same machine. I'm using Visual Studio.NET 2003 and the .NET Framework 1.1 on Windows 2000 Server. The .NET Framework 1.0 is also installed. The following error is raised:

Using NAnt I'm getting the following error: error CS0117: 'System.Web.UI.WebControls.DropDownList' does not contain a definition for 'SelectedValue'.

The SelectedValue property has been added in the .NET1.1, so I'm thinking NAnt is using .NET1.0 to compile against. But I don't understand how.

I changed nant.exe.config in the following ways:

1) I changed the default framework to 1.1 (via <nantsettings defaultframework="net-1.1">)
2) I deleted the framework 1.0 definition (just to be sure ;-)
3) I changed the framework 1.1 definition to point explicitly to the folder C:\WINNT\Microsoft.NET\Framework\v1.1.4322 instead of a registry key

All to no avail. Does anyone have any clue why the solution task behaves this way, assumed that it indeed uses .NET 1.0?

Thanx in advance,

 

Carlo Poli
Macaw

Reply via email to