Bugs item #1902098, was opened at 2008-02-26 13:27
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1902098&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: Framework support
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: André Næss (hisnessness)
Assigned to: Nobody/Anonymous (nobody)
Summary: 3.5 Support failing on machine without VS2008 installed

Initial Comment:
I have a build server on which I'm trying to use the latest 0.86-beta1 release. 
Trying to build my solution gave me the following error:

 [property] Target framework changed to "Microsoft .NET framework 3.5".

BUILD FAILED

INTERNAL ERROR

System.NullReferenceException: Object reference not set to an instance of an 
object.
   at NAnt.Core.FrameworkInfo.get_Version()
   at NAnt.Core.Project.UpdateTargetFrameworkProperties()
   at NAnt.Core.Tasks.PropertyTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Project.InitializeProjectDocument(XmlDocument doc)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()

Please send bug report to [EMAIL PROTECTED]

I found a fairly simple fix, in the nant.exe.config, I changed the reading of 
the sdkInstallRoot registry key (in the framework 3.5 node) to:

<readregistry
  property="sdkInstallRoot"
  key="SOFTWARE\Microsoft\MicrosoftSDKs\Windows\v6.0A\InstallationFolder"
  hive="LocalMachine"
  failonerror="false" />

And the problem was solved.

Now, I'm using TeamCity as the CI-solution on this server, and when setting it 
up I had some issues with not being able to run builds at all. The server was 
complaining about a missing "al.exe". To get around this I copied the contents 
of the v6.0A SDK folder from my machine (which has VS2008 installed) to the 
build server. I also manually set up the above registry entry.

I'm not really sure where this problem is rooted. Is it simply me that haven't 
installed all the necessary stuff on my build server (I don't see Visual Studio 
as necessary stuff!), or is there something wrong with the .NET 3.5 framework 
installer. Or should NAnt use a different registry key?

----------------------------------------------------------------------

>Comment By: Gert Driesen (drieseng)
Date: 2008-02-26 18:06

Message:
Logged In: YES 
user_id=707851
Originator: NO

Can you try using a recent nightly build of NAnt (without your
NAnt.exe.config modifications), and report back whether this fixes the
issue for you?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1902098&group_id=31650

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to