. Oracle ORM in NetcoreAfter the project was actually ported to. Netcore, it was discovered that there would be many problems, such as access to Oracle, when the problem occurred at the end of 2017 reference connection: http://blog.jobbole.com/104442/Dapper:https://g Ithub.com/phnx47/microorm.dapper.repositories. Oracle does not have a specific connection implementation in Netcore, originally planned to be implemented at the end of 2017, but not implemented, and now requires the use of the original class library System.Data.OracleClient, the class library requires an Oracle client to be installed to use 1. Use System.Data.OracleClient to install OracleClient Client 2. Then configure the system environment variable to Path 3 Restart the computer or configure the command to make the environment variable effective 4. Use OracleConnection to connect in the program Oracle has already provided the first version of the SDK, refer to the connection http://www.oracle.com/technetwork/ Topics/dotnet/downloads/odpnetcorebeta-4077982.html, you will not need to use a client-side way to connect the version of the package to a file-mode DLL reference, but the ASP. NET core does not support direct referencing. You need to publish the temporary version yourself to NuGet, then download the references, and refer to the corresponding document NuGet to publish your own Dll,nuget release method, and update it immediately.
in the. Netcore API routing rules, the routing rules are also large changes in ASP. This is followed by a detailed description, divided into the following two categories' convention-based Routing ' rules route ' Attribute Routing ' attribute routing
ASP. NET core three Oracle ORM
