I am looking for someone to implement a history logger in DotNet Core 3.0 (Preview 5).
It should use Asp.Net Core WebApi template to implement 1 Controller which will receive the data to be logged. It should operate against SQL Serevr 2017 with Entity Framework Core 3.0.
I would like to have a Service Layer which implements EF (code first) with all database functionality (dependency injected, with Service Layer interface, in the Controller).
What needs to be logged in the History Database:
- Id (guid)
- Microservice (enum)
- Node (string)
- Module (string)
- Layer (enum)
- Classification (enum)
- Timestamp (datetime2 (5))
- Message (string)
Develop a class which can be added to the Service Collection of an existing Asp.Net Core application (either MVC or WebApi), in ConfigureServices, which subsequently reads its connection data from [login to view URL] and configures itself to connect to the History Server.
Something like :
[login to view URL]<TConfig>; //where TConfig is the configuration object to be retrieved from [login to view URL] section. AddHistoryRecording is thus an Extension method (where you could read the configuration data from [login to view URL]).
** There should be NO REFERENCE to the history server. **
There should be a dependendency injectable interface, which could be injected anywhere in the application, to invoke a HistoryRecord method, which calls the WebApi to save the history request to the database.
The solution also should have a mechanism to switch on and switch off the logging in runtime, so that in the case of switched off, all calls made to the HistoryRecord method will be ignored and thus not do anything.
- Visual Studio 2019 Solution with
- Asp.Net Core 3.0 Preview 5 project which implements the Api layer of the server part
- DotNet Core 3.0 Preview 5 Class Library project which implements the Service Layer of the server part
- Visual Studio 2019 Solution with:
- DotNet Core Class Library which implements the client part which consumes the History Server
This needs to have the ConfigreServices extension method to configure itself.
It needs to expose an interface + a class to call the History Server.
And it needs to expose the structure of the Entoty to be saved.
- AspNet Core MVC or WebApi which implements the client part which consumes the History Server
MAXIMUM BUDGET: USD 50
Please place your bids.
7 freelancers are bidding on average $47 for this job
Good afternoon I briefly read what was requested in the project, I have 4 years of experience in .net and I will gladly carry out the work if you choose me. Thank you.
HELLO I CAN START RIGHT NOW - I AM EXPERT IN and I BET YOU CANNOT FIND BETTER FREELANCER THAN ME ... pLEASE MESSEGE ME AND LETS DISCUSS THE THINGS THANKSPlease Reply