Hi FB

obzekt discovered a possible bug in the SDK.

obzekt wrote:

The LGP I'm using has been created by another developer and initially held his SQL credentials which are different than mine. When I open the LGP though, I refresh the catalog providing my own credentials and save the LGP expecting the connection string to be totally overwritten, but is not.

As your exception handling exposed, ProjectDefinition.ConnectionString is still providing the old string to your TP which fails. It seems like a bug in the LLBLGen SDK.

The SDK is not yet updated with the very latest driver sourcecode, however should have the latest taskperformer stuff.

The connection string is stored in the project object, which should be readable by your code and hasn't anything to do with the SDK or the sourcecode in the SDK (you reference the shipped assemblies )

(you reference the shipped assemblies Regular Smiley)

OK...Then there is a possible bug in the shipped assemblies

wayne wrote:

(you reference the shipped assemblies Regular Smiley)

OK...Then there is a possible bug in the shipped assemblies

True, see thread in general

(in short: connection string wasn't set to new value if connection parameters were changed. Normally you won't run into this, however with your taskperformer you will)