NAnt - A .NET Build Tool / Bugs / #724 Aximp does not support .NET 3.5

#724 Aximp does not support .NET 3.5

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2010-03-18

Created: 2010-03-18

Creator: D Skiles

Private: No

In the latest nightly build (2010-03-17) almost every task supports using .NET 3.5 on a 64 bit Windows 7 system. Aximp, however, fails with the following message.

Error importing ActiveX control from 'c:\windows\system32\shdocvw.dll'.
The SDK for the 'net-2.0' framework is not available or not configured.

Discussion

Ryan Boggs - 2010-03-19

Hi,

Can you please provide a sample project that we can use to test?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gert Driesen - 2010-03-19

Would need to look into this further to be sure if this applies here, but one of the problems that we need to deal with is a way to discover the installation directory of Windows SDK's that provide tooling support for a given target framework.

For .NET 1.x and 2.x, this w

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gert Driesen - 2010-03-19

I hate notebook keyboars :-)

For .NET 1.x and 2.x, this was easy as we could check for a specific registry key.
As of .NET 3.0 (and higher), MS stopped shipping a separate SDK for each .NET Framework version. Instead they included it in the Windows SDK.

For a given .NET Framework version one or more Windows SDK's may be released that contain SDK tools.

I know we had Windows SDK 6.0, 6.0a, 6.1.

Whenever a new SP for a given version of the .NET Framework is released, MS tends to release a new SDK resulting in a new installation directory that is not easily discoverable.

Sure, you can find which Windows SDKs are installed. But how can we know which .NET Framework version is targeted by that SDK. How can we avoid having to update our configuration file (NAnt.exe.config) whenever a new SP is released ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ryan Boggs - 2010-03-20

Yeah Gert, that is a problem that we should look into soon. I ran into a similar problem yesterday, in fact, when NAnt was looking for the .NET 3.5 SDK for a project I was testing.

D Skiles,
What .NET SDKs do you have installed? And do you have a sample project we can use to test?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

D Skiles - 2010-03-20

I won't be able to get you a sample project until I get back to work on Monday, but I think that the problem is with how it's discovering the Windows 7 SDK. I was able to work around it by adding a registry key to the .NET Framework node in SysWow64.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

D Skiles - 2010-03-20

RmBoggs,
I currently only have the .NET 3.5 Framework and the Windows 7 SDK.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ryan Boggs - 2010-03-20

dskiles,
Thanks for getting back. If I understand the Win7 SDK, it is referred to Windows SDK v7.0 (I know, duh). Gert, correct me if I am wrong, but NAnt is not currently setup to look for the sdk there. If that is the case, I'll submit a patch to include this in the sdk search.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ryan Boggs - 2010-07-04

Hey dskiles,
Is this still an issue? Please reply so I know whether or not to close out this ticket.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.