Solution updates, clean install and esperantus notes
I wanted to let everyone know that thanks to some pointers from ace, and some initiative on turning the error handler of, I was able to make some progress in correcting the clean install... I am not there yet, but I am pushing forward and hope to have a fix sometime this weekend. Along with that I have added some preprocessor compile that in case of DEBUG compilation turns of the global error handling, so that you WILL receive asp.net runtime errors for undraped errors. This is biennial to me debugging and others probably, but people should note ( and this should be done anyway ) do not RELEASE DEBUG dll's to your prod sites :-) even if it's the same code, just compile it as release code.
In the meantime, I am calling for a volunteer or two to help with porting a couple of features from esperantus to my sandbox solution. Basically, the language switcher code is all inside Rainbow.Framwork.Web.UI.WebControls (However it's inside the appcode dll because there are some core pages that use ESPERANTUS FOR CULTURE??????????) and all of that logic was housed inside the language switcher module. so, part of the task is to move the culture logic into a separate Rainbow.Framework.Localization or Globalization ( anyone has advice on namespace here would be appreciated, ) and then move all the methods that have to do with culture lists and logic out of the language switcher, the switcher is supposed to be only a up module that pulls from the language framework ... point being the core should not rely on the module to select languages.... for example, if users have a preferred culture stored in their profile.... you know what I mean?
Second task.... is two fold.... the language switcher must be update to use new code which should be easy enough.
In the Registration and Profile pages, there is Country and State... these also where inside of espererantus and must be ported out (I have not done this yet)... so if someone could get started on that, that would be great.
That would complete the extraction of esperantus, and a more flexible localization API base.... which we then can extend and utilizes in the content API.
If anyone would like to volunteer and help me with those issues, it would help stabilize and move closer to making this the official dev solution and soon a first release of 2.0.
Localization has alwasy been one of the key features in rainbow, and I need some help to bring it back quickly in my code base.
you can contact me at jminond at gmail dot com or send me private messages throgh here. Or better yet, we can open a thread in the forum, and maybe get a couple people working as a team to get those things done quick.