Bugs item #2972647, was opened at 2010-03-18 15:35
Message generated for change (Comment added) made by dskiles
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2972647&group_id=31650
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: D Skiles (dskiles)
Assigned to: Nobody/Anonymous (nobody)
Summary: Aximp does not support .NET 3.5
Initial Comment:
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.
----------------------------------------------------------------------
>Comment By: D Skiles (dskiles)
Date: 2010-03-20 20:58
Message:
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.
----------------------------------------------------------------------
Comment By: Ryan Boggs (rmboggs)
Date: 2010-03-20 17:31
Message:
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?
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2010-03-19 07:44
Message:
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 ?
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2010-03-19 07:37
Message:
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
----------------------------------------------------------------------
Comment By: Ryan Boggs (rmboggs)
Date: 2010-03-19 02:48
Message:
Hi,
Can you please provide a sample project that we can use to test?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2972647&group_id=31650
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
