Good point about the installer. In some cases you need a little bit extra to be added to it which may warrant c# (such as the installer.) Although I'll still prefer to use the DSL even if it's wrapped in C#. The reason? The DSL scripts are generally less verbose and easier to maintain. We have an operations/scripts folder that allows us to build out many of them and invoke them quite easily from within a c# app.
I think at the end of the day it's preference and a little bit about the environment you are in. Both are supported models. Nathan Palmer On Sun, Jul 22, 2012 at 5:45 PM, Jeffrey Becker <jeffrey.a.bec...@gmail.com>wrote: > One of the great aspects of Rhino-ETL is that the C# is just as valid as > the DSL. In my case I've mostly written things in C#. My current > environment sees the idea of an "ETL Script" as a net-negative. > I currently build a command-line exe to be scheduled from the task > scheduler. Our IT administrator requires everything to be deploy-able via > an installer, which makes the exe less of a hassle. > > > On Sun, Jul 22, 2012 at 5:38 PM, Nathan Palmer <em...@nathanpalmer.com>wrote: > >> No issues with the DSL at all. I use the DSL most of the time and it's >> only when I need C# integration that I'll use C#. I prefer the idea that >> you have ETL "scripts" that can easily be invoked from a command line or >> in-process. >> >> Nathan Palmer >> >> >> On Tue, Jul 17, 2012 at 12:46 PM, Michael Gates <miketga...@gmail.com>wrote: >> >>> I'm starting to get into using Rhino-ETL and have noticed that most of >>> the examples out there use C# instead of the Boo DSL. Is the DSL in a way >>> deprecated? What are the reasons for using C#? (I can guess at some like >>> "well, I know C#", but I'm wondering if there aren't issues with using the >>> DSL to begin with) >>> >>> Thanks! >>> >>> -- >>> 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/-/cXIfRijGUrgJ. >>> To post to this group, send email to rhino-tools-dev@googlegroups.com. >>> To unsubscribe from this group, send email to >>> rhino-tools-dev+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To post to this group, send email to rhino-tools-dev@googlegroups.com. >> To unsubscribe from this group, send email to >> rhino-tools-dev+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to rhino-tools-dev@googlegroups.com. > To unsubscribe from this group, send email to > rhino-tools-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
