Hi Damian, 

Can you please put the environment variable of your Path here. It is most 
likely that it is detecting the older .net version. I'm not sure if this 
behavior has been changed already but I seem to recall that this is happening 
in 1.4.0 You could also try changing your environment variable to have .net 4.0 
first 


HTH, 

-- 
Joe Ocaba 

----- Original Message ----- 
From: "Damian Pooley" <damian.poo...@hyro.com> 
To: npanday-users@incubator.apache.org 
Sent: Wednesday, October 12, 2011 1:44:57 PM 
Subject: aspx compilation error: found different/older .NET framework version 

Hi all, 

I am getting an a build failure during the maven-aspx-plugin compile step, 
because it has found an earlier version of the .NET framework (2) and not the 
one that the project is written with (4). The maven-compile-plugin compile uses 
the correct (4) version of .NET. 

I am using 1.4.0-incubating. 

Maven-compile-plugin messages: 
[INFO] NPANDAY-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = 
4.0, Framework Version = 4.0, Executable Paths = 
[C:\Windows\Microsoft.NET\Framework64\v4.0.30319, C:\Program Files 
(x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools] 
[INFO] NPANDAY-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = 
MICROSOFT, Assembly Name = <path.to>.dll 
[INFO] NPANDAY-068-005: Found executable path for csc: 
C:\Windows\Microsoft.NET\Framework64\v4.0.30319 

Maven-aspx-plugin messages: 
[INFO] NPANDAY-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = 
2.0.50727, Framework Version = 2.0.50727, Executable Paths = 
[C:\Windows\Microsoft.NET\Framework64\v2.0.50727, C:\Program Files 
(x86)\Microsoft SDKs\Windows\v6.0A\bin] 
[INFO] NPANDAY-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = ASP, 
Assembly Name = <path.to>.dll 
[INFO] NPANDAY-068-005: Found executable path for aspnet_compiler: 
C:\Windows\Microsoft.NET\Framework64\v2.0.50727 

Why would the .NET version detected be different? How can the aspx plugin be 
forced to use the latest version? 

Regards, 

Damian Pooley 

Reply via email to