Home Dashboard Directory Help
Search

.NET 3.5 Application with Oracle in Visual Studio 10: Assembly Error by NikiR


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 568510
Opened: 6/17/2010 10:32:53 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Targeting Framework Version 3.5 in Visual Studio in an application using Oracle Tools for .NET leads to 'missing assembly' compilation error.
Details
Sign in to post a comment.
Posted by Microsoft on 3/12/2011 at 7:15 AM
Hi,

Thanks for reporting this issue again. We will consider what we can do in the future to avoid this kind of issue. For now, we will resolve it as "External" as this is an issue with ODP.NET setup.

Thanks,

Young Gah Kim
Developement Lead
ADO.NET Managed Providers and DataSet Team

Posted by NikiR on 8/9/2010 at 3:41 AM
Been out of commission for a while, so sorry for the delay.

The problem seems to be caused by an issue with the Oracle Data Provider. Once this was removed the problem was resolved.

It leaves me with the problem that I can't use Oracle in VS10 unless I use the depreciated oracle connector.

I appreciate that the ODP.net is provided by Oracle, so I'll let them know of the issue, but there is clearly a conflict there that Oracle and the Visual Studio team may need to interact on.

Thanks for your help.
Posted by Microsoft on 7/22/2010 at 11:08 AM
Hi,

Thanks for reporting this issue. Do you have the same issue if you don’t install Oracle Data Provider for .NET? Have you try to re-install VS 2010?

Thanks,

Young Gah Kim
Development Lead
ADO.NET Managed Providers Team
Posted by Microsoft on 6/18/2010 at 1:16 AM
Thanks for your feedback.

We are rerouting 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 6/17/2010 at 5:04 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.