Hi,

After upgrading from LLBLGen v4.2 Final(July 8, 2014), "Generate source code from project" caused error. Please find below the message, I'm using Firebird.

Thanks

Dextre

Input string was not in correct format.

LLBLGen Pro version 4.2. Build July 8th, 2014 -----[Core exception]-------------------- at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at SD.LLBLGen.Pro.DBDriverCore.DBDriverBase.ProduceMajorAndMinorServerVersionNumber() at SD.LLBLGen.Pro.DBDriverCore.DBDriverBase.DetermineServerVersion() at SD.LLBLGen.Pro.DBDrivers.Firebird.FirebirdDBDriver.GetTargetDescription() in c:\Myprojects\VS.NET Projects\LLBLGen Pro v4.2\Drivers\Firebird\FirebirdDBDriver.cs:line 386 at SD.LLBLGen.Pro.Gui.Controls.WizardPages.MetaDataRetrievalWizard_Step_ElementSelection.FillControls() at SD.LLBLGen.Pro.Gui.Forms.MetaDataRetrievalWizard._mainWizardControl_SelectedPageChanging(Object sender, WizardPageChangingEventArgs e) at DevExpress.XtraWizard.WizardControl.RaiseSelectedPageChanging(BaseWizardPage oldPage, BaseWizardPage newPage, Direction direction) at DevExpress.XtraWizard.WizardControl.SetSelectedPageCore(BaseWizardPage prevPage, BaseWizardPage value, Direction direction) at DevExpress.XtraWizard.WizardControl.SetNextPage() at DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m) at DevExpress.XtraEditors.BaseControl.WndProc(Message& msg) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

• Does this happen at 'Generate code' as you mention or at 'Refresh catalog'?
• What version are you upgrading from? (i.e. the latest build where this didn't happen.

Additionally, what's the version of the firebird .net provider you're using? Is that a recent one or an old one?

Hi Daelmo

First I selected the Test connection and it returned 'Test succeeded', then I selected Next Button and the problem pop-up. In version 4.1 I didn't encounter any problem.

Btw, the same config for 4.1 and 4.2

Hi Otis,

Same result for Firebird .Net provider 3.2.0 and 4.2.0.

Right now, I'm using LLBLGen 4.2 for Postgre and 4.1 for Firebird.

Thanks

Same result for Firebird .Net provider 3.2.0 and 4.2.0.

So the mentioned versions worked perfectly with LLBLGen v4.1, but v.4.2 shows the mentioned exception, correct?

Yes Walaa...

Dextre wrote:

Hi Daelmo

First I selected the Test connection and it returned 'Test succeeded', then I selected Next Button and the problem pop-up. In version 4.1 I didn't encounter any problem.

Btw, the same config for 4.1 and 4.2

Hi Otis,

Same result for Firebird .Net provider 3.2.0 and 4.2.0.

Right now, I'm using LLBLGen 4.2 for Postgre and 4.1 for Firebird. Thanks

I'll see if I can reproduce it. Seems odd though, but perhaps Jiri broke something in the version retrieval code. I'll test this on Firebird v2.5.

Btw, you mention above you use v4.1 on firebird but v4.2 on postgresql, however the error is in v4.2 and with firebird. A little confusing...

Reproduced. Looking into it.

(edit). The firebird driver returns a string like: "WI-V2.5.2.26540 Firebird 2.5", which we don't expect (we expect 2.5.2.....). And this thus fails. Looking into a way to fix this...

It's fixed (v4.2), however we were required to change both the base class in the designer and the driver code, so we can't give you a temp build of the driver here. We'll release a new build later today on the website which you should use.

New build is now available in the customer area.

Thanks Otis.

Sorry for late reply