Sql Server 2005 User Defined Types and the “File or assembly name not found” exception.

“File or assembly name ‘<udtname>’, Version=1.2.0.0, Culture=neutral, PublicKeyToken=389619d4c1235f8a’, or one of its dependencies, was not found.” If you have started using Sql Server 2005 User Defined Types it is likely that you have run into the exception above. Why is this happening? The short answer is that Fusion has not been able to find your…

0

Format=UserDefined UDTs in Sql Server 2005

Today I am talking about Format=UserDefined User Defined Types (UDTs). Format=Native UDTs are leaner, meaner and faster but only support blittable types as fields (no Strings!). UserDefined UDTs support any field type since they require the user to implement the UDT serialization themselves (in Native UDT the server does all the work). This sounds scary,…

2

Getting started with Sql Server 2005 User Defined Types (UDTs)

I have really tried to start with the simplest possible UDT I could come up with. As you can see, the simplest UDT is still quite a handful, and this is still not a complete example.   using System; using System.Data.Sql; // Required by SqlUserDefinedType . using System.Data.SqlTypes; // Required by INullable.    [SqlUserDefinedType(Format.Native)] public…

7

Whidbey ADO.NET 2.0 User Defined Types (UDTs) and Visual Studio

User Defined Types are a complicated feature, but it is hard to tell when you are using Visual Studio. All you need to do is create a Database project, connect to a Sql Server 2005 server, add a User Defined Type to your project and then click on Deploy. Magic, you are done. As is…

5

Whidbey ADO.NET 2.0 User Defined Types (UDTs) with Sql Server 2005

You can now create your own objects in managed code and install them into Sql Server 2005 as data types!   I am going to spend the next week blogging about the new Sql Server 2005 User Defined Types (UDTs). This is a very powerful feature that allows you to define new data types for…

4