The worst thing about WCF is all the configuration! Just because everything else sucks it doesn't mean that it's ok for us to suck too!
At least you can configure WCF programatically. Along the same lines, it would be nice for IronRuby to offer a programmatic option also (if it already does, then hooray!) On 16/01/2010, at 8:34 AM, Ryan Riley wrote: > To further the point, adding elements to your config should be a fairly > routine task, as it is also required by data access, WCF, and other > libraries. Some of those may have tooling, but you must edit the config in > some way. So I don't see this as quite an incredulous thing to ask. > > > Ryan Riley > > > On Fri, Jan 15, 2010 at 1:09 PM, Jimmy Schementi > <jimmy.scheme...@microsoft.com> wrote: > > This configuration, setting different paths etc is too much a hassle for > > developers. > > Let's go over what "configuration, setting different paths etc" actually > means: > > - When using ir.exe directly? > > Nothing, the Ruby standard library just works. > > - When embedding IronRuby inside a .NET app? > > Just telling your C# app where IronRuby's libraries are: > 1. Copy ir.exe.config into your app.config > 2. Make sure LibraryPaths still make sense. Making these full-paths is > easiest, > So just replace the ".." with "C:\IronRuby" (or wherever you extracted a > IronRuby > release to ... for example this is the LibraryPaths for a C:\IronRuby > installation: > > C:\IronRuby\lib\IronRuby;C:\IronRuby\lib\ruby\site_ruby\1.8;C:\IronRuby\lib\ruby\site_ruby;C:\IronRuby\lib\ruby\1.8 > > And that's it. So please, let me know how this could be too much hassle for > you. > Sure, embedding isn't "one-click", but don't blow it up to be more than it > really is. > Please let us know if you've found any real ship-stopping bugs. > > Note that ir.exe.config uses relative paths as we have no idea where someone > will > unzip the release to. With the MSI we can possibly generate ir.exe.config to > use > full paths, but that would be very low on our list of stuff to do for 1.0. > Also, > if we release VS integration in the future, generating the correct app.config > for embedding is also a possibility. > > However, for embedding, presumably you are going to want to put the libraries > into your application's directory, so you do really care about where the paths > are, which is why we don't somehow magically find them. > > ~Jimmy > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
