.NET 2.0 Framework Support
Iron Speed Designer V3.0.3, V3.1.0 and later include preliminary support for .NET 2.0! Our full support for .NET 2.0 is just a few weeks away. In the meantime, you can start testing .NET 2.0 applications with V3.1. If you are developing applications that require deployment soon, we recommend you use V3.1 with .NET 1.1. You can migrate to .NET 2.0 as soon as V3.2 is released.

Direct support for Visual Studio 2005 is not yet available and will be released with our Version 3.2 release, coming soon.

When developing with Microsoft .NET 2.0, you need to have *both* .NET 1.1 and .NET 2.0 installed on your system to run Iron Speed Designer. If you only have .NET 2.0 installed, you will receive an error when starting Iron Speed Designer that your Product Key is invalid. This will be addressed in V3.2 as well.

No Migration Needed
Applications generated with Iron Speed Designer can run unmodified with Microsoft .NET Framework 1.1 or 2.0. Simply rebuild your application in Iron Speed Designer V3.0.3 or later (Build, Rebuild All) to make your applications compatible with either version of Microsoft .NET Framework. The generated application automatically recognizes the active version of Microsoft .NET Framework and adjusts itself as necessary.
Running Multiple Versions of Microsoft .NET Framework
If you have multiple versions of Microsoft .NET Framework on your system, you must designate the version of .NET Framework to use for your application. You can designate the version by running the aspnet_regiis.exe tool from the specific framework directory. For example, to run the 1.1 version of aspnet_regiis, you should be in the following directory:

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322

To run the 2.0 version of aspnet_regiis, you should be in the following directory:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Note: As new versions of Microsoft .NET Framework 2.0 get released, the 5-digit build number may change from 50727 to a higher number.

To designate the Microsoft .NET Framework 2.0 as the default framework for MyApp1:
1. Open a Command Prompt
2. CD C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
3. aspnet_regiis –sn “W3SVC/1/ROOT/MyApp1”
This will designate MyApp1 to run using Microsoft .NET Framework 2.0.

To switch back to Microsoft .NET Framework 1.1:
1. Open a Command Prompt
2. CD C:\WINDOWS\Microsoft.NET\Framework\ v1.1.4322
3. aspnet_regiis –sn “W3SVC/1/ROOT/MyApp1”

Please also review the online help on Running Multiple Versions of Microsoft .NET Framework.

Microsoft Visual Studio 2005 Support
Last Updated: November 1, 2005.

Direct support for Visual Studio 2005 is not yet available and will be released with our final support for .NET 2.0.

  • Generate Microsoft Visual Studio 2005 applications. Generate applications with the preferred class architecture and file organization for Microsoft Visual Studio 2005. Or, generate applications for the more established Visual Studio 2003.
  • Combined safe class and generated class files. Applications generated with the Visual Studio 2005 architecture combine your customizable (“safe” class) and generated code into a single file. Fewer code files make it easier to locate classes and add code customizations.
  • Run-time application compilation. Your generated applications are compiled dynamically at run-time by the .NET 2.0 framework.
  • Automatic definition of controls.
Microsoft SQL Server 2005 Support
Last Updated: November 10, 2005.

Iron Speed Designer V3.1 includes preliminary support for Microsoft SQL Server 2005. Iron Speed Designer maps all of the new data types to something reasonable. Microsoft SQL Server 2005 includes a new XML data type and also created a number of variations of existing types. All of these are handled properly by Iron Speed Designer and the generated application.

The XML data type is mapped to a Very Large String data type in Iron Speed Designer. While no XML validation is done by the generated application, you can enter XML in textboxes and it is saved appropriately. You can, if you like, request XML validation in the database. If you do, you specify an XML schema and your XML will be validated against that schema by your database, and an error message is reported if your XML does not map properly.

Known Issues
Last Updated: November 1, 2005.
  • Microsoft Visual Studio 2005 Migration Tool: When an existing application compatible with Visual Studio 2003 is opened in Visual Studio 2005, the Migration Tool tries to convert the project to a Visual Studio 2005 project. The migration tool is unable to convert all the controls to the new format and results in error messages indicating “unrecognized controls” and broken reference problems.
  • Delete Record: We have confirmed a problem with the Delete button on a Show Table page. We are investigating this problem at this time.


  Privacy Statement