-
I have a solution with the following structure:
- DomainObjects - .NET 5.0 class library without any special dependencies, contains entities. Compiled as **x86**.
- DAL (references DomainObjects) …
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…
-
It seems unacceptable that a primitive that can be accelerated (leading to ~1.5x speedup) is not.
Hence I suggest to look into how one should add assembly for field ops to make used of vectorised i…
-
As per the discussion today, it seems imperative to eventually have a `DofHandler`-like structure. This seems to be the way large finite element codes are typically done, and there is probably quite a…
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…
-
```
I have a use case where I am working solely with stored procedures. Most of
the time, the POCO properties are going to need to be renamed to adhere to C#
coding/naming standards. Much of thi…