Skip to main content

Return to Question

remove deprecated tag
Source Link
Brian Tompsett - 汤莱恩
Brian Tompsett - 汤莱恩
  • 5.9k
  • 72
  • 63
  • 135

Creating a .NET Core web apiAPOI that has a route access to an existing Database

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. How do I make an web apiAPI that only expose or has one route to expose the table in a specific database using Entity Framework that no need data migration?

Creating a .NET Core web api that has a route access to an existing Database

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. How do I make an web api that only expose or has one route to expose the table in a specific database using Entity Framework that no need data migration?

Creating a .NET Core web APOI that has a route access to an existing Database

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. How do I make an web API that only expose or has one route to expose the table in a specific database using Entity Framework that no need data migration?

Post Closed as "Needs details or clarity" by ekad, Burak Serdar, mpromonet
added 3 characters in body
Source Link
Ping
Ping
  • 41
  • 6

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. Is there a documentation/tutorials or sample codeHow do I make an web api that only expose or has one route to expose the table in a specific database using Entity Framework that no need data migration?

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. Is there a documentation/tutorials or sample code that only expose or has one route to expose the table in a specific database using Entity Framework?

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. How do I make an web api that only expose or has one route to expose the table in a specific database using Entity Framework that no need data migration?

Source Link
Ping
Ping
  • 41
  • 6

Creating a .NET Core web api that has a route access to an existing Database

Currently I am reading some documentations on creating web API using the Database first approach. I noticed that most of the tutorials migrate their table on their application. Is there a documentation/tutorials or sample code that only expose or has one route to expose the table in a specific database using Entity Framework?