You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to remind folks that if you have a legacy .NET application that you are thinking of migrating to Oqtane, it is NOT required that you use EF Core for data access or migrations. Oqtane fully supports SQL scripts and can use alternate data access approaches such as Dapper, ADO.NET, etc... I described all of this in a blog post last year, and I even created an example module as a demonstration:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I just wanted to remind folks that if you have a legacy .NET application that you are thinking of migrating to Oqtane, it is NOT required that you use EF Core for data access or migrations. Oqtane fully supports SQL scripts and can use alternate data access approaches such as Dapper, ADO.NET, etc... I described all of this in a blog post last year, and I even created an example module as a demonstration:
https://www.oqtane.org/blog/!/67/dapper-sql-scripts
https://github.com/oqtane/Oqtane.Dapper
Beta Was this translation helpful? Give feedback.
All reactions