Discussions
Categories
- 385K All Categories
- 2.6K Data
- 595 Big Data Appliance
- 2K Data Science
- 452.1K Databases
- 222.4K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 576 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 575 SQLcl
- 4K SQL Developer Data Modeler
- 187.7K SQL & PL/SQL
- 21.5K SQL Developer
- 12 Data Integration
- 12 GoldenGate
- 297.7K Development
- 3 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 294.3K Development Tools
- 118 DevOps
- 3.1K QA/Testing
- 646.5K Java
- 30 Java Learning Subscription
- 37K Database Connectivity
- 185 Java Community Process
- 107 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 174 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 584 LiveLabs
- 41 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 191 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 240 Portuguese
VS 2022 AND ODT
Answers
-
Following for updates.
-
Christian:
I'm willing to accept that there was a bug in VS 2022 on the Microsoft side. However, as previously pointed out in this thread, Microsoft does preview versions long before the release date. There is no good reason for Oracle not to be working on ODT Next during that preview period. The only reason that makes sense is that Oracle doesn't consider this to be a priority and therefore doesn't assign sufficient resources for the work.
If this was a one-time thing, I would feel differently. However, this has been a consistent pattern with previous releases of ODT. IMO, it has been normal for ODT to trail the release of VS by at least nine months. Please feel free to refute my statement if you can.
Another poster asked a reasonable question "What is the functionality that is broken?" My best guess is that most of us are using ODT to do reverse engineering. If that part works, we'd cheerfully accept bugs or missing functionality elsewhere until you get this resolved.
All of these posters should tell you two things. First, provide regular updates at least every two weeks. Second, do better on the next release. That means getting the resources now and committing to having a functional release of ODT within one month of the Visual Studio release.
-
Are there any updates or timelines? Its been over a year since we were told Oracle would support the new Visual studio version and we are unable to upgrade due to the lack of support and urgency from Oracle.
-
Hi,
Is there any update on ODT for VS 2022?
-
following for update
-
Following for updates to ODTforVS2022
-
...and I was hoping that, ten months after VS2022 was released, Oracle would be able to deliver at least an release candidate...
silly me...
-
At this point it almost feels like Oracle has abandoned anyone who tries to use .NET and Oracle DB's and is wanting them to move to a competitor's DB like MS SQL and does not want their business any longer.
@Christian.Shay -Oracle Can you provide an update or let us know if you are no longer planning to support .NET teams that use Oracle? This is taking far too long and the excuse of it being a Microsoft issue no longer holds water given it's been going on a year since the release version came out and over a year since the beta came out.
-
Following thread for an update.
-
Radio silence since July 1st is deafening... OK, Microsoft might be at cause (as usual ;-)) but some more communication would be appreciated...