Thanks to some quick (and cool) work by John Kaster, you can now share links/diggs/bookmarks with other bookmarking/tagging sites using the new “Share This” feature on CDN.  Click on the “Share This” plus sign to expand the list of tagging systems to share the link (the bitmap below shows the expanded list of sites).  See an article you like?  You can rate the article and share the link.

Notice the first item in “Share This“?  You can also easily email the article title, abstract, and URL to a friend.

Share This | Email this page to a friend

Thanks to some quick (and cool) work by John Kaster, you can now share links/diggs/bookmarks with other bookmarking/tagging sites using the new “Share This” feature on CDN.  Click on the “Share This” plus sign to expand the list of tagging systems to share the link (the bitmap below shows the expanded list of sites).  See an article you like?  You can rate the article and share the link.

Notice the first item in “Share This“?  You can also easily email the article title, abstract, and URL to a friend.

Share This | Email this page to a friend

Share This | Email this page to a friend

Share This | Email this page to a friend

Delphi for PHP Update 2 traz a VCL for PHP 1.2. Encontramos um problema na utilização de DataModules/Forms e componentes que tenham links com outros formulários. Por exemplo, si você utiliza um controle DataAccess em um DataModule que esteja associado com data aware irá receber uma excepción EPropertyNotFound.

A solução para este problema é fácil, faça o download do arquivo clases.inc.php através do link abaixo e copie no diretório VCL:

http://vcl4php.svn.sourceforge.net/viewvc/vcl4php/trunk/vcl/classes.inc.php?view=markup&pathrev=155

Share This | Email this page to a friend

Delphi for PHP Update 2 traz a VCL for PHP 1.2. Encontramos um problema na utilização de DataModules/Forms e componentes que tenham links com outros formulários. Por exemplo, si você utiliza um controle DataAccess em um DataModule que esteja associado com data aware irá receber uma excepción EPropertyNotFound.

A solução para este problema é fácil, faça o download do arquivo clases.inc.php através do link abaixo e copie no diretório VCL:

http://vcl4php.svn.sourceforge.net/viewvc/vcl4php/trunk/vcl/classes.inc.php?view=markup&pathrev=155

Share This | Email this page to a friend

VCL for PHP 1.2 viene incluido con Delphi for PHP Update 2. Hemos encontrado un problema en el uso de DataModules/Forms en componentes que contienen links con otros formularios. Por ejemplo, si usas un control  DataAccess en un DataModule y lo ligas con un control data aware de el formulario con el DataModule vas a recibir una excepción EPropertyNotFound.

La solución a este problema es fácil. Solo tienes que sustituir el archivo clases.inc.php en la carpeta VCL con el que encontraras en el siguiente link:

http://vcl4php.svn.sourceforge.net/viewvc/vcl4php/trunk/vcl/classes.inc.php?view=markup&pathrev=155

Share This | Email this page to a friend

VCL for PHP 1.2 viene incluido con Delphi for PHP Update 2. Hemos encontrado un problema en el uso de DataModules/Forms en componentes que contienen links con otros formularios. Por ejemplo, si usas un control  DataAccess en un DataModule y lo ligas con un control data aware de el formulario con el DataModule vas a recibir una excepción EPropertyNotFound.

La solución a este problema es fácil. Solo tienes que sustituir el archivo clases.inc.php en la carpeta VCL con el que encontraras en el siguiente link:

http://vcl4php.svn.sourceforge.net/viewvc/vcl4php/trunk/vcl/classes.inc.php?view=markup&pathrev=155

Share This | Email this page to a friend

VCL for PHP 1.2 ships along with Delphi for PHP Update 2, and we have found a problem you can get when working with datamodules/forms that link controls to another forms. For example, if you place data access controls on a datamodule and you link data aware controls in a form to that datamodule you will get an EPropertyNotFound exception.

The patch is easy, is just overwriting classes.inc.php inside vcl folder, you can get the file here:

http://vcl4php.svn.sourceforge.net/viewvc/vcl4php/trunk/vcl/classes.inc.php?view=markup&pathrev=155

If you click on the “download” link, you will get it.

Versão em Português clique aqui
Versión en Español clic aca

Share This | Email this page to a friend

VCL for PHP 1.2 ships along with Delphi for PHP Update 2, and we have found a problem you can get when working with datamodules/forms that link controls to another forms. For example, if you place data access controls on a datamodule and you link data aware controls in a form to that datamodule you will get an EPropertyNotFound exception.

The patch is easy, is just overwriting classes.inc.php inside vcl folder, you can get the file here:

http://vcl4php.svn.sourceforge.net/viewvc/vcl4php/trunk/vcl/classes.inc.php?view=markup&pathrev=155

If you click on the “download” link, you will get it.

Versão em Português clique aqui
Versión en Español clic aca

Share This | Email this page to a friend

In the effort to consolidate the dbExpress and BDP driver frameworks into one we needed to enhance the metadata for dbexpress.  The dbExpress 3 metadata is written in C.  The BDP metadata is written in C#.  The dbExpress metadata was not rich enough for the tooling infrastructure we want to support in the future for both win32 and .NET.  Our solution was to implement new metadata for all drivers in Object Pascal.  This can be compiled for both win32 and .NET.

On the .net side this is also the metadata we use for our ADO.NET 2.0 AdoDbxClient provider which allows any of our dbExpress drivers to be surfaced as an ADO.NET 2.0 provider.

Another interesting aspect is that the new metadata is provider based making it pluggable.  This allows other dbExpress driver implementations that use the same back end to reuse our metadata implementation.  It also allows us to potentially support other vendor’s ADO.NET drivers with our tooling.  For example, the DataExplorer can use Microsoft’s ADO.NET driver with our MS-SQL metadata provider.

The provider is specified in the dbxdrivers.ini.  If this entry does not exist in the dbxdrivers.ini file, the metadata request will be passed on to the underlying driver.  In the case of our dbxDrivers, you will get dbExpress 3 metadata support.

I’d say about 25% of the dbExpress driver implementations deal with metadata support.  There is already a large amount of framework implementation shared for all drivers.  With the new metadata we are one more significant step towards a 100% Object Pascal solution.  Object Pascal provides us with the portability we need to support win32, .NET and eventually win64.

The new metadata commands are documented in the DbxCommon.pas.  There are also several classes with constants and documentation for the new metadata tables and their columns.  The new metadata extends dbExpress 3 metadata with support for retrieving:  data types, views, synonyms, catalogs, schemas, procedure source, package source, package procedure parameters, roles, and reserved words.

We also now provide driver independent support for editing metadata.  Support for creating sql dialect sensitive create, alter, drop statements was initially only provided for tooling purposes in the DataExplorer.  However we have now also exposed a DbxMetaDataProvider class that surfaces this capability for applications.  This will make a slight increase in the size of your application since you will need to include the metadata writers.  The ability to generically create tables is useful for many applications.  The interface allows you to describe what a table and its columns should look like.  This description is passed to the TdbxMetaDataProvider.CreateTable.  Here is a very simple example that shows how to create a table with an int32 column named "C1", a decimal with a precision of 10 and scale of 2 named "C2" and a character based column with a precision of 32 named "C3". 

var
  MetaDataTable: TDBXMetaDataTable;
  DataGenerator: TDbxDataGenerator;
  Command: TDBXCommand;
  Row: Integer;
begin
  MetaDataTable := TDBXMetaDataTable.Create;

  MetaDataTable.TableName := ‘QCXXX_TABLE’;
  MetaDataTable.AddColumn(TDBXInt32Column.Create(’C1′));
  MetaDataTable.AddColumn(TDBXDecimalColumn.Create(’C2′, 10, 2));
  MetaDataTable.AddColumn(TDBXUnicodeCharColumn.Create(’C3′, 32));
  MetaDataProvider.CreateTable(MetaDataTable);

TDBXInt32Column, DecimalColumn and UnicodeCharColumn are pre fabricated class extensions of the TDBXMetaDataColumn class.  The TDBXMetaDataColumn class contains several column properties including data type, precision, scale, is fixed length, is Unicode, etc.  You can create your own pre fabricated classes for column types common to your application.  The MetaDataProvider will find the best possible match of each TDBXMetaDataColumn to the underlying type system of the targeted database backend.

Share This | Email this page to a friend

In the effort to consolidate the dbExpress and BDP driver frameworks into one we needed to enhance the metadata for dbexpress.  The dbExpress 3 metadata is written in C.  The BDP metadata is written in C#.  The dbExpress metadata was not rich enough for the tooling infrastructure we want to support in the future for both win32 and .NET.  Our solution was to implement new metadata for all drivers in Object Pascal.  This can be compiled for both win32 and .NET.

On the .net side this is also the metadata we use for our ADO.NET 2.0 AdoDbxClient provider which allows any of our dbExpress drivers to be surfaced as an ADO.NET 2.0 provider.

Another interesting aspect is that the new metadata is provider based making it pluggable.  This allows other dbExpress driver implementations that use the same back end to reuse our metadata implementation.  It also allows us to potentially support other vendor’s ADO.NET drivers with our tooling.  For example, the DataExplorer can use Microsoft’s ADO.NET driver with our MS-SQL metadata provider.

The provider is specified in the dbxdrivers.ini.  If this entry does not exist in the dbxdrivers.ini file, the metadata request will be passed on to the underlying driver.  In the case of our dbxDrivers, you will get dbExpress 3 metadata support.

I’d say about 25% of the dbExpress driver implementations deal with metadata support.  There is already a large amount of framework implementation shared for all drivers.  With the new metadata we are one more significant step towards a 100% Object Pascal solution.  Object Pascal provides us with the portability we need to support win32, .NET and eventually win64.

The new metadata commands are documented in the DbxCommon.pas.  There are also several classes with constants and documentation for the new metadata tables and their columns.  The new metadata extends dbExpress 3 metadata with support for retrieving:  data types, views, synonyms, catalogs, schemas, procedure source, package source, package procedure parameters, roles, and reserved words.

We also now provide driver independent support for editing metadata.  Support for creating sql dialect sensitive create, alter, drop statements was initially only provided for tooling purposes in the DataExplorer.  However we have now also exposed a DbxMetaDataProvider class that surfaces this capability for applications.  This will make a slight increase in the size of your application since you will need to include the metadata writers.  The ability to generically create tables is useful for many applications.  The interface allows you to describe what a table and its columns should look like.  This description is passed to the TdbxMetaDataProvider.CreateTable.  Here is a very simple example that shows how to create a table with an int32 column named "C1", a decimal with a precision of 10 and scale of 2 named "C2" and a character based column with a precision of 32 named "C3". 

var
  MetaDataTable: TDBXMetaDataTable;
  DataGenerator: TDbxDataGenerator;
  Command: TDBXCommand;
  Row: Integer;
begin
  MetaDataTable := TDBXMetaDataTable.Create;

  MetaDataTable.TableName := ‘QCXXX_TABLE’;
  MetaDataTable.AddColumn(TDBXInt32Column.Create(’C1′));
  MetaDataTable.AddColumn(TDBXDecimalColumn.Create(’C2′, 10, 2));
  MetaDataTable.AddColumn(TDBXUnicodeCharColumn.Create(’C3′, 32));
  MetaDataProvider.CreateTable(MetaDataTable);

TDBXInt32Column, DecimalColumn and UnicodeCharColumn are pre fabricated class extensions of the TDBXMetaDataColumn class.  The TDBXMetaDataColumn class contains several column properties including data type, precision, scale, is fixed length, is Unicode, etc.  You can create your own pre fabricated classes for column types common to your application.  The MetaDataProvider will find the best possible match of each TDBXMetaDataColumn to the underlying type system of the targeted database backend.

Share This | Email this page to a friend

We’ve been going about 90 miles an hour this summer working to get the next release of BDS studio out.  On the database side of the house there are a ton of new features.  I don’t know what we were thinking putting so much into the product and shipping at the end of the summer.  The good news is that there’s lots of cool features to talk about now.  In this blog I’m going to talk about one of the big features – Blackfish SQL 8.0.

Blackfish SQL is an embeddable database which is now a feature of Delphi.  Delphi Pro, Enterprise and Architect customers have unlimited deployment licenses of Blackfish SQL.  There are file size and user limits, but these limits should be acceptable for a large number of smaller scale applications.  Deployment licenses can be purchased if the user or file size limits need to be increased.

The Blackfish SQL database was written completely in Java for its first 7 revisions.  The database product was called JDataStore then.  A couple years ago or so Jens Ole created a Java to C# translator so that we could create a .NET version of the database.  The bulk of the database kernel, query engine and driver layers are written in Java with minimal dependencies on runtime classes.  Since at its core the C# language and .NET runtime is semantically very similar to Java’s, and because we had minimal runtime dependencies, the Java to .NET translator came together fairly quickly (well, much faster than rewriting the database).  This translator allows us to continue extending the internals in Java and then automatically translate to C# to produce the .NET edition.  There is a very high degree of compatibility between the .NET and Java editions.  .NET clients can connect to Java servers and visa versa.  The file format is compatible as well.

We also have introduced a 100% Object Pascal DBX4 driver that can connect to Blackfish SQL called DbxClient.  Source code for this driver is included in the product.  It can be compiled for either win32 or .NET. Because it is 100% Object Pascal and requires no client library you can even build “big fat win32 exes” that connect to either a Blackfish SQL for windows (.NET) or Blackfish SQL for Java server.  No additional client library is required.  This is a perfect example of why I really like seeing database drivers implemented in Object Pascal.  This allows us to use the same code for both .NET and win32 as packages or linked directly into the exe.  When there is 64 bit Delphi we can reuse the same code yet again.  What other language and runtime can do this as elegantly as Delphi (or even at all)?  To me this is one of the many reasons Delphi just flat out rocks.

What else is cool about DbxClient?  Well, its not called the Blackfish SQL DBX4 driver.  It’s a driver that remotes the interfaces of the DBX4 framework.  It can connect to anything that understands its JSON based streaming protocol.  Today only the Blackfish SQL for windows and Blackfish SQL for Java support this protocol.  However, I’d really like to see if we can leverage this technology as a connectivity solution for DataSnap as well.  I view a database driver is a fairly capable RPC layer.  The streaming protocol is currently a hybrid where it will mix binary data with text data.  In the future we’d also like to implement a full text mode to support other transports like http(s).  The binary hybrid mode is more compact and performant.

Another interesting aspect of the DbxClient is the source code.  I already mentioned that it was 100% Object Pascal compliable for win32, .NET and someday the win64 platform.  If you look at the source code you will notice that some units are located under a pas directory tree and some are located under an xpas directory tree.  The source code in the pas directories was authored in Delphi.  The source code in the xpas was not.  Jens Ole has taught his Java to C# translator a new trick.  It now can also translate from Java to Object Pascal.  Its pretty hard to tell it came from Java though.  Typical Delphi naming conventions are applied as part of the translation process and multiple related classes are packaged into single Delphi units.  Often times a Java package of classes logically maps to a Delphi unit.  Why do we do this?  By using Java as “pseudo code”, we can maintain this JSON based streaming protocol on 3 different platforms:  Delphi/C++ win32/win64, .NET and Java.  Keep in mind we have a .NET and a Java server at the other end of the DbxClient that need to be able to interpret the same JSON streaming protocol.  This same technique was also applied for the new DBX4 metadata.

DBXClient also has some DBX4 extensions.  It is the first dbExpress driver we have created that supports streaming blobs and parameter metadata.  You don’t need to read the entire contents of the blob in one shot.  This is not that big of a deal for things like pictures.  But for things like video streams you really want to be able to stream the blob.  The DBXClient also supports parameter metadata.   If you don’t add parameters to the command, it will add them for you when you prepare the statement.  This saves coding and is less error prone than creating parameter objects yourself.  I’d like to make these important capabilities part of a “DBX5” in the future.

That’s enough for one blog…

Share This | Email this page to a friend

We’ve been going about 90 miles an hour this summer working to get the next release of BDS studio out.  On the database side of the house there are a ton of new features.  I don’t know what we were thinking putting so much into the product and shipping at the end of the summer.  The good news is that there’s lots of cool features to talk about now.  In this blog I’m going to talk about one of the big features – Blackfish SQL 8.0.

Blackfish SQL is an embeddable database which is now a feature of Delphi.  Delphi Pro, Enterprise and Architect customers have unlimited deployment licenses of Blackfish SQL.  There are file size and user limits, but these limits should be acceptable for a large number of smaller scale applications.  Deployment licenses can be purchased if the user or file size limits need to be increased.

The Blackfish SQL database was written completely in Java for its first 7 revisions.  The database product was called JDataStore then.  A couple years ago or so Jens Ole created a Java to C# translator so that we could create a .NET version of the database.  The bulk of the database kernel, query engine and driver layers are written in Java with minimal dependencies on runtime classes.  Since at its core the C# language and .NET runtime is semantically very similar to Java’s, and because we had minimal runtime dependencies, the Java to .NET translator came together fairly quickly (well, much faster than rewriting the database).  This translator allows us to continue extending the internals in Java and then automatically translate to C# to produce the .NET edition.  There is a very high degree of compatibility between the .NET and Java editions.  .NET clients can connect to Java servers and visa versa.  The file format is compatible as well.

We also have introduced a 100% Object Pascal DBX4 driver that can connect to Blackfish SQL called DbxClient.  Source code for this driver is included in the product.  It can be compiled for either win32 or .NET. Because it is 100% Object Pascal and requires no client library you can even build “big fat win32 exes” that connect to either a Blackfish SQL for windows (.NET) or Blackfish SQL for Java server.  No additional client library is required.  This is a perfect example of why I really like seeing database drivers implemented in Object Pascal.  This allows us to use the same code for both .NET and win32 as packages or linked directly into the exe.  When there is 64 bit Delphi we can reuse the same code yet again.  What other language and runtime can do this as elegantly as Delphi (or even at all)?  To me this is one of the many reasons Delphi just flat out rocks.

What else is cool about DbxClient?  Well, its not called the Blackfish SQL DBX4 driver.  It’s a driver that remotes the interfaces of the DBX4 framework.  It can connect to anything that understands its JSON based streaming protocol.  Today only the Blackfish SQL for windows and Blackfish SQL for Java support this protocol.  However, I’d really like to see if we can leverage this technology as a connectivity solution for DataSnap as well.  I view a database driver is a fairly capable RPC layer.  The streaming protocol is currently a hybrid where it will mix binary data with text data.  In the future we’d also like to implement a full text mode to support other transports like http(s).  The binary hybrid mode is more compact and performant.

Another interesting aspect of the DbxClient is the source code.  I already mentioned that it was 100% Object Pascal compliable for win32, .NET and someday the win64 platform.  If you look at the source code you will notice that some units are located under a pas directory tree and some are located under an xpas directory tree.  The source code in the pas directories was authored in Delphi.  The source code in the xpas was not.  Jens Ole has taught his Java to C# translator a new trick.  It now can also translate from Java to Object Pascal.  Its pretty hard to tell it came from Java though.  Typical Delphi naming conventions are applied as part of the translation process and multiple related classes are packaged into single Delphi units.  Often times a Java package of classes logically maps to a Delphi unit.  Why do we do this?  By using Java as “pseudo code”, we can maintain this JSON based streaming protocol on 3 different platforms:  Delphi/C++ win32/win64, .NET and Java.  Keep in mind we have a .NET and a Java server at the other end of the DbxClient that need to be able to interpret the same JSON streaming protocol.  This same technique was also applied for the new DBX4 metadata.

DBXClient also has some DBX4 extensions.  It is the first dbExpress driver we have created that supports streaming blobs and parameter metadata.  You don’t need to read the entire contents of the blob in one shot.  This is not that big of a deal for things like pictures.  But for things like video streams you really want to be able to stream the blob.  The DBXClient also supports parameter metadata.   If you don’t add parameters to the command, it will add them for you when you prepare the statement.  This saves coding and is less error prone than creating parameter objects yourself.  I’d like to make these important capabilities part of a “DBX5” in the future.

That’s enough for one blog…

Share This | Email this page to a friend

Almost seems like it was yesterday we announced the JGears, but it was actually almost a month ago. You’ll find some good resources for the JGears on the JGear support pages.

We just announced RAD Studio 2007 the other day, which will be available very soon. I’ve been deep down in producing the Partner DVD.

Very soon, as you may have seen indications of, there will soon be some noise on the Ruby on Rails front. Less than two weeks until that Berlin trip.

Share This | Email this page to a friend

Almost seems like it was yesterday we announced the JGears, but it was actually almost a month ago. You’ll find some good resources for the JGears on the JGear support pages.

We just announced RAD Studio 2007 the other day, which will be available very soon. I’ve been deep down in producing the Partner DVD.

Very soon, as you may have seen indications of, there will soon be some noise on the Ruby on Rails front. Less than two weeks until that Berlin trip.

Share This | Email this page to a friend

• You need to rename the units in the uses clause in all pas-files. Usually you only need to remove the Q infront of the unit name.
• For forms you need to change the extension of the xfm file to dfm. Change the $R directive in the pas-file to include the dfm file instead.
• Properties should be 99% compatible with current version. Open each converted form in Delphi to verify this. If there is any problem, click ignore and make a note so you can investigate if it demands any adjustments.

If you have more tips and trix, drop a comment in my new blog at blog.fredrikhaglund.se

Share This | Email this page to a friend

• You need to rename the units in the uses clause in all pas-files. Usually you only need to remove the Q infront of the unit name.
• For forms you need to change the extension of the xfm file to dfm. Change the $R directive in the pas-file to include the dfm file instead.
• Properties should be 99% compatible with current version. Open each converted form in Delphi to verify this. If there is any problem, click ignore and make a note so you can investigate if it demands any adjustments.

If you have more tips and trix, drop a comment in my new blog at blog.fredrikhaglund.se

Share This | Email this page to a friend

So, there’s a little room in my schedule for meetups, or impromptu chats over beer. Possibly even in Gothenburg - a 4.5 hour train ride from my dad’s house.

You tell me, fellow Swedes - what shall we do? Chat about RAD Studio 2007? Ruby on Rails? JGears? JBuilder? InterBase? BlackFish? Let me know.

Share This | Email this page to a friend

So, there’s a little room in my schedule for meetups, or impromptu chats over beer. Possibly even in Gothenburg - a 4.5 hour train ride from my dad’s house.

You tell me, fellow Swedes - what shall we do? Chat about RAD Studio 2007? Ruby on Rails? JGears? JBuilder? InterBase? BlackFish? Let me know.

Share This | Email this page to a friend

Hoje anunciamos nosso novo Studio, grandes novidades e mudanças nesta versão, claro que as novidades e principalmente as mudanças foram para melhor.

As novidades desta versão são:

• 3 linguagens em 1 IDE - Delphi for Win32, C++ e Delphi for .NET
• Delphi for .NET trazendo suporte para ASP.NET 2.0 e VCL.NET 2.0
• Suporte a generics
• ECO IV com total suporte a VCL.NET
• ADODbx client - com total suporte a .NET 2.0
• Blackfish SQL um novo banco de dados 100% gerenciado, ou seja, baseado em .NET, com isso você poderá escrever triggers e stored procedures em Delphi.NET
• dbExpress IV integrado a ASP.NET, isso significa que você agora pode usar dbExpress and VCL.NET e ASP.NET
• VCL.NET suportada em Windows Vista e em .NET 2.0

Esteja atento ao Developer Network Brasil (http://dn.codegear.com/br) em breve artigos e informações serão publicados.

Se quiser conhecer em detalhes os novos recursos do RAD Studio 2007 ao vivo, o BorCon 2007 terá diversas apresentações, faça já sua inscrição.

Share This | Email this page to a friend

Hoje anunciamos nosso novo Studio, grandes novidades e mudanças nesta versão, claro que as novidades e principalmente as mudanças foram para melhor.

As novidades desta versão são:

• 3 linguagens em 1 IDE - Delphi for Win32, C++ e Delphi for .NET
• Delphi for .NET trazendo suporte para ASP.NET 2.0 e VCL.NET 2.0
• Suporte a generics
• ECO IV com total suporte a VCL.NET
• ADODbx client - com total suporte a .NET 2.0
• Blackfish SQL um novo banco de dados 100% gerenciado, ou seja, baseado em .NET, com isso você poderá escrever triggers e stored procedures em Delphi.NET
• dbExpress IV integrado a ASP.NET, isso significa que você agora pode usar dbExpress and VCL.NET e ASP.NET
• VCL.NET suportada em Windows Vista e em .NET 2.0

Esteja atento ao Developer Network Brasil (http://dn.codegear.com/br) em breve artigos e informações serão publicados.

Se quiser conhecer em detalhes os novos recursos do RAD Studio 2007 ao vivo, o BorCon 2007 terá diversas apresentações, faça já sua inscrição.

Share This | Email this page to a friend

Just in case you missed all the other CodeGear bloggers, the press release, and the article on the CodeGear Developer Network… I’ll go ahead an mention it here;  CodeGear has announced RAD Studio 2007.  If you’ve been waiting for the next studio release to upgrade, now is the time to do it.  This release will also include Update 3 for the previously released Delphi and C++Builder 2007.  If you already have Studio Level Software Assurance, you’ll be getting this release automatically.  If you still haven’t signed up for SA, now is the time to do it.  By maintaining your annual SA account, you are assured that you’ll have all the latest versions and features available.

While RAD Studio 2007 includes many updates for the Delphi and C++Builder 2007 personalities, the main addition is the Delphi for .NET personality.  This includes the new language feature, parameterized types (generics).  This allows you to both create and consume generic data types as supported by the latest .NET 2.0 framework.  And updated version of VCL for .NET is included with all the same level of support for Windows Vista.  You can also create ASP.NET web applications.

Ok.. the commercial is over…

Share This | Email this page to a friend

Just in case you missed all the other CodeGear bloggers, the press release, and the article on the CodeGear Developer Network… I’ll go ahead an mention it here;  CodeGear has announced RAD Studio 2007.  If you’ve been waiting for the next studio release to upgrade, now is the time to do it.  This release will also include Update 3 for the previously released Delphi and C++Builder 2007.  If you already have Studio Level Software Assurance, you’ll be getting this release automatically.  If you still haven’t signed up for SA, now is the time to do it.  By maintaining your annual SA account, you are assured that you’ll have all the latest versions and features available.

While RAD Studio 2007 includes many updates for the Delphi and C++Builder 2007 personalities, the main addition is the Delphi for .NET personality.  This includes the new language feature, parameterized types (generics).  This allows you to both create and consume generic data types as supported by the latest .NET 2.0 framework.  And updated version of VCL for .NET is included with all the same level of support for Windows Vista.  You can also create ASP.NET web applications.

Ok.. the commercial is over…

Share This | Email this page to a friend

We have added a new community - Ruby, where we will soon start posting Ruby and Rails articles.

As you may know, we announced that we are working on a Ruby on Rails IDE product at RailsConf in Portland, OR earlier this year. You will see a lot more of what we have been working on shortly. A good place to start looking (if you have the chance) is our booth at RailsConf Europe in Berlin. The booth is open September 18th and 19th, and I will be in it.

Stay tuned to the new Ruby community for lots of cool stuff over the next couple of weeks.

Share This | Email this page to a friend