Spatial types as parameters to SQLCommand objects

Question

I saw on Bob's blog that some parameter items are going to be fixed in .net 4.0
http://www.sqlskills.com/BLOGS/BOBB/post/L2S-and-EF-parameterization-problem-will-be-fixed-in-NET-40-completely.aspx

I noticed that if trying to pass parameters from C# to a stored proc using SqlCommandBuilder.DeriveParameters any parameters for Geography (probably Geometry as well) do not get assigned a known UdtTypeName.  The parameters are thought to be of type varbinary. 

The workaround is to explicity set UdtTypeName like this
_cmd.Parameters["@Geog"].UdtTypeName = "GEOGRAPHY";

It would be great if this were also fixed in .net 4.  If anyone has the environment to verify this, please post your findings.

Answer 1

I found this to be true and had to use the workaround you mentioned with Geometry data types too. Neither Geometry nor Geography are in the SqlDbType enumeration.

Answer 2

It's the same in .NET 4.0 Beta1, just tried it. Did you report it as a connect item?

Cheers,
Bob

Answer 3

Thanks for confirming.  I had not yet reported it on connect just in case it was fixed in .net 4.  I will do so.

It is now in connect at
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=464085