This release of the Oracle Developer Tools for Visual Studio .NET now supports both Microsoft Visual Studio .NET 2003 and Visual Studio 2005. It also includes a tightly integrated PL/SQL debugger. The latest downloads, information, and community forums can be found here: http://www.oracle.com/technology/tech/dotnet/tools/index.html
This file contains important information about Oracle Developer Tools for Visual Studio .NET. The following topics are covered:
Oracle is very interested to hear your comments related to this release, including feature requests and bug reports. Please visit the Oracle Technology Network (OTN) community forums to tell us what you think!
https://community.oracle.com/community/database/developer-tools/windows_and_.net/oracle_developer_tools_for_visual_studio (Registration with OTN required)
This install includes the following:
Visual Studio 2005 and .NET Stored Procedures Deployment Requires Update to the Database
To use Visual Studio 2005 to generate or deploy .NET stored procedures requires that the database be updated with Oracle Database Extensions for .NET version 10.2.0.2.20 or higher.
Integrated online help
Configuring PL/SQL debugging for first use
Please see the online help for information detailing what configuration steps are required before PL/SQL debugging is possible. This includes the following database side configurations:
Oracle connection errors after installing Oracle Developer Tools in new Oracle home
If you start receiving Oracle connection errors immediately after installing Oracle Developer Tools, check to see if you created a new Oracle home during the install. If you did, you will need to copy over the TNSNAMES.ORA file from your old Oracle home to the new one.
Do not install Oracle Developer Tools into an Oracle8, Oracle9, or Oracle 10.1 Oracle Home
In order for a locally installed database to show up as a "Local Database" in the connection dialog box, Oracle Developer Tools must be installed in the same Oracle Home as the database. If the tools are installed in a separate Oracle home from the database, the Oracle NET Configuration assistant will need to be used to create an alias for the database.
To Deinstall, run Setup.exe, or use Oracle Universal Installer
This installation does not install the Oracle Universal Installer. If you have already installed the Universal Installer as part of some other product, you may run it from the Programs menu and choose "Deinstall products." Otherwise, run the Setup.exe that was provided with this installation and choose "Deinstall products."
Japanese Online Help
Visual Studio .NET 2002 and Visual Studio 2005 Express Editions not supported
Visual Studio 2005 Express Edition does not allow "add-ins" so it is not possible to use ODT with it. Visual Studio .NET 2002 is not supported.
DataSet generation problems with OracleDataAdapter for Web Site projects in Visual Studio 2005
The version of Visual Studio 2005 that is shipped does not contain C# ASP.NET Web Application project types, and users typically use Web Site projects to create solutions. However, these Web Site projects have the caveat that once the OracleDataAdapter has been dragged into the component designer the code generation for the corresponding DataSet does not work properly. Microsoft provides a patch to Visual Studio 2005 that will make all ASP.NET Web Application projects available. Once developers use these ASP.NET Web Application project types the DataSet code generation will work exactly as it did in Visual Studio .NET 2003.
The patch is located here:
PL/SQL Debugger known issues
ODT and Visual Studio 2005 known issues
User defined datatypes created after opening a connection to the database
After a connection to the database is opened using Oracle Explorer in Visual Studio .NET, if a new user defined datatype is created in the database, i.e. VARRAY, NESTED TABLE, or OBJECT, it will not be visible to the PL/SQL wizards unless the connection node is refreshed. To achieve this, go to the connection node in Oracle Explorer, right click, and choose refresh from the menu.
PL/SQL types as parameter types for stored procedure/function/package method
Some of the PL/SQL data types (such as NATURAL or INTEGER) are aliases to database native types (for example, NUMBER). When these PL/SQL types (NATURAL, INTEGER) are used as parameter types in stored procedure or function, the PL/SQL data type displayed in the properties window for these parameters will reflect the database native type.
PL/SQL autocompletion with synonyms
In a PL/SQL editor window, synonyms nested beyond 2 levels will not expand for autocompletion.
Connecting with SYSOPER role
Connecting with SYSOPER role is not supported.
Case sensitivity and special characters in name
To preserve the case in a name for a schema object, the name needs to enclosed in double quotes. Otherwise, when the focus is moved out of the text box where the schema object name is entered the schema object name will be automatically uppercased.
Retrieving table or view data
When retrieving data from a table or view, display or editing of data for the following Oracle types are not supported:
XMLType columns and parameters not supported with 9.0.x database
Using XMLType columns or parameters with 9.0.x database is not supported.
Running stored procedure or function
"This product includes software developed by the University of California, Berkeley and its contributors."