console core 3.1 gives this error - Unrecognized configuration section add

Question

console core 3.1 gives this error - Unrecognized configuration section add

iqworks Information Quality Works 331

Hi, this is what i get from running my console core 3.1 project that is trying to access .net 4.7.2, through, .netstandard2.0, which will run a method in my 4.7.2 which returns data back into .netstandard2.0 and returns this data to be displayed on the core console. Take note, the data returned from 4.7.2 is entity framework data 6.4.4.

> The current error is (as in one of the images from my previous post)
Inner Exception 1:
ConfigurationErrorsException: Configuration system failed to initialize
Inner Exception 2:
ConfigurationErrorsException: Unrecognized configuration section add. (D:\MBSSys\MbsaMultiTargeting\MbsaMultiTargeting\bin\Debug\net472\MbsaMultiTargeting.exe.Config line 6)

As you can see, this is the location of my "MbsaMultiTargeting.exe.Config " this is what the config file looks like:

Now I need advice about what is WRONG with this config section error. Googling this error shows many different config files, but I dont see any that handle an "exe.config" file for core console 3.1?

Thanks for any advice or suggestions

Yiyi You - MSFT 521 Reputation points

2022-12-08T09:28:26.857+00:00

Hi,@iqworks Information Quality Works

Can you explain more about what you want?Do you mean you want to share the database between .net core 3.1 and .net 4.7.2?If so,maybe you can try to use .net standard.
iqworks Information Quality Works 331 Reputation points

2022-12-09T00:41:44.747+00:00

Hi Yiyi, what i am trying use core 3.1 to access my .net4.7.2 EF6, THROUGH .netstandard.
Bruce was correct, you cannot access .net4.7.2 from core 3.1. But I found the actual reason.
Core 3.1 puts its connection string in appsettings.json. net4.7.2 cannot read this appsettings.json, it only reads its web.consig file. One solution is to pass the connection string from core 3.1 through .netstandard to .net7.7.2. This was ONE suggestion.

But, for others that are looking into this issue. Do a google search with "core 3.1 console .nt472 Message=No connection string named could be found in the application config file. Source=EntityFramework". Here you will find MANY links of people suggesting there reasoning and, many different ways to get around this.

But thanks for any further input from Bruce and Yiyi for your suggestions and advice.

Accepted answer

1 additional answer

Your answer

Yiyi You - MSFT 521 Reputation points

2022-12-08T09:28:26.857+00:00

Hi,@iqworks Information Quality Works

Can you explain more about what you want?Do you mean you want to share the database between .net core 3.1 and .net 4.7.2?If so,maybe you can try to use .net standard.
iqworks Information Quality Works 331 Reputation points

2022-12-09T00:41:44.747+00:00

Hi Yiyi, what i am trying use core 3.1 to access my .net4.7.2 EF6, THROUGH .netstandard.
Bruce was correct, you cannot access .net4.7.2 from core 3.1. But I found the actual reason.
Core 3.1 puts its connection string in appsettings.json. net4.7.2 cannot read this appsettings.json, it only reads its web.consig file. One solution is to pass the connection string from core 3.1 through .netstandard to .net7.7.2. This was ONE suggestion.

But, for others that are looking into this issue. Do a google search with "core 3.1 console .nt472 Message=No connection string named could be found in the application config file. Source=EntityFramework". Here you will find MANY links of people suggesting there reasoning and, many different ways to get around this.

But thanks for any further input from Bruce and Yiyi for your suggestions and advice.

Answer 1

Bruce (SqlWork.com) 77,686 Volunteer Moderator

As stated in your last post, core 3.1 can not call 4.* code. Also .net core apps do not support .config files.

iqworks Information Quality Works 331 Reputation points

2022-12-05T15:46:43.387+00:00

Hi Bruce, core 3.1 can not call 4. code*

I am trying to access my .net 4.7.2 THROUGH .netstandard. Is using .netstandard here incorrect? Or am I not understanding something :-)

I can understand from our past postings that I cannot make a call DIRECTLY from core 3.1 TO .net 4.7.2.
I guess your saying this is the reason i am getting these errors in the first place?

It just seems like I fix each error I get and it brings me further into the processing I am trying . I guess I will get to an error where there is no fix?

In the meantime, can you give me any advice about my "MbsaMultiTargeting.exe.Config" and the Unrecognized configuration section add error?

thanks again for your time and valuable advice.
Bruce (SqlWork.com) 77,686 Reputation points Volunteer Moderator

2022-12-05T20:46:21.257+00:00

calling 4.7 thru netstandard only works if the caller of .netstardard is .net 4.7/4.8 program. the issue is that 4.* code is not supported by the .net core runtime. that is you can get to build, but t won't run. actually if the 4.7 code is a proper subset of .netstandard 2.0, it might work - but then it should be compiled as .netstandard 2.0..

agin to share library code between between 4.7 and core, it must be built as .net standard 2.0, or multi-target each platform. also all the libraries the library calls must follow the same rules.

again, "MbsaMultiTargeting.exe.Config" is only supported by a .net 4.7/4.8 programs.

Answer 2

iqworks Information Quality Works 331

 Hi Yiyi, what i am trying to do is to use core 3.1 to access my .net4.7.2 EF6, THROUGH .netstandard.

Bruce was correct, you cannot access .net4.7.2 from core 3.1. But I found the actual reason pertaining to my particular issue.
Core 3.1 puts its connection string in appsettings.json. net4.7.2 cannot read this appsettings.json, it only reads its web.consig file. One solution is to pass the connection string as a parm or something like a session variable and send it from core 3.1 through .netstandard to .net7.7.2. This was ONE suggestion.

But, for others that are looking into this issue. Do a google search with "core 3.1 console .nt472 Message=No connection string named could be found in the application config file. Source=EntityFramework". Here you will find MANY links of people explaining this issue and, the many different ways each link showing how to get around this.

Thank you guys for your help and enlighting information.

Bruce (SqlWork.com) 77,686 Reputation points Volunteer Moderator

2022-12-11T19:09:01.557+00:00

The issue is not where the configuration file is, it’s that the two runtimes 4.* and .net core have different and incompatible configuration libraries.

Components built to be shared (.netstandard 2.0) use a new configuration wrapper that works for both. There are many more libraries besides configuration that have this same issue.

When libraries for frameworks change major versions, breaking changes are always allowed.
iqworks Information Quality Works 331 Reputation points

2022-12-13T15:22:20.203+00:00
thanks again Bruce. In my case, I use the appsettings.json file is in my .netstandard 2.0 and my core 3.1 console calls a method in .netstandard which then calls the .net4.7.2.

But I appreciate this answer as well. You told me this several times :-), and I understand.

This is what I googled :
"core 3.1 console .nt472 Message=No connection string named could be found in the application"

I am working on another project for the next few days, but I get back, I will try a few suggestions of passing the connection strings. I will report how that works. Currently I left off where I got a connection string could not be found.

thanks again Bruce.

Share via

console core 3.1 gives this error - Unrecognized configuration section add

1 additional answer

Your answer