.NET

EAServer 6.1 .NET Client Support

Mon, 05 Nov 2007 11:00:00 EST

The EAServer .NET client is one of the most important features in EAServer 6.1. This new feature enables .NET to communicate with EAServer components using IIOP. It provides underlying marshaling support for PowerBuilder's WinForm applications with EAServer and it's also a way to interoperate between .NET and J2EE distributed objects.

Sybase TechWave 2007: How to Develop a .NET Client/Server Application with PowerBuilder

Thu, 09 Aug 2007 13:15:00 EDT

This article is based on my presentation at TechWave 2007 and is intended for the beginner or moderately experienced PowerBuilder developer. I hope to share some of the useful information I've picked up as an application developer using PowerBuilder and EAServer.

Calling .NET Components from PowerBuilder

Sat, 07 Jul 2007 13:00:00 EDT

Back in August of 2006, I wrote an article about calling .NET components from PowerBuilder using COM wrappers (i.e., CCW). Since I was basing it on a registry entry approach, the technique demonstrated required the component to be added to the GAC, which in turn required that we create a strong name and sign the assembly (besides having it compiled as a COM-visible assembly).

SQL Anywhere 10 & DataWindow .NET 2.0 in an ASP Environment

Thu, 07 Jun 2007 11:00:00 EDT

Most of the applications we software developers build need to interact somehow with data from a database. The .NET Framework defined by Microsoft provides a rich set of objects to manage database interaction; these classes are collectively referred to as ADO.NET and the latest versions of DataWindow .NET (which is now version 2.01).

SQL Server and SODA

Fri, 16 Mar 2007 12:00:00 EDT

Over the past year, I've been discussing some of the various technologies found inside SQL Server 2005. Three of these technologies are CLR integration, HTTP endpoints, and Service Broker. (Articles on these topics were published, respectively, in the November 2005, March 2006, and November 2006 editions of the DNDJ.) Each of these is a powerful tool in its own right, and can be used to great effect in almost any SQL installation. When used together, however, they become much more powerful. Used together, these tools let SQL Server become an active participant in a service-oriented system. Not only can SQL Server provide the data used by these services but it can host the services themselves. This is an example of what Microsoft calls a 'Service-Oriented Database Architecture' or SODA, and it's another powerful capability of the SQL Server 2005 system.