Xavier

The problem persists after switching to net452. I switched C:\Git\github\xavier\super-funicular\SuperFuncular\SuperFuncular\Matrix\SparseColumnMatrix.cs to use mstest and profiling works.

I pushed out my changes to switch to net452 and “Profile Test” on SubStringPerformanceTest fails with the same error “[10/4/2017 6:57:57 PM Error] Illegal characters in path.” I can’t see...

One option could be to wrap the DbDataReader, something like ``` public static DbDataReader ExecuteReader(this Database database, object storedProcedure) { if (storedProcedure == null) throw new ArgumentNullException("storedProcedure"); var info =...

That is true. I have been thinking if we should have a companion library with commonly needed items like Email, RequiredString, Error, etc. Here we could have an `ErrorList` so...

I figured out the problem with the Generic Error so now we have to option of only keeping the generic version in this library.

> params T [] errors Added.

@vkhorikov I hope your new course will have a solution to this error problem that is rfc7807 compliant. https://datatracker.ietf.org/doc/html/rfc7807 Using the ProblemDetails Class in ASP.NET Core Web API https://code-maze.com/using-the-problemdetails-class-in-asp-net-core-web-api/ https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.problemdetails?view=aspnetcore-6.0

I used Envelope when there was no standard. Now that HTTP API has defined RFC7807, we have to follow it. ProblemDetails is RFC7807 compliant. We also want failure to be...

Having to create a ValidationAttribute for each value object seems like extra work. I want to be lazier :) `public sealed class EmailAttribute : ValidationAttribute` I wonder if we can...

> Yeah, that's the default approach in many projects. I don't like it because it goes against the principles of domain model encapsulation. How does it break domain model encapsulation?...