Hi,

I recently took over application management of a BizTalk application which promptly started to give me "object reference not set" exceptions, with a stack trace going deep into SD.LLBLGen.Pro.ORMSupportClasses.

I checked the version, and it seems it's VERY old indeed: fileversion is 1.20051.7.307 and copyright date 2002-2005 .

LLBLGen is new to me, so I was wondering what kind of effort I can expect if I upgrade to the latest version. Would it be a matter of replacing the old DLL's and rebuilding? Or will this likely not work anymore, and will complete regeneration be necessary?

The application was built on Sql Server 2005 and .NET framework 2.0. I would post some sample code as an indication of how the LLBLGen DLL's are used in the application, but I can't even be sure what files were generated by LLBLGen and what files were customized etc...

Thanks,

Patrick

You can debug and trace the source of the exceptions and try to solve them.

Otherwise if you want to upgrade to the latest version (v.3.0), you will have to buy a license, and then you will have to migrate your project to v.2.6 first, then using migration templates you can port the project to v.3.0.

All the way you should read the documentation section migrating your code, to check for breaking changes.

1.20051.7.307 is the latest build of 1.0.2005.1

If it's not too much trouble, we could look into the exception, perhaps it's easy to solve. So if you could post the code snippet which triggers the exception, some details about the entities involved and the stacktrace (with exception message) it would be great.