Unable to create connection in ASP.NET core in microsoft.practices.enterpriselibrary.data

Question

0.00/5 (No votes)

See more:

I am using Microsoft.Practices.EnterpriseLibrary.Data to create connection using below code

Database namedDB = EnterpriseLibraryContainer.Current.GetInstance<database>("myConnectionString");

below is my appsetting.json

ConnectionStrings": {
"Default": "Server=CINT-IAOW-014\\***;Database=***;User ID=**;Password=***;Trusted_Connection=False;",
"providerName": "System.Data.SqlClient"
}
but i am getting this error :

Microsoft.Practices.ServiceLocation.ActivationException: 'Activation error occurred while trying to get instance of type Database, key "myConnectionString"'

InvalidOperationException: The current type, Microsoft.Practices.EnterpriseLibrary.Data.Database, is an abstract class and cannot be constructed. Are you missing a type mapping?
Ple

What I have tried:

unable to find any solution on the issue

Posted 3-Feb-20 5:41am

vivek_2984

Add a Solution

Comments

ZurdoDev 3-Feb-20 11:47am

Lots of possible solutions if you google.

Richard Deeming 3-Feb-20 12:19pm

You are trying to access a connection string called myConnectionString, but the only connection string in your appSettings file is called Default.

Also, it's not clear whether the Microsoft.Practices.EnterpriseLibrary.Data library supports .NET Core. There's a .NET Core port on GitHub, but I can't immediately tell whether it supports reading connection strings from the appSettings file.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)