NuGet -> Rhino-Etl-Cmd.1.1.1.0 depends on Boo.Lang.Useful

[Kirk Erickson]

Installed the Rhino-Etl-Cmd.1.1.1.0  nuget package and its missing Boo.Lang.Useful.  Needs to be of type .net 2.0.

I can find the  Boo.Lang.Useful.dll in the shared libs of ayende and hibernating rhino.

Is this a know issue?  

Thanks

[Nathan Palmer]

It is in here: https://github.com/hibernating-rhinos/rhino-etl/tree/master/SharedLibs/Boo

I haven't heard the issue reported before. Possible that not many people are using the Cmd Nuget package and are instead downloading the zip build from builds.hibernatingrhinos.com

Nathan

--
You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/Yqq_NMViYhYJ.
To post to this group, send email to rhino-t...@googlegroups.com.
To unsubscribe from this group, send email to rhino-tools-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.

[Miles Waller]

Hi,

From the build script, the package lists it's dependencies as Boo >=
0.9.4, but it should also list Boo.Lang.Useful >= 0.9.4 as otherwise,
as you spotted, the dependency won't be pulled in.

Miles

[Kirk Erickson]

Thanks to you and miles for such fast replies.

Trying to get the cmd project to build as a .net 2.0 project.  When manually adding references to the boo.lang.*   

Warning 5 The primary reference "Boo.Lang.Parser" could not be resolved because it has an indirect dependency on the framework assembly "System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "Boo.Lang.Parser" or retarget your application to a framework version which contains "System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089". cdb.etl.cmd

ILSpy says that boo.lang.compiler does ref system.core 3.5.

The only reason I'm trying is that I'm loading a .net 2.0 dll that that really crashes badly when loaded with a mix of .net frameworks.  That is my best guess at this point.

Kirk