linq2db.Sybase.DataAction
This package includes a T4 template to generate data models for SAP/Sybase ASE database and a reference to the linq2db and AdoNetCore.AseClient nugets. This is a fully managed provider with .NET Core support.
Deprecated Package Version
Reason: Legacy
Substituted by linq2db.Sybase package
Install
No framework information available.
README
LINQ to DB
Starting from version 4 we obsolete T4 nugets in favor of new command-line scaffolding tool: linq2db.cli. Consider migration as we don't plan to introduce new features and fixes to T4 functionality.
This nuget package contains database scaffolding T4 templates to generate POCO classes from your database.
You can read about T4 templates options here. Demonstration video could be found here.
Important
Don't use this package if you don't need database scaffolding functionality. Instead of this package, use:
- main linq2db package
- database provider nuget (see list of supported providers below)
Supported database providers
- MS Access (.NET Core-only)
- System.Data.Odbc for ODBC Access provider
- System.Data.OleDb for OLE DB Access provider
- DB2 LUW and Informix
- IBM.Data.DB.Provider: .NET Framework provider
- IBM.Data.DB2.Core: .NET Core Windows provider
- IBM.Data.DB2.Core-lnx: .NET Core Linux provider
- IBM.Data.DB2.Core-osx: .NET Core MacOS provider
- Net5.IBM.Data.Db2: .NET 5+ Windows provider
- Net5.IBM.Data.Db2-lnx: .NET 5+ Linux provider
- Net5.IBM.Data.Db2-osx: .NET 5+ MacOS provider
- Net.IBM.Data.Db2: .NET 6+ Windows provider
- Net.IBM.Data.Db2-lnx: .NET 6+ Linux provider
- Net.IBM.Data.Db2-osx: .NET 6+ MacOS provider
- for
Informixyou can also use legacy ODS or SQLiIBM.Data.Informixproviders, but we don't recommend it
- DB2 iSeries
- linq2db4iSeries: Don't reference linq2db package explicitly. This package already references supported linq2db version
- Firebird
- MySQL
- MySqlConnector (recommended)
- MySql.Data (highly discouraged, low quality provider)
- MariaDB
- MySqlConnector (recommended)
- Oracle
- Oracle.ManagedDataAccess (.NET Framework)
- Oracle.ManagedDataAccess.Core (.NET Core)
- also native legacy ODP.NET provider supported, but not recommended
- PostgreSQL
- SAP HANA 2
- System.Data.Odbc for ODBC provider
- also native ADO.NET provider could be used (Windows-only)
- SQL Server Compact Edition
System.Data.SqlServerCeprovider
- SQLite
- System.Data.SQLite.Core (recommended as it use most recent SQLite engine and provides access to SQLite functions)
- Microsoft.Data.Sqlite
- SQL Server
- Microsoft.Data.SqlClient (recommended)
- System.Data.SqlClient (legacy)
- SAP/Sybase ASE
- AdoNetCore.AseClient (recommended)
Sybase.AdoNet45.AseClientnative provider (not recommended, low quality provider)
Obsoletion Note
T4 templates obsoleted starting from Linq To DB 4.0.0 and replaced with new scaffolding utility. We still release newer versions of templates to maintain compatibility with new LinqToDB releases but don't actively develop new features for them.
There are multiple reasons for it:
- T4 templates doesn't work well outside of Visual Studio. MacOS/Linux users or users of alternate IDEs could face serious issues trying to use T4 templates.
- T4 templates executed using .NET Framework by Visual Studio, which also creates issues for non-Windows users.
- T4 host use x86 process for Visual Studio 2019- and x64 process for Visual Studio 2022+. This creates issues with native providers as they are platform-dependent (ODBC and OleDb providers, various native ADO.NET providers).
- It's very hard to maintain big code generation framework, written in T4 templates.
These are the most significant issues with T4 templates.
Changes from Previous Version
Adoption Assessment
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.