sqlhelper | SQL Tools | Object-Relational Mapping library

To sum up here, although the exception took place in controller, but with the code snippet provided by OP, we finally locate the error in the implement of ITerminalService.

Just using FormatterServices.GetUninitializedObject rather than Activator.CreateInstance to create instance can solve it.

your POST code is fine.

problem not in content size , but in a way you are building json payload.

you have doublequotes in content

so, using string interpolation for json building like this:

In your client, inside the AddOpenIdConnect method, you need to also define what scopes you want to have access to, like:

Oh... This is really hard to read. I will try to give you some tips for better architecture. I hope you are fine with it.

1. Why are you using so many lists? Why you don't make one list of custom madr classes with all the data like title, image, ingredient itp.
2. Why you name the type of class recyclercart instead of RecyclerCard. In Kotlin and in Java programmers have not written rule that classes should be named from big letter and in camelCase stale.
3. The other thing is that you melted together using database and uploadung data into the view processes. It is not good. It would be better to have other class like DatabaseManager or something like this, which will make the job of taking data from the database etc. If you will do that your RecyclerViewAdapter will get list of ready items in the constructor and the only responsibility of this class will be to show the data in the views. The code will be simplified and maybe the mistake will be more visible. If you want to upload children data dynamically (during scrolling) you cab, but the code for it should be places in the DatabaseManager or Helper, too. If number of data is not big- it could be better to upload it before adapter is created even and just put Map
4. I would also check the way of using SQLiteHelper. I am not sure, but something tells me that you are creating few databases in one program. It can be damgerous. Please, just check it. Remember to create database once and just connect to it few times. About this one I am not sure. I have to less time to investigate yourt code.

About my tips: checkout SOLID; you will have a lot more clear architecture.

I think I have a solution for you. It will great to return the DataTable object to PL Layer. However, if you don't want to do that then you can check my dummy code and try it. You can also check that similar problem link LINK

You are not providing enough parameters for sql.Execute.

Look closely:

• exec takes three parameters - bind, parametres (btw, typo), and query
• In the body of Execute you give it one parameter - bind
• Therefore, the result of Execute is a function that still expects the other two parameters - parametres and query
• But when you're calling sql.Execute, you're only giving it one parameter - [query], which will end up bound to parametres

Therefore, the result of calling sql.Execute [query] is yet another function, which still expects the final parameter to be provided before its body will be executed. In fact, if you pay close attention to compiler warnings, you will see that the compiler actually tells you as much:

This expression is a function value, i.e. is missing arguments. Its type is ...

To fix, provide the correct parameters. Judging by the little piece of your query that I can see, I assume that it's not supposed to have any parametres, so I'll put an empty list there:

A nuance of ADO.NET is that if the value of a parameter is null, the parameter is not added (for input purposes, at least). As such, when adding - you should check for null and use DbNull.Value instead.

You should retrieve the values of Output parameters after you have consumed all of the result sets from SqlDataAdapter (and disposed of it). Try restructuring your code such as the following: