Adding methods would be a solution, although it has several overloads, I wouldn't want to clutter the class.
On Tue, Feb 17, 2009 at 9:28 AM, Tuna Toksoz <[email protected]> wrote: > Adding another method, making current one call the other and marking > obselete? > > Or we may assume that this is not a big breaking change, can simply be done > with rename/or even find&replace? > > Tuna Toksöz > http://tunatoksoz.com > http://turkiyealt.net > http://twitter.com/tehlike > > Typos included to enhance the readers attention! > > > > > On Tue, Feb 17, 2009 at 10:23 AM, Simone Busoli > <[email protected]>wrote: > >> I'm not sure, this would break many applications. Someone? >> >> >> On Tue, Feb 17, 2009 at 2:42 AM, Rob Kitson <[email protected]>wrote: >> >>> Hey guys, >>> >>> I spent a good chunk of my afternoon trying to figure out why the version >>> of Rhino.Commons I was referencing didn't have the >>> InitializeNHibernateAndIoC in the DatabaseTestFixtureBase. Was pretty >>> relieved when I finally found the IntializeNHibernateAndIoC method and >>> realized that VisualStudio and R#er were not playing a mean joke on me. >>> Not that this is a problem that I'm bound to run into again in the >>> future, but I thought it might be helpful for future noobs, so I opened the >>> source and did a quick Rename with R#er. The patch is attached. >>> >>> -rk >>> >>> ** >>> * * >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
