Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. The Insider News
  4. New Firebird Data Access Layers Released...

New Firebird Data Access Layers Released...

Scheduled Pinned Locked Moved The Insider News
dotnetcsharpasp-netdatabasecom
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Steve Naidamast
    wrote on last edited by
    #1

    Using a Data Access Layer is still the most efficient form of database access, though modern ORMs definitely have their place. For those who are interested in using the Firebird Database Engine, Black Falcon Software's older 4.5 Firebird Data Access Layer has been updated to .NET Framework 4.8 and .NET Core 5.0, with both using the latest Firebird drivers available. As with the original version, both new versions come with a complete test-client and full documentation. To download either version, please got to the following link... https://blackfalconsoftware.com/firebird-data-access-layer/

    Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups