DB2 Development Add-In Technical Preview

Document options Document options requiring JavaScript are not displayed Rate this page Help us improve this content

Level: Introductory

Abdul Al-Azzawe, DB2 Development Tools Architect, IBM San Francisco

04 Dec 2003

IBM has introduced a tech preview for the DB2 Development Add-in for Visual Studio .NET. This article introduces you to all the new features and rich functionality that are now available.

Introduction

The DB2® Development Add-In for Visual Studio .NET Stinger Technical Preview is a monumental achievement that builds upon a robust and functionally rich product. It's a preview of technologies designed to enhance productivity for .NET and Java application programmers. The sheer number of new features introduced and the time it took to release them is mind boggling!

Apart from the extended server support, there are four main feature groups. Each one of these feature groups is worthy of a product release on its own:

• Common Language Runtime (CLR) procedure development
  The CLR procedures support brings the power of C# and VB.NET development to the DB2 Universal Database servers. This key new feature has already been demonstrated in a number of Microsoft conferences and VS.NET 2003 and Windows® 2003 launch events.
• Wizards for creating server objects
  The new set of scripting wizards greatly simplifies the task of creating new server objects.
• Re-usable data adapters
  The re-usable adapters are a powerful new usability tool that will expedite your ADO.NET application development promoting code sharing and re-use.
• Automatic generation of Web methods and Web services
  Finally, the new Web methods and Web services automatic generation support will enable you to deploy your DB2 database logic and schema to the Web without having to write a single line of code!

Release features at a glance

Here are some of the new things you will be able to do using the features of the DB2 Development Add-In for Visual Studio .NET tech preview:

• Discover and work with remote DB2 data connections using server host name/IP, port, and database name
• Create new tables, views, indexes, and triggers using functionally rich scripting wizards
• Extend the SQL IntelliSense support beyond the SQL editor to include multi-line edit controls in your wizards and dialogs
• Retrieve data for tables and views using data grids in read/write mode
• Access table and view details including columns, indexes, and triggers
• Generate create scripts for tables, views, functions, and procedures
• Develop and deploy DB2 CLR procedures using C# and VB.NET.
• Manage the deployment of CLR assemblies to local and remote DB2 for windows servers
• Create re-usable data adapters directly under your data connections and share them with other developers, across projects and form designers
• Discover or manually define the shape of your data adapter result sets
• Preview results from your data adapters using data grids in read/write mode
• Automatically generate Web methods and Web services for your data adapters or their commands
• Customize your add-in using an extended set of DB2 tools settings
• Add collapsible regions to your DB2 database script files.

Availability

The DB2 Development Add-In for Visual Studio .NET Stinger Technical Preview is a limited availability product. This is not part of DB2 Universal Database V8.1.2 or V8.1.3.

Supported platforms

The DB2 Development Add-In for Visual Studio .NET Technical Preview extends the DB2 server support to include:

• DB2 for z/OS® and OS/390® versions 6, 7, and 8
• DB2 for iSeries® (AS/400®) versions 5.1 and 5.2
• DB2 for Linux, UNIX®, and Windows V8.1 and later

Currently not all of the features are available for the various DB2 servers. Table 1 lists the restricted features:

Table 1. Restricted features

Back to top

DB2 database project

The DB2 database project has been enhanced in this release. The project tree now includes tables, indexes, triggers, and views, as well as procedures, Functions and scripts default folders. Some of the new features of the DB2 database project include:

• New scripting wizards for creating table, view, trigger and index project script items
• New CLR procedure wizard that generates the required DDL for your CLR project methods.
• Ability to manage CLR project assemblies and deployment to local or remote DB2 servers.
• Collapsible script regions using the extensible ScriptOptions XML tags
• Improved multi-configuration support targeting multiple data connections with advanced z/OS options
• Full automation support allowing for extending the DB2 database project using the standard extensibility features of Visual Studio .NET.

As with any other full-featured project template in Visual Studio .NET, the DB2 database project supports cross-project dependencies, build order, and integration with source control management systems like Visual Source Safe and RationalClear Case.

Note that the DB2 database project is now accessible from the IBM Projects folder as well as the standard Visual Studio .NET generic projects folder.

Scripting wizards

One of the most powerful features of the new DB2 database project is the set of functionally rich scripting wizards that greatly simplify the task of creating new DB2 server objects. Apart from enhancing the existing SQL procedure and SQL function wizards to incorporate new usability features, we've added a set of new wizards, including the table, view, index, and trigger wizards. The new CLR wizard will be covered in the DB2 CLR procedures section below.

Smart multi-line SQL editor

This new release of the DB2 Development Add-In boasts of a new multi-line SQL editor that supports SQL syntax colorization and intellisense. The intellisense support includes the ability to use the schema defined in the DB2 database project and in the various IBM Explorer data connections to allow for quick lookup of schema objects given a schema, or a list of columns given a table or a view, or a list of parameters given a procedure or function

The other key feature of the new editor is the built-in SQL parser that allows for, where possible, the lookup of data type of parameters. This includes positional parameter markers as well as actual named parameters that are preceded with a colon special character.

This new editor is embedded in most of the DB2 Development Add-In wizards and dialogs.

SQL procedure and function wizards

The SQL procedure and function wizards have been enhanced to incorporate the smart multi-line SQL editor for defining the SQL statements required by these routines. This enhancement includes the syntax colorization, intellisense, and the SQL parser that automatically detects routine parameters and their types. Another interesting enhancement to this wizard is the ability to import additional routine parameters from existing table and view column definitions.

Based on customer feedback, the code fragments wizard step has been moved to a secondary dialog, thus reducing the number of wizard steps required to create a new routine.

Table wizard

The table wizard allows you to quickly define new DB2 tables that range from very simplistic tables to ones that include primary keys, unique keys, and foreign keys, as well as advanced check constraints. The table wizard also allows for defining columns with special values, such as default values, formula-based values, or identity values.

Another very powerful feature of this wizard is the ability to import column definitions from existing tables and views that are defined in the various data connections of the IBM Explorer. This means that now you can easily clone the full or partial definition of other tables/views as well as include the required columns for defining referential integrity between two or more tables.

The table wizard steps include:

1. Identification - Specify a schema, table name, table space, and comment.
2. Primary Key - Define one primary key for this table. A primary key is a column or combination of columns that uniquely identifies a row in a table. The columns of a primary key cannot contain null values.
3. Unique Keys - Define one or more unique keys. A unique key is a key that is constrained so that no two of its values are equal. The columns of a unique key cannot contain null values.
4. Foreign Keys - Define one or more foreign keys for this table. A foreign key is a column or set of columns whose values are required to match at least one primary key value in another table.
5. Script Options - Specify files that contain script fragments that you want to insert in the generated table script. Also, specify additional SQL statements that you want to generate.

View wizard

The view wizard is a simple yet powerful wizard that allows you to define the SQL query required to define a new view using the smart multi-line SQL editor detailed above.

The view wizard steps include:

1. Identification - Specify a schema, view name, and comment for the view that you are creating.
2. Content - Specify the CREATE VIEW SQL statement. You can edit the SQL template to create your own statement.
3. Script Options - Specify files that contain script fragments that you want to insert in the generated view script. Also, specify additional SQL statements that you want to generate.

Index wizard

The index wizard allows you to define an index for existing tables. This wizard automatically detects the definition of the table and shows the list of appropriate columns. You can create regular as well as unique indexes. Definition only indexes are supported for federated data sources, also known as nicknames.

The index wizard steps include:

1. Identification - Specify an index name, table name, comment, and index options.
2. Columns - Specify the column or columns that you want to define as part of the index key.
3. Script Options - Specify files that contain script fragments that you want to insert in the generated index script. Also, specify additional SQL statements that you want to generate.

Trigger wizard

The trigger wizard greatly simplifies the somewhat complex task of creating triggers for tables and views. It breaks down the trigger creation steps into more manageable ones. The trigger SQL condition allows you to define the condition, namely the WHEN clause, and the trigger action allows you to define the action taken when the trigger is executed. Both of these steps make use of the smart multi-line SQL editor detailed above.

The trigger wizard steps include:

1. Identification - Specify the source table or view for the trigger and the trigger name, schema, and comment.
2. Execution Condition - Specify the time and event to execute the trigger.
3. SQL Condition - Further specify the qualified table or view condition before a trigger can be activated.
4. Action - Specify the action that the trigger can perform.
5. Script Options - Specify files that contain script fragments that you want to insert in the generated trigger script. Also, specify additional SQL statements that you want to generate.

Properties and configurations

A key feature that is unique to the DB2 database project and is missing from the Visual Studio .NET generic database project is the support for multiple configurations. This support allows you to target a different data connection for compiling the scripts as well as including and excluding script items from the project based on the active configuration. This feature enables you to target test, QA, and production systems that may be different databases residing on different servers.

For z/OS and OS/390 SQL procedures, the multi-configuration support also allows you to define a per-configuration set of advanced build options.

Back to top

DB2 data connections

The IBM Explorer has been greatly enhanced in this release. You can now

• Create new database
• Add remote server data connections
• Create new database objects in an ad hoc manner using full-featured wizards
• Generate create scripts
• Generate Web methods and Web services, and
• Create re-usable data adapters.

IBM Explorer data connections are now named connections. The add/modify connection dialog allows for discovery of DB2 servers, as well as DB2 server databases. You are no longer required to locally catalog the remote databases. Multiple data connections may be added for the same physical database. This allows for specifying a different set of filters on these connections or using a different user id and password to connect to the same database. Additionally, new local DB2 databases may be created from the data connections folder.

Based on your feedback, we have now created two separate connection settings, a default owner and a current owner. The default owner will be used in the various wizards as the pre-filled schema for the new object. The current owner will be used by the add-in to issue a SET CURRENT SCHEMA or SQL ID prior to executing any scripts against the database.

Another key enhancement is the ability to specify per-connection advanced z/OS build and runtime options. Defaults for these options are specified in the userOptions.xml file and are customizable using the IBM DB2 Tools settings dialog detailed below. The SQL procedure wizard will use these options for any newly-created procedure script. You can also look up these options from a centrally administered user table.

Scripting wizards

One of the key new features of this release is the set of functionally rich scripting wizards that greatly simplify the task of creating new database objects in an ad hoc manner directly from the IBM Explorer. These are the same set of wizards outlined earlier in the DB2 database project section with the exception of a new DB2 project selection page. You now have the option of either adding the new scripts to a new or existing DB2 database project or directly executing the scripts against the database without requiring a DB2 database project.

Tables and views

The tables and views support has been enhanced to allow for creation of new tables and views using wizards. Additionally you can create indexes and triggers for tables, and triggers for views. When launching the trigger and index wizard for a specific table or view, the table and view information will be pre-filled in the wizard.

Apart from creating the new objects, you can also access the table and view details using a new details designer. The table and view details include the listing of columns, indexes, and triggers. You also have the ability to delete and create new indexes and triggers using this designer.

The table and view preview data feature has been enhanced to now allow for a refresh action, as well as direct insert, update, and delete of data rows where possible.

Another feature that has been added for Linux, UNIX, and Windows DB2 data connections is the ability to generate the CREATE DDL based on the catalog information. This feature makes use of the db2look utility to generate the script. This script can either be added as a new script item to a new or existing DB2 database project or it can be inserted into existing DB2 script files. You can also drag and drop tables and views directly from the IBM Explorer and drop them onto DB2 script files.

Procedures and functions

The procedures and functions support has also been enhanced to include the ability to create new SQL and CLR procedures as well as SQL functions using wizards. The generated scripts for the new objects can either be executed directly or added to new or existing DB2 database projects.

The ability to view the source code of SQL procedures and functions as well as execute any language procedure and function has not changed much in this new release.

Back to top

DB2 CLR procedures

One of the most exciting new features of this new release is support for CLR (Common Language Runtime) procedures. You can now code C# and VB.NET methods in class assemblies and then deploy them as DB2 procedures. DB2 CLR procedures enable you to code your procedures using your choice of .NET language.

Although SQL in the body of CLR procedures is optional, any SQL contained in these procedures may be coded using the DB2Context object to create new ADO.NET commands that have the context connection object pre-set. Apart from in, out, and in/out parameters, CLR procedures can also return zero or more result sets to the client.

DB2 Class Library

Although you can use the standard Class Library template from the C# and VB.NET projects folders to code new CLR methods, a DB2 Class Library project template has also been added for you under these folders. The advantages of using the DB2 Class Library project template include the automatic project reference to the DB2 managed provider, IBM.Data.DB2, and the creation of the base class and method that conform to the required signature criteria for a DB2 CLR procedure.

You can use the new DB2 Class project item template for C# and VB.NET to add additional CLR method and classes to your project.

using System;
using IBM.Data.DB2;

namespace DB2ClassLibrary1
{
	/// <>summary>
	/// Summary description for DB2Class1.
	/// This class and method can be used as the basis for a DB2 CLR procedure.
	/// For more information on creating and deploying DB2 CLR procedures visit:
	///	http://www.ibm.com/software/data/developer
	///
	/// <summary>
	public class DB2Class1
	{

	  public static void DB2Procedure1(
		String		inParm1,
		ref String	inoutParm2,
		out String	outParm3)
	  {
		// Create new command object from connection context
		DB2Command myCommand = DB2Context.GetCommand();

		// TODO: Insert your code here

		outParm3 = null;
		// myCommand.CommandText = "SELECT FIRSTNME, MIDINIT, LASTNAME FROM EMPLOYEE";
		// DB2DataReader myReader = myCommand.ExecuteReader();
		// myReader.Close();
	 }
   }
}

Imports System
Imports IBM.Data.DB2

Namespace DB2ClassLibrary1

 'Summary description for DB2Class1.
 ' This class and method can be used as the basis for a DB2 CLR procedure.
 ' For more information on creating and deploying DB2 CLR procedures visit:
 '	http://www.ibm.com/software/data/developer
 '
 Public Class DB2Class1

     Public Shared Sub DB2Procedure1( _
         ByVal inParm1 As String, _
         ByRef inoutParm2 As String, _
         ByRef outParm3 As String)

         ' Create new command object from connection context
         Dim myCommand As DB2Command
         myCommand = DB2Context.GetCommand()

         ' TODO: Insert your code here

         outParm3 = Nothing
         ' myCommand.CommandText = "SELECT FIRSTNME, MIDINIT, LASTNAME FROM EMPLOYEE"
         ' Dim myReader As DB2DataReader
         ' myReader = myCommand.ExecuteReader()
         ' myReader.Close()
     End Sub

  End Class

End Namespace

DB2 CLR Procedure Wizard

Once you have coded one or more CLR methods and you would like to deploy them to the DB2 for Windows server, you can make use of the new DB2 CLR procedure wizard to automatically detect all of the CLR projects in your solution as well as all of the candidate CLR methods in your chosen project.

The CLR wizard can be launched from the add new item dialog for a DB2 database project, from the projects folder of a DB2 data connection in the IBM Explorer, or from the Tools->IBM DB2 Tools->DB2 CLR Procedure Wizard menu.

Although default mapping is performed for the procedure name, parameter names and data types, and procedure options, you have the ability to modify these mappings using the wizard, including the ability to specify the number of result sets returned from each procedure.

When you click Finish on the wizard, the DB2 script file is generated with the appropriate drop and create statements as well as the optional grant execute statements for each of the selected CLR methods.

-- <ScriptOptions statementSeparator="@"/>
@
-- <ScriptOptions errors="off"/>
@
-- Drop the procedure if one already exists
DROP  SPECIFIC PROCEDURE DB2PROCEDURE1
@
-- <ScriptOptions errors="on"/>
-- <ScriptOptions regionStart="CLR Procedure DB2PROCEDURE1" type="clr"/>
@
-- Create procedure
CREATE PROCEDURE DB2PROCEDURE1(
	IN	INPARM1		VARCHAR ( 254 ),
	INOUT	INOUTPARM2		VARCHAR ( 254 ),
	OUT	OUTPARM3		VARCHAR ( 254 ))
  SPECIFIC DB2PROCEDURE1
  LANGUAGE JAVA
  PARAMETER STYLE JAVA
  NO DBINFO
  FENCED
  CONTAINS SQL
  DYNAMIC RESULT SETS 0
  PROGRAM TYPE SUB
  EXTERNAL NAME '"[!DB2CLRAssembly DB2ClassLibrary4.dll]":DB2Class1!DB2Procedure1'
-- <ScriptOptions regionEnd="CLR Procedure DB2PROCEDURE1" type="clr" />
@
-- Grant access privilages to procedure
GRANT EXECUTE ON  SPECIFIC PROCEDURE DB2PROCEDURE1 TO PUBLIC
@

Notes:

• In the tech-preview release, the procedure language and parameter style is generated as Java. This will eventually be changed to DOTNET in the final release of the product.
• In order for the DB2 engine to recognize Java procedures as .NET CLR procedures, you will need to define a system level environment variable, JAVA_IS_DOTNET=1, on DB2 for Windows server system.

DB2 database project assemblies

In order for CLR procedures to work, they must be cataloged on the DB2 server and their assemblies must be shipped over to the DB2 server file system somewhere under the sqllib\function path. To accomplish this assembly movement, CLR assemblies are automatically registered with the DB2 database project by the DB2 CLR procedure wizard. You can manage the list of registered assemblies using the DB2 project assemblies dialog that is launched from the Assemblies... project pop-up menu.

Assemblies are registered once with the project regardless of the number of CLR procedures defined in them. Assemblies can be manually installed on the server using the install action on the dialog, or they can be automatically installed by the DB2 database project build action whenever they are modified (for example re-built).

Since multiple configurations may be specified for the solution, and the assembly may be created by the Visual Studio .NET compiler in a different file path depending on the active assembly, you must explicitly specify the client file path for the assembly using the DB2 project assemblies dialog.

CLR procedure script region

This release of the add-in introduces the concept of collapsible script regions that may be specified using the ScriptOptions XML tag. The DB2 CLR procedure wizard generates the appropriate script for the one or more selected CLR methods. Each CLR procedure CREAT DDL is wrapped in a CLR script region.

It's sometimes possible for the CLR method signature to be altered and fall out of sync with the generated CLR procedure CREATE DDL. The DB2 script needs to be updated to match the new CLR method signature. It is advisable to avoid manually modifying the generated CREATE DDL; rather, you should re-launch the DB2 CLR procedure wizard through the pop-up menu for the collapsed CLR region. Using this simple version of the wizard you can update the DB2 mapping information and re-generate the CREATE DDL for the updated method.

Back to top

DB2 managed provider tools

The DB2 Development Add-In for Visual Studio .NET tech preview extends the DB2 managed provider toolbox objects tooling to include a more intuitive connection string editor, a more advanced data adapter configuration wizard that allows for result shape definition and support for procedure commands, and an enhanced command editor that incorporates the full-blown features of the smart multi-line SQL editor with intellisense support detailed earlier.

DB2 Connection tooling

The new DB2 connection string editor allows you to choose from an existing DB2 data connection defined in the IBM Explorer. You will note that the connection passwords are no longer visible or persisted by default. This change was in line with the security guidelines for ADO.NET connections. You can certainly cause the password to be persisted using the persist security info=true connection string option.

DB2 Data Adapter tooling

The new configure DB2 data adapter wizard is tightly integrated with the SQL parser allowing for better column and parameter data type detections. The four data adapter commands support both SQL statements and procedures. The adapter automatically detects the procedure parameters, and allows for either discovery or manual definition of the procedure result sets.

The generate data set support has been enhanced to generate the data set definition based on the defined shape of the data adapter. This includes the ability to generate a dataset for a stored procedure select command.

The new preview data feature of data adapters allows for entering the required input parameter values and then displaying the results in an updatable data grid. Based on the data adapter commands, the update, delete, and insert commands may be used to propagate the design-time updates to the DB2 server.

DB2 Command tooling

The new DB2 command editor has been enhanced to include support for text commands and procedure commands.

When using text commands, the editor will make use of the smart multi-line SQL editor including the SQL parser for detecting the data column names and types and the SQL statement parameter names and types, and intellisense support for schema objects and columns of tables and views.

When using procedure commands, the editor will automatically retrieve the list of procedures defined in the IBM Explorer based on the chosen schema as well as the procedure parameters list.

When using the configure data adapter wizard, you can discover the command result set shape or manually define the shape of the one or more result sets using the import columns dialog that allows for importing columns from existing tables and views.

Back to top

Reusable data adapters

One of the greatest usability features of this new release of the DB2 Development Add-In is the introduction of the re-usable data adapters folder under the individual data connections of the IBM Explorer. These data adapters may be used across multiple win/web forms, across multiple projects, and shared among multiple users.

Some of the key capabilities of the reusable data adapters include:

• Ability to drag and drop onto winform and webform designers
• Ability to generate data set classes for inclusion in existing CLR projects
• Ability to use the data form wizard to quickly add functionally rich data forms to your project utilizing the automatically generated data adapter data sets classes
• Access to direct design-time preview of data adapter data in read/write mode
• Ability to generate Web methods and Web services for data adapters or commands
• Ability to import and export data adapters to/from the file system as XML files.

You can create new re-usable data adapters using a variety of methods including the use of the configure DB2 data adapter wizard. The wizard can also be used to alter the definition of the data adapter and its commands and the shape of the data adapter result sets.

Adding tables and views as reusable data adapters

You can quickly create a data adapter for any table or view listed in your data connection folders. This can be achieved by accessing the New->Data Adapter pop-up menu action for the table or view.

The appropriate insert, update, and delete command statements are automatically generated based on the definition of the table or view.

Adding procedures and functions as reusable data adapters

You can quickly create a data adapter for any procedure or function listed in your data connection folders. This can be achieved by accessing the New->Data Adapter pop-up menu action for the procedure or function.

By default, the insert, update, and delete commands are not generated; however, you can use the data adapter configuration wizard or the command editor to define these additional commands.

Adding component tray data adapters

Just as you can drag and drop data connection data adapters and drop them on form designers, you can select an existing form data adapter and click the Add to connection action to add the data adapter definition to the appropriate IBM Explorer data connection.

Generating Web methods and Web services

A very powerful feature of the re-usable data adapters is the ability to generate IIS Web methods for all of the data adapter commands or each individual command. This action translates into generating the appropriate C# and VB.NET class files and adding them to the chosen CLR Web project.

You can also elect to generate and deploy DB2 Web services for the data adapter or its individual commands. These Web services will be hosted by the DB2 embedded application server. An automatic WSDL and test Web client is generated for the deployed Web services.

Import and export

Re-usable data adapters are persisted alongside your IBM Explorer data connections user cache under %APPDATA%\IBM\vsnet\userCache.xml. You can export one or more data adapter definitions as XML files to your file system directly from the data adapters folder using the Export menu action. You can also import these exported data adapter definitions into your data connection using the Import menu action.

One interesting usage of this import/export feature is the ability to check in/out these data adapter definitions into source control management systems. The exported files may also be shared among other developers in your team.

Back to top

IBM DB2 Tools settings

The IBM DB2 Tools options are accessible through the Tools->Options->IBM DB2 Tools Visual Studio .NET menu. Using the standard Visual Studio >NET options dialog you can customize the various features of the DB2 Development Add-In.

Alternately, you can manually modify these options by accessing the %APPDATA%\IBM\vsnet\userOptions.xml file.

The IBM DB2 Tools options are broken down into categories, such as Code Generation, Data Access, Editor, Project, and z/OS options. Refer to the Options dialog or the userOptions.xml file for a complete list of options and their description.

Back to top

Conclusion

The new DB2 Development Add-In for Visual Studio .NET Stinger Technical Preview promises to be an exciting feature-packed release that demonstrates DB2's commitment to the .NET platform and the Visual Studio .NET IDE. This release targets application developers, database developers, DBAs and architects alike

You can now develop SQL and CLR procedures, SQL functions, tables, views, indexes, and triggers using feature-rich and easy to use scripting wizards. You can build these objects as part of your DB2 database project or directly from your IBM Explorer's data connections. Using the new re-usable data adapters, you can now quickly develop data bound win/web forms, Web methods, and Web services. These are some of the new features that will make your DB2 application development experience a very pleasant and productive one.

Acknowledgements

The DB2 Development Add-In would not be possible without the contribution of many talented people from across three IBM labs. From the San Francisco lab, special thanks to Kreg, Addi, Sonali, Eric, Kevin, Vasantha, Ajay, Kalpana, Veera, and Alex. From the Silicon Valley lab, special thanks to Connie, Nancy, Tammi, Chenhong, and Michael. And from the Toronto lab, special thanks to Brent, Nancy, Kelvin, Michael, Andrew, Gustavo, Leon, Shili, and Gene.

About the author

		Abdul Al-Azzawe is the DB2 Tools architect for Visual Studio .NET. He joined IBM in 1990 and worked in the Toronto lab for ten years as part of the DB2 engine development team with special focus on the Windows platform. In 2000, Abdul joined the IBM Silicon Valley Lab to architect the release of the DB2 integrated SQL debugger, the DB2 Development Center, and the DB2 Development Add-Ins for Visual Studio 6.0. In 2002, Abdul joined the IBM San Francisco team to architect the integration with Visual Studio .NET.

Rate this page

Please take a moment to complete this form to help us better serve you. Did the information help you to achieve your goal? Yes No Don't know   Please provide us with comments to help improve this page:   How useful is the information? 1 2 3 4 5 Not useful Extremely useful

Share this.... Digg this story del.icio.us Slashdot it!

Back to top