Home Dashboard Directory Help
Search

System.Data.Oracleclient.DLL by Kenoby1


Status: 

Closed
 as By Design Help for as By Design


2
0
Sign in
to vote
Type: Bug
ID: 562278
Opened: 5/27/2010 10:16:17 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Trying to add a reference to System.Data.OracleClient.Dll", dated 3/18/2010. I know that this support will be deprecated in FUTURE versions, but isn't it supposed to work now?

Details
Sign in to post a comment.
Posted by Microsoft on 5/28/2010 at 4:24 PM
Hi,

Thanks for reporting this issue. We shipped System.Data.OracleClient.dll in the full version .NET Framework 4.0, but not as a part of the client SKU. The decision was made to align with our decision to deprecate the component.

For you to reference System.Data.OracleClient.dll in your project, you need to have your project to target “.NET Framework 4” not “.NET Framework 4 Client Profile”. You can change the target by bring up the properties of your project (Solution Explorer/Right click on the project / “Properties”) and select “Application” tab. Change “Target framework:” to “.NET Framework 4” from “.NET Framework 4 Client Profile”. As a side note, the machines where you are deploying your application will need to have the full version of .NET Framework 4.0 installed rather than the client version.

As this is intended behavior, we will resolve this issue as “By Design”. If you still have a problem with this issue, please don’t hesitate to contact us. Thanks again for reporting this issue.

Thanks,

Young Gah Kim
Development Lead
ADO.NET Managed Providers Team

Posted by Microsoft on 5/27/2010 at 10:02 PM
Thank you for reporting the issue.
We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.These specialized experts will follow-up with your issue.
Posted by Microsoft on 5/27/2010 at 5:06 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.