Hello

After some time I'm trying to restart an old project of mine.

So I restored the DB from backup - after the first warnings I completely scripted it with SSMS and created it new with this script, but the warnings still show.

I can create a new LLBLGen-project (LLBL 5.5.3, MS-SQL, adapter, LLBLGen-Framework) just fine. But the next sync then complains that the types SqlHierarchyId and SqlGeometry can't be found (see complete errors attached at bottom)...

I don't use these types in my DB, that I am pretty sure of. Maybe there is some setting switched the wrong way?

OTOH the computer was installed just a few weeks ago and this is my first .NET-project on it. So there might also be a missing library.

As far as I can see I can generate code without additional problems, but I don't like warnings in read text, so I'd like to resolve these anyway

Thanks for any tips Juergen

Error: 'Exception caught while instantiating UDT type 'Microsoft.SqlServer.Types.SqlHierarchyId' from assembly 'Microsoft.SqlServer.Types.SqlHierarchyId, Microsoft.SqlServer.Types, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91': Couldn't find type: 'Microsoft.SqlServer.Types.SqlHierarchyId' using type description: 'Microsoft.SqlServer.Types.SqlHierarchyId, Microsoft.SqlServer.Types, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'. Type skipped.' Error: 'Exception caught while instantiating UDT type 'Microsoft.SqlServer.Types.SqlGeometry' from assembly 'Microsoft.SqlServer.Types.SqlGeometry, Microsoft.SqlServer.Types, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91': Couldn't find type: 'Microsoft.SqlServer.Types.SqlGeometry' using type description: 'Microsoft.SqlServer.Types.SqlGeometry, Microsoft.SqlServer.Types, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'. Type skipped.' Error: 'Exception caught while instantiating UDT type 'Microsoft.SqlServer.Types.SqlGeography' from assembly 'Microsoft.SqlServer.Types.SqlGeography, Microsoft.SqlServer.Types, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91': Couldn't find type: 'Microsoft.SqlServer.Types.SqlGeography' using type description: 'Microsoft.SqlServer.Types.SqlGeography, Microsoft.SqlServer.Types, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'. Type skipped.'

You can find all about this error here: http://www.llblgen.com/Documentation/5.2/Designer/How%20To/WorkWithSpatialTypes.htm#how-to-work-with-spatial-types

Also it was discussed in the following thread: http://llblgen.com/TinyForum/Messages.aspx?ThreadID=23953

for the record, in the upcoming v5.6 we fixed this for good by using internal types for these 2 sql server types in the designer so users won't see this error ever again

Otis wrote:

for the record, in the upcoming v5.6 we fixed this for good by using internal types for these 2 sql server types in the designer so users won't see this error ever again

I am still retrieving this error in 5.6 beta?

Edit: Ran fine in visual studio extension, however, it didn't seem like much happened (no entity mapping or anything)

We'll look into it.

(Edit) The exception shouldn't happen anymore, but it apparently still does. We didn't see this as the test box has the sqlserver types dll in the gac. We'll correct this and try to solve this properly

The error is reported in the log right? This isn't fatal, it's just something that you can ignore for now. However this should be a smooth conversion so we'll add extra code to have these errors not pop up anymore (as the geometry/geography types have to be converted anyway).

Otis wrote:

The error is reported in the log right? This isn't fatal, it's just something that you can ignore for now. However this should be a smooth conversion so we'll add extra code to have these errors not pop up anymore (as the geometry/geography types have to be converted anyway).

Yeah, it was happening in the log. I switched to just using the Visual Studio extension partially because we want to integrate it in with our solution anyways. Which doesn't prompt with this error. Thank you.

Strange that the vs extension doesn't give the same error, as the designer instance is the same code

Anyway, we've correct this for the next build of v5.6