I constantly get the following message in my output/debug windows. The app doesn't crash but I was wondering what the deal with it is:

A first chance exception of type 'System.InvalidOperationException' occurred in System.dll

       using (DataAccessAdapter adapter = new DataAccessAdapter()) //after this line executes
        {
            //Some dataCode
        }

Just wondering if I may be doing something wrong somewhere or something.

connection string in config not available?

it is loading data so...Unless llblgen is clairvoyant (which wouldn't surprise me) ...it must be seeing the connection string.

Ok when do you receive the message, when you start a debug session and you get an exception there? Because if it's a runtime exception, the execution stops, and should give you a stacktrace

No the app does not break on the exception. I just see it pass by in the output window (Debug.WriteLine()) type of deal.

Sam wrote:

No the app does not break on the exception. I just see it pass by in the output window (Debug.WriteLine()) type of deal.

So you debug the app and you see that output? If so, I'll try to reproduce it.

Exactly. And it is not just one project. I have seen it will all my Adapter LLBLGen projects.

This occurs if the following two keys are not present in the App.Config file.

Values don't matter.

Add the two keys to the appSettings section and the problem goes away.

Change the value to 1 and specify a specific catalog if you like.

    <add key="CatalogNameUsageSetting" value="0"/>
    <add key="CatalogNameToUse" value="NorthWind"/>

Hmm, that shouldn't be happening, as the code checks if the sections are there or not. Will see what the cause of this is... Thanks Jim

Thanks Jim that fixed it!

I can't reproduce it with a normal .config file. Sam, did you by any change have a line like: <section name="sqlServerCatalogNameOverwrites" type="System.Configuration.NameValueSectionHandler" />

in your config file? Because THEN you need to add more lines, though I can't reproduce the exception... (at least not on .NET 1.x)

I can reproduce it at will on 2.0 with 1.2005.1 Feb 9 2006

I do not have the sqlServerCatalogNameOverwrites section.

I initially got into this because of the delay in startup time due to the exception while debugging.

Thanks, will look into it.

I have not modified the connection string but I am using 2.0 as well.

Ok, the exception is occuring in DataAccessAdapter.ReadHandleCatalogNameSettingFromConfig(). (is in the generated code)

It's occuring when this line is executed:

CatalogNameUsage catalogNameUsageSetting = (CatalogNameUsage)(int)configReader.GetValue("CatalogNameUsageSetting", typeof(int));

there's no way to test if a section is there, you just have to try and if it's not there you'll end up with an exception, which says: "The key 'CatalogNameUsageSetting' does not exist in the appSettings configuration section.". This exception is caught and never propagated upwards, but used as a signal that the setting isn't there and the code therefore reverts to the default.

So that's the reason for this exception. I.o.w.: harmless.

I also get this Exception but I pass a custom connection string to the Adapter so the exception is not necessary because there is no need to look up the config file.

DerMohr wrote:

I also get this Exception but I pass a custom connection string to the Adapter so the exception is not necessary because there is no need to look up the config file.

The lookup is for the name overwrites, not for the connection string.

Do you know how to disable this exception from scrolling in the debug window for VS2005?

Do you know how to disable this exception from scrolling in the debug window for VS2005?

I found the following thread, which might be helpful in this case http://www.codecomments.com/archive370-2005-10-659423.html