FirebirdClient 2.5.0 Beta 2
I’m glad to announce Beta 2 release of FirebirdClient 2.5.0.
This release contains implementation of new Firebird 2.1 protocol,
couple of bugfixes in Entity Framework support and other bug fixes and
improvements.
Thanks SMS-Timing for support on new protocol and Entity Framework support and Vlad Khorsun for answering all my questions on new protocol.
Download on http://www.firebirdsql.org/index.php?op=files&id=netprovider.
For more information about this release visit:
http://tracker.firebirdsql.org/secure/ReleaseNote.jspa?version=10340&styleName=Text&projectId=10003
for detailed changes follow the SVN log or visit:
http://tracker.firebirdsql.org/browse/DNET?report=com.atlassian.jira.plugin.ext.subversion:subversion-project-tab



There's 9 Comments So Far
April 13th, 2009 at 16:10
Tak jsem to po delsi dobe zkusil. Moje sestava (32bit OS):- Firebird 2.1.2.18118- NET Provider 2.5.0 Beta 2- DDEX Provider for Visual Studio- Ukazkova databaze EMPLOYEE.FDBPri generovani modelu vznikne vyjimka:error 6003: An error occurred while executing the command definition. See the in ner exception for details. Dynamic SQL ErrorSQL error code = -104Token unknown – line 2, column 11. Exception of type ‘FirebirdSql.Data.Common.IscException’ was thrown.Nevim jak pripadne zalogovat to SQL, protoze provider asi zadny Trace nepodporuje.
April 13th, 2009 at 16:23
Generujes pomoci EdmGen nebo VS (je to sice stejne API, ale jine filtry)? Mas spravnou verzi v GAC?
Zkusil jsem to nyni a uplne bez problemu na stejne DB.
Trace je pouze v debug buildu.
BTW s 2.1.2 se ti spatne vygeneruji vazby resp. PK, kvuli chybe s left outer join. Musis (aspon na generovani modelu) pouzit 2.5.
April 13th, 2009 at 20:09
Aha, s 2.5 beta to na prvni pohled funguje. Jenze to je v praxi tezko pouzitelne. Pak by neskodilo to bud nekam napsat nebo vyhodit nejaky warning. Stejne tak pridat tu podporu pro Visual Studio primo do instalace.
April 13th, 2009 at 20:13
Pro deploy uz muzes pouzit i 2.1. Jen model se vygeneruje spravne jen na 2.5.DDEX zatim instalator nema (pro bezneho vyvojare by nemel byt problem udelat 3 kroky), nicmene muzes klidne prispet.
April 13th, 2009 at 20:21
Jasne, nemel. Jenze takovych drobnych opruzu je nakonec tolik, ze se na to cele clovek radsi vykasle
To logovani SQL prikazu by myslim nebylo na skodu, zvlast pro tyhle objektove frameworky, aby clovek videl co z toho leze. Predpokladam ze zadnym jinym externim nastrojem to trasovat ani nejde. Bud pomoci nejakeho TraceSwitch v konfiguraci nebo parametrem v connection stringu (tak to ma treba .NET driver pro MySQL).
April 13th, 2009 at 20:35
Aktualne je to pres System.Diagnostics, ale jak rikam, v release buildu je to vypnute.Jedine co jde pouzit na server jsou monitorovaci tabulky (2.1+) nebo Trace API (2.5+). Pak jedine nastroje tretich stran (myslim, ze IBSurgeon neco ma).
April 13th, 2009 at 20:47
Prave proto by bylo dobre, kdyby to slo necim zapnout i v Release. Samozrejme tohle by mel resit spis Entity Framework sam, jenze to je porad takova polobeta
April 13th, 2009 at 21:16
Pak jedine buildnout si FirebirdClienta sam.
Who Linked To This Post?
Share your thoughts, leave a comment!