datalibrary | Open Source Data Library for data serialization | Serialization library

There are two problems in your code :

1. Your GetLogicalDrives method calls itself in its body, it will not be able to work with your logic, because there is no List to browse.

2. An using directive is missing in your file. To acces to Directory class and then call the GetLogicalDrivers method you must add using System.IO at the top of your file.

I hope this will help you.

this line is wrong schooltypeId = school.SchoolsSchoolTypes.Select(s => s.SchoolType.Id).ToString() you've multiple SchoolsSchoolTypes so if you want it as string replace it with the following

So many questions.

• Why do you have a private constructor?
• What is DataLayers, is this some homegrown data access library?
• Why doesn't the stored procedure allow for searching on @agentContact?
• Why load all data from the database, upon controller construction, instead of filtering on demand?

And so on. But assuming you're stuck with this approach, you've defined the wrong signature and logic for your requirements. You want to return a list instead of a single item:

You're looking for something called self.kwargs['name'], but your view won't have any such item.

Firstly, the name of the search input in your HTML is search, not name.

And secondly, self.kwargs is for elements that are captured from the URL; but this is sent as a GET form, so you should get it from the querystring: self.request.GET['search'].

Putting it together, in a slightly more idiomatic way:

First off you should remove partial from the Assignment class if you want to be able to use it in your put method.

Second you are missing the attribute.

FromBody

Specifies that a parameter or property should be bound using the request body.

When you use FromBody attribute you are specifying that the data is coming from the body of the request body and not from the request URL/URI. You cannot use this attribute with HttpGet requests, only with PUT, POST, and Delete requests. Also you can only use one FromBody attribute tag per action method in Web API (if this has changed in mvc core I could not find anything to support that).

FromRouteAttribute

Summary: Specifies that a parameter or property should be bound using route-data from the current request.

Essentially it FromRoute will look at your route parameters and extract / bind the data based on that. As the route, when called externally, is usually based on the URL. In previous version(s) of web api this is comparable to FromUri.

You are using Dapper.Contrib and your database is MS Access. Your INSERT call is generating two SQL queries. First, as you expect, to insert record. Second is behind the screen to fetch the newly generated id.

So, generated queries looks like something like this:

For what it's worth, I found this happening one a smaller file in the system and was able to figure out what going on, after painstaking research into the code and the net. Basically, the file file has numeric fields on the i-series. Somehow, the records were written to the file on the original system with null values in the numeric fields instead of numeric values. When storing the original records, I had to do this calculation:

The EF6 setup is creating a so called One-To-One Shared Primary Key Association where the PK of the dependent entity is also a FK to principal entity.

The things have changed in EF Core. It supports naturally both shared PK and FK one-to-one associations. Also optional/required are not used to determine the principal and dependent ends of the association. IsRequired is used to control if the dependent entity can exists w/o principal and applies only whith separate FK. While HasForeignKey and HasPrincipalKey are used to determine the principal and dependent ends of the association and also map the dependent FK and principal PK / Alternate Key.

With that being said, the equivalent EFC configuration is as follows:

Thanks to the pointers given in the comments above, I was able to locate where the error was stemming from, and figured out what was triggering the error. The basic answer is that this was caused by a concurrency issue. I was trying to update a MyTable object that had already been deleted in a previous call.

On my web page, I have a table of MyTable object: