Windows Forms designer error since VS 17.5 update

Question

Windows Forms designer error since VS 17.5 update

cstauffer 10

Since updating to 17.5.0 (as well as 17.5.1) I am unable to open winforms design files due to the following error:

Unable to cast object of type 'System.Data.SqlClient.SqlCommand' to type
'Microsoft.Data.SqlClient.SqlCommand'.

This only happens for forms using components from the System.Data.SqlClient namespace, such as SqlDataAdapter, SqlCommand, SqlConnection, etc. There really isn't any additional info provided in Visual Studio aside from that error message. The projects all target .NET Framework 4.8.

Nothing has changed with the code, and applications still compile and run as they did prior to the update. I'm not sure where to look to see what is causing this issue. The projects do not have a reference to Microsoft.Data.SqlClient in them so I'm not sure why it's trying to cast stuff to types in that assembly.

Jack J Jun 21,976 Reputation points Microsoft Vendor

2023-03-08T05:54:24.9466667+00:00
@cstauffer, Welcome to Microsoft Q&A, the error often means that there two different namespaces have the same class name. I recommend that you could use the class with the namespace like the following code:

System.Data.SqlClient.SqlConnection connection = new System.Data.SqlClient.SqlConnection(); System.Data.SqlClient.SqlCommand cmd = new System.Data.SqlClient.SqlCommand(); etc.
James Taylor 6 Reputation points

2023-03-08T06:59:04.74+00:00

I have the same issue, have submitted a bug report:

https://developercommunity.visualstudio.com/t/Windows-Forms-designer-since-VS-175:-U/10303272
Lionelmesi 0 Reputation points

2023-03-08T07:02:00.79+00:00

Me too
Jack J Jun 21,976 Reputation points Microsoft Vendor

2023-03-08T09:03:30.6366667+00:00

@cstauffer, I also reproduced the problem. I also recommend that you could ask the Question in DC or follow other's submitted question.
Andy 0 Reputation points

2023-03-14T13:46:00.49+00:00

In my case, it appears that the old VS toolbox items for SqlCommand, SqlDataAdapter, etc. no longer appear to compile properly as part of the VS designer rendering code. I had to take them out of the .designer files and move the initialization code into the _Load event for the form. Once I did that, the designer would render the form again without errors.

Initially, the issue showed up as an error that it wouldn't render because it couldn't load Microsoft.Data.SqlClient version 3.0.0.0 (a DLL that I didn't use in my .NET 4.8 code, since that's something for .NET Core 3.0 or later), in case anyone is having that problem too.

Jack J Jun 21,976 Reputation points Microsoft Vendor

2023-03-08T05:54:24.9466667+00:00

@cstauffer, Welcome to Microsoft Q&A, the error often means that there two different namespaces have the same class name. I recommend that you could use the class with the namespace like the following code:

System.Data.SqlClient.SqlConnection connection = new System.Data.SqlClient.SqlConnection(); System.Data.SqlClient.SqlCommand cmd = new System.Data.SqlClient.SqlCommand(); etc.
James Taylor 6 Reputation points

2023-03-08T06:59:04.74+00:00

I have the same issue, have submitted a bug report:

https://developercommunity.visualstudio.com/t/Windows-Forms-designer-since-VS-175:-U/10303272
Lionelmesi 0 Reputation points

2023-03-08T07:02:00.79+00:00

Me too
Jack J Jun 21,976 Reputation points Microsoft Vendor

2023-03-08T09:03:30.6366667+00:00

@cstauffer, I also reproduced the problem. I also recommend that you could ask the Question in DC or follow other's submitted question.
Andy 0 Reputation points

2023-03-14T13:46:00.49+00:00

In my case, it appears that the old VS toolbox items for SqlCommand, SqlDataAdapter, etc. no longer appear to compile properly as part of the VS designer rendering code. I had to take them out of the .designer files and move the initialization code into the _Load event for the form. Once I did that, the designer would render the form again without errors.

Initially, the issue showed up as an error that it wouldn't render because it couldn't load Microsoft.Data.SqlClient version 3.0.0.0 (a DLL that I didn't use in my .NET 4.8 code, since that's something for .NET Core 3.0 or later), in case anyone is having that problem too.

Answer 1

Even a fresh new project "Windows Forms" has the same problem.

When drag/drop a data component form the Toolbox like SqlCommand, SqlDataAdapter the message appears:

Failed to create component "SqlCommand"... System.InvalidCastException: Unable to cast object of type 'System.Data.SqlClient.SqlCommand' to type 'Microsoft.Data.SqlClient.Sqlcommand'

Windows Forms designer error since VS 17.5 update

1 answer

Activity