Hi, I've created a nuget package of the current rhino.etl trunk.
It's pretty cool as it pulls in all the relevant boo, rhino.dsl, filehelpers and log4net dependencies that are needed automatically, from the other packages published there. I noticed that changes cause successful new builds to end up here: http://builds.hibernatingrhinos.com/builds/Rhino-ETL Is there any mileage in getting the packages automatically fed to the nuget feed at the same time? It doesn't look too hard, though I didn't manage to get the powershell-based build to work at all. Cheers, Miles -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
