3.12.0 but I still get the .NET 4 warning on build in last week’s Fire. Is there something in the project or sln file that’s weird?
Btw, here’s what I get whn switching to the external compiler (the last one that shipped with a Fire distro) in case that helps. Used to be that it would build with the external compiler.
xbuild /Users/jobrien/Source/UnitOOPS/Nougat/ConsoleApplication1/ConsoleApplication1.sln /nologo /target:Rebuild /verbosity:normal /property:Configuration=Debug "/property:ElementsXbuildNougatSDKFolder=/Applications/Fire.app/Contents/Resources/Nougat SDKs" "/property:ElementsXbuildReferencePathsXMLFolder=/Applications/Fire.app/Contents/Resources/Reference Paths" /toolsversion:4.0
Build started 1/30/2015 11:55:21 AM.
__________________________________________________
Project "/Users/jobrien/Source/UnitOOPS/Nougat/ConsoleApplication1/ConsoleApplication1.sln" (Rebuild target(s)):
Target ValidateSolutionConfiguration:
Building solution configuration "Debug|AnyCPU".
Target Rebuild:
Project "/Users/jobrien/Source/UnitOOPS/Nougat/ConsoleApplication1/ConsoleApplication1/ConsoleApplication1.oxygene" (Rebuild target(s)):
Target GetTargetSDK:
: error : Error initializing task GetTargetSDKType: Could not load file or assembly 'RemObjects.Oxygene.CrossBoxClient' or one of its dependencies. The system cannot find the file specified.
File name: 'RemObjects.Oxygene.CrossBoxClient'
at System.AppDomain.Load (System.Reflection.AssemblyName assemblyRef, System.Security.Policy.Evidence assemblySecurity) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.AppDomain:Load (System.Reflection.AssemblyName,System.Security.Policy.Evidence)
at System.AppDomain.Load (System.Reflection.AssemblyName assemblyRef) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.AppDomain:Load (System.Reflection.AssemblyName)
at System.Reflection.Assembly.Load (System.Reflection.AssemblyName assemblyRef) [0x00000] in <filename unknown>:0
at Microsoft.Build.BuildEngine.TaskDatabase.RegisterTask (System.String classname, Mono.XBuild.Framework.AssemblyLoadInfo assemblyLoadInfo) [0x00000] in <filename unknown>:0
at Microsoft.Build.BuildEngine.UsingTask.Load (Microsoft.Build.BuildEngine.TaskDatabase db) [0x00000] in <filename unknown>:0
at Microsoft.Build.BuildEngine.TaskDatabase.GetTypeFromClassName (System.String classname) [0x00000] in <filename unknown>:0
at Microsoft.Build.BuildEngine.BuildTask.get_Type () [0x00000] in <filename unknown>:0
at Microsoft.Build.BuildEngine.BuildTask.InitializeTask () [0x00000] in <filename unknown>:0
at Microsoft.Build.BuildEngine.BuildTask.Execute () [0x00000] in <filename unknown>:0
Build FAILED.
Errors:
/Users/jobrien/Source/UnitOOPS/Nougat/ConsoleApplication1/ConsoleApplication1.sln (Rebuild) ->
(Rebuild target) ->
/Users/jobrien/Source/UnitOOPS/Nougat/ConsoleApplication1/ConsoleApplication1/ConsoleApplication1.oxygene (Rebuild) ->
/Library/Frameworks/Mono.framework/External/xbuild/RemObjects Software/Oxygene/RemObjects.Oxygene.Nougat.targets (GetTargetSDK target) ->
: error : Error initializing task GetTargetSDKType: Could not load file or assembly 'RemObjects.Oxygene.CrossBoxClient' or one of its dependencies. The system cannot find the file specified.
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:00.8325110
Also, I looked inside /Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/Microsoft.Common.targets
and it certainly seems to be putting v4.0 for Version. Should that be 4.5?
/Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/Microsoft.Common.targets: warning : Unable to find framework corresponding to the target framework moniker '.NETFramework,Version=v4.0'. Framework assembly references will be resolved from the GAC, which might not be the intended behavior.
Shouldn’t matter, as it shouldn’t be needing any version of the .NET SDK for building a Cocoa app… I’ll need to investigate kore next week.
FYI, still get the warning with 1701 and the project I already sent you.
If it helps, I always see this (just ignored it as I know I’m not using it), and it happens even if you just create a master/detail (universal) app from the new project wizard.
bugs://71055 got closed with status fixed.