SqlParameter and DBNull.Value - possible bug?

From: Martin Ret <MartinRet@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 14 May 2021 08:23:03 -0700

Is following behaviour by design or is it a bug?
For shure breaking change from framework 1.1.

Try under framework => 2.0
SqlParameter param = new SqlParameter("Test", DbType.Int32);
Console.WriteLine("Value: {0}, Type: {1}",param.Value, param.DbType);
param.Value = DBNull.Value;
Console.WriteLine("Value: {0}, Type: {1} --- WTF",param.Value, param.DbType);
Console.ReadLine();
.

Follow-Ups:
- Re: SqlParameter and DBNull.Value - possible bug?
  - From: Bob Barrows [MVP]

Prev by Date: Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
Next by Date: Re: SqlParameter and DBNull.Value - possible bug?
Previous by thread: Non initialized Cmd Parameter Collection via ASP vs SQL Server 200
Next by thread: Re: SqlParameter and DBNull.Value - possible bug?
Index(es):
- Date
- Thread

Relevant Pages

Re: OODesign - OPF, design pattern
... What I had in mind were very specific design patterns, ... It's under their control, for goodness ... but once I had reached a point where I could stop "tweaking" the framework to handle scenarios that I hadn't previously thought of the development time suddenly increased dramatically. ... once you zoom in even just a little, OO design reveals more layers. ...
(borland.public.delphi.non-technical)
Re: Books / Articles on Embedded SW Architecture
... and dirty patches must be done to already fixed architecture. ... decomposition, then there was a problem with the decomposition. ...</b