I haven't used LLBLGen for a month or so now, but today when I generated my code and then did my first FetchEntityCollection, I got a "Object not set to an instance" error.

I traced it down to the method in my DataAccessAdapter code named ReadHandleCatalogNameSettingFromConfig. Now, I fixed my problem by adding in the two app settings it was looking for (CatalogNameUsageSetting and CatalogNameToUse) but I was confused because I never had to do that before. I looked in the generated app.config files and they aren't in there. Did something change in the last month or has that been around for a while? If it has been around for a while, why wasn't I affected by it before?

Nick,

Take a look at this LLBLGen User Manual page for a full explanation of what's going on with these properties:

Generated code - DataAccessAdapter Functionality, Adapter "Catalog specific persistence info (SqlServer specific)"

So to recap, you didn't have any config file settings in your .config file besides the connection string?

Otis wrote:

So to recap, you didn't have any config file settings in your .config file besides the connection string?

Exactly. Now, in the connection string I had "initial catalog" but I don't think your code was examining the actual string itself, was it?

Paul.Lewis wrote:

Nick,

Take a look at this LLBLGen User Manual page for a full explanation of what's going on with these properties:

Generated code - DataAccessAdapter Functionality, Adapter "Catalog specific persistence info (SqlServer specific)"

Thanks, Paul. That's how I figured out how to fix the problem. So I undertand it was my fault to begin with, but it seemed odd to me that it worked before when these settings were absent.

It should work without these settings present. (so with a config file with solely an appsettings section with a connection string). Though if you define the sections at the top of the config file and not add the actual sections to the config file, it won't work.