SmartDate and dates earlier than 1753

[Chicagoan2016]

In one of our existing applications, an error has been reported for dates earlier than 1753. In SQL Server we are storing the date as datetime2(3) and from our Csla code we are sending the value as the DBValue of a SmartDate property.
We are on Sql server 2022 and we are using stored procs with ADO.NET.
Any ideas?
Kind regards

[rockfordlhotka]

Can you identify where the value is being (I assume) corrupted? In code or in the database? Or in the DAL?

[hurcane]

Check if your code is somehow using a parameter value that is datetime instead of datetime2. Datetime has a range starting with 1753-01-01. SQL will successfully convert a datetime parameter into a datetime2 column, but the parameter type will still have the restrictions of the datetime type.

[Chicagoan2016]

This project is using 'ConnectionManager' from Csla.Data.
and we are adding parameters to the command object as

  cm.Parameters.AddWithValue("@MyDate", MyDate.DBValue);

Well, the above code was creating a SQL parameter of datetime (as opposed to datetime2)
When I changed the code to something like

       SqlParameter mydate = new SqlParameter
         { 
              ParameterName = "@MyDate", 
              DbType = DbType.DateTime2, 
              Value = MyDate.DBValue, 
         };

It's working!

Is it because Csla.Data is using System.Data.SqlClient?
or for cases like this we have to use the longer version of declaring Sql parameters?
I liked the shorter version : )

[hurcane]

Not related to CSLA, but we have banned the use of AddWithValue in our company. Dan Guzman wrote about the problems with using AddWithValue. Convenience comes at a cost, and this method is one of those values that has a pretty high cost.

[Chicagoan2016]

@hurcane Thank you.
How do you folks generate ADO.NET Dal code? I hate writing that part of the code. It's error-prone and tedious.
Regards