In order to download Xbase++ CTP4R1 build, please log into your customer account and go to Downloads->Community Previews. Of course, only customers with an active subscription and customers which have purchased Xbase++ in the last 12 months are eligible to participate in CTPs.
For details about this refresh, please consult the section "Release Information" of the Xbase++ 2.0 help file.
Finally, please keep in mind that CTP-related questions and/or issues are to be posted in the dedicated news group preview.xbase++.20 on our news server news.alaska-software.com
Xbase++ 2.0 CTP4R1 available for download!
Xbase++ 2.0 CTP4R1 available for download!
Nolberto Paulino
Regards
Regards
Re: Xbase++ 2.0 CTP4R1 available for download!
This is the README for Xbase++ 2.0 Community Technology Preview (CTP4)
Attention:
Behavior of pbuild changed in build #467. See section 8) for further information.
1) Focus of this release
This package contains the fourth installment in the Xbase++ 2.0 Community Technology Preview (CTP4). Further details about the contents as well as on how to get started with this build can be found on the start page of the online documentation included in this package.
Simply run the Xbase++ Workbench from your Start menu to begin working with this CTP. The corresponding menu item can be located by selecting All Programs and Alaska Software Xbase++ 2.0 (CTP), or by using the search option. The Workbench is your command center for developing with Xbase++, and contains all the features and tools required to build great desktop and web applications. The Workbench also provides access to the documentation and the examples included in this CTP.
2.1) Installation
Prerequisite: If you have installed an earlier preview build, you must uninstall this build before installing CTP4. After uninstalling, please make sure that the program files were successfully removed by the setup program. Any left-over files and directories in the folders c:\program files\alaska software (32-bit operating systems) and c:\program files (x86)\alaska software (64-bit operating systems) should be deleted prior to installing CTP4.
To install Xbase++ perform a double-click on the Microsoft Installer package xppctp4.msi. An installation wizard is started which guides you through the installation procedure.
2.1.1) Destination folder
Xbase++ is installed to two different locations on your harddrive. The Xbase++ Workbench, the Xbase++ development tools and other features are installed into the folder c:\program files\alaska software by default. On 64-bit operating systems, the destination folder is c:\program files (x86)\alaska software. Source files and examples are installed into the Documents folder of the current user. Under Windows Vista and later operating systems, sources and examples reside in the folder c:\users\<user name>\documents\xbase++.
2.1.2) Side-by-side installation
For using this preview build on computers which have an older Xbase++ version installed, we recommend to opt for a custom installation in the installation wizard's Choose Setup Type dialog. In addition, make sure that the environment is not changed by the installer. This can be done by unchecking the appropriate option in the Select Options dialog. Otherwise, the environment settings established by the package installer (eg. PATH, INCLUDE) may conflict with the ones used by the older Xbase++ version.
Note that the Xbase++ Workbench uses environment settings which can be configured in the IDE's Environment Options dialog. This allows to develop applications using this preview build while retaining your original environment used for production. To configure the environment used by the Workbench, select the menu item Tools -> Environment Options and then click on the Directories tab. Note that this environment will also be used by all processes started from within the Xbase++ Workbench! The commandline (CMD) opened via the Tools menu hence can be used as if the environment was configured for the whole machine. For example, invoking the project builder (PBUILD) in this commandline allows to build 2.0 projects even though Xbase++ 1.9 might be used as the development environment elsewhere on the computer.
3) Requirements
It is recommended to install a PostgreSQL server in order to be able to use the features included in this preview build. For developing web or connected mobile applications, a web server such as Microsoft Internet Information Server or Apache is required.
4) Obtaining and installing the PostgreSQL server
An installation archive for installing the PostgreSQL server is available as a separate archive and can be downloaded in the Community Preview section of the Alaska Software website. Please download the corresponding ZIP archive to your computer, and unpack its contents to your hard drive. Afterwards, double-click on the file postgresql-8.3.msi to begin the installation process.
5) Redistributables
The Community Technology Preview installation package does not install any redistributables into the runtime folder. This is by intention as the CTP is not suitable for usage in a production environment.
6.1) Internet Information Server (IIS) 7 or higher
In this section, you can find information about installing the IIS on the Windows operating system. Before you begin, please establish whether you are using a desktop or a server operating system. Vista, Windows 7 and later versions belong to the desktop operating systems group. Windows 2008 and later are server operating systems. The installation procedure differs sligthly between these groups and is outlined in individual sections below. Further information on IIS configuration and administration can be found on http://www.iis.net. Once the IIS web server is properly installed, the installation package will properly install the <CXP/> technology and will also apply proper configuration on the IIS web server for <CXP/> usage.
6.1.1) Vista and later
Open the Control Panel and select the item Programs. Under Programs and Features select Turn Windows features on or off. Then accomplish following steps. Please follow strictly the order below:
Ensure that the item Internet Information Service is selected. If this is not the case select the item Internet Information Service.
Also make sure that support for CGI executables is enabled which also enables the FastCGIModule. The CGI feature can be found at the following location in the feature tree:
=> Internet Information Services
=> World Wide Web Services
=> Application Development Features
=> CGI
6.1.2) Windows 2008 and later
Open the Server Manager and scroll down to Roles Summary. Click Add Roles. Select the role Web Server (IIS) and click Next. Ensure that the role service CGI is selected which also enables the FastCGIModule. The role service CGI can be found on the following location:
=> Web Server
=> Application Development
=> CGI
Click Close to complete the installation.
6.1.3) Verify IIS7 installation
Start a web browser on the machine the IIS7 web server has been installed. Then navigate to http://localhost. The IIS7 welcome page will be displayed if IIS7 was installed successfully.
7) Verify installation
PostgreSQL server: Use the PgAdmin administration utility to verify you can connect to the PostgreSQL server. To do this, run PgAgmin and right-click on your server in the tree view. In the context menu which opens, click Connect. Specify the credentials of the Postgres administrator user (usually postgres) and click Ok. Verify that the server state changes to “connected”.
Development platform: open your command line and type XPPLOAD VERSION [ENTER]. Verify the version numbers listed for the various runtime files match the one listed on the top of this README file.
<CXP/> infrastructure and IIS: Start a web browser and navigate to http://localhost/cxpinfo.cxp. The <CXP/> info page will be displayed if <CXP/> was installed successfully.
8) Support for projects with targets in multiple directories
Beginning with this version, complex project scenarios involving targets located in different directories are fully supported. This required changes in the way the targets and the source files included in a project are handled by the project builder pbuild. Consequently, you should verify your .xpj files for semantical correctness if your projects are laid out in the manner described.
Performing the following steps is not required for projects whose targets reside in the same folder as the project file (xpj)!
In previous versions, the location of the targets and the source files was specified relative to the folder which contained the project file. This approach had serious side-effects which basically made managing multi-target/multi-directory projects impossible. Beginning with this version, the location of the source files is specified relative to the corresponding target in the project file. This means that your existing projects may have to be modified before they can be used with this version.
This section explains the steps required to adapt your projects so that they can be used with the new Xbase++ version.
If you plan to use your project concurrently with an older Xbase++ version, create a copy of the file for usage with the older version.
Adapt the path of the source files in the project file
The following example shows an old-style project file with two targets, an executable (app.exe) and a DLL (helper.dll) which is located in a sub-folder:
[PROJECT]
Project.xpj
[Project.xpj]
app.exe
sub\helper.dll
[app.exe]
main.prg
common.prg
usual.ch
[sub\helper.dll]
sub\dllmain.prg
sub\resources.arc
sub\special.ch
common.prg
Because source files are now specified relative to the target, the relative path sub\(file) now expands to a folder which does not exist (sub\sub\(file)). Furthermore, assuming the DLL and the .exe target are built using the same source file common.prg, this source file must be prefixed with "..\" for the DLL target. This instructs the project builder to use the file in the target's parent directory. The required modifications are highlighted in the following example:
[PROJECT]
Project.xpj
[Project.xpj]
app.exe
sub\helper.dll
[app.exe]
main.prg
common.prg
usual.ch
[sub\helper.dll]
dllmain.prg
resources.arc
special.ch
..\common.prg
Use the new TARGET_DIR define to specify where a target shall be placed.
In previous versions, the project target location was used as some kind of deployment location to have all EXEs and DLLs of an Xbase++ project deployed at a single location which holds data files and other auxiliary files. With Xbase++ 2.0 the project target and the project binaries target location can be different. The benefit of this approach is that no intermediate files are created at the binary target location. Furthermore different targets can have source files with the same name without conflict. With previous versions, having different targets with identical prg/ch/arc filenames broke the dependency management of the Xbase++ Project builder. As a workaround “pbuild –a” was used, leading to unnecessary large build cycles.
The following example shows an old-style project file with the target app.exe that shall be created in the folder ..\bin:
[PROJECT]
Project.xpj
[Project.xpj]
..\bin\app.exe
[..\bin\app.exe]
app.prg
src\util.prg
To migrate an old-style Xbase++ project to a 2.0 project file simple remove the folder ..\bin from your project as well as project target node. Then add a TARGET_DIR definition to each of your project targets and specify the project target binary location using TARGET_DIR=..\bin
[PROJECT]
Project.xpj
[Project.xpj]
app.exe
[app.exe]
TARGET_DIR = ..\bin
app.prg
src\util.prg
9) Technical support
Alaska Software provides support for all issues related to this preview build and the Xbase++ 2.0 CTP through a dedicated news group. Please use the news group nntp://news.alaska-software.com/preview.xbase++.20 to discuss issues related to this preview build and the CTP. Because the news group is password protected, you need to configure your news reader to use the login information associated with your Alaska Software customer account when connecting to the news server.
Should you encounter problems with the installation routine, please post a message to the preview.xbase++.20 news group attaching the installer log file. To obtain the log file, run the installer from the command line using the following parameters. Please replace <installationpackage> with the name of the installation package:
msiexec /i <installationpackage>.msi /L*V install.log
10) How to contact Alaska
You can contact Alaska Software using the contact addresses outlined below:
Customers located in Europe, Middle east, Africa
E-mail: info@alaska-software.com
FAX: +49 (0)6196 779999-23
Phone: +49 (0)6196 779999-51
Mail: Alaska Software Inc., Germany
Industriestr. 9
65760 Eschborn
Germany
Customers located in the Americas, Asia, Pacific Rim, Australia use:
E-mail: info@alaska-software.com
FAX: +1 (646) 218-1281
Phone: +1 (646) 218-1280
Mail: Alaska Software, Inc.
1133 Broadway Suite 706
New York, NY 10010
U.S.A.
12) Trademarks
Xbase++, Xbase++ Workbench, Arctica, <CXP/> and the <CXP:xxx/> namespace logotype are trademarks or registered trademarks of Alaska Software.
Visual FoxPro, Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows Server 2012, IIS7 and ASP are trademarks or registered trademarks of Microsoft Corporation.
All other trademarks are trademarks or registered trademarks of the respective companies.
With best regards,
Your Xbase++ Team...
Attention:
Behavior of pbuild changed in build #467. See section 8) for further information.
1) Focus of this release
This package contains the fourth installment in the Xbase++ 2.0 Community Technology Preview (CTP4). Further details about the contents as well as on how to get started with this build can be found on the start page of the online documentation included in this package.
Simply run the Xbase++ Workbench from your Start menu to begin working with this CTP. The corresponding menu item can be located by selecting All Programs and Alaska Software Xbase++ 2.0 (CTP), or by using the search option. The Workbench is your command center for developing with Xbase++, and contains all the features and tools required to build great desktop and web applications. The Workbench also provides access to the documentation and the examples included in this CTP.
2.1) Installation
Prerequisite: If you have installed an earlier preview build, you must uninstall this build before installing CTP4. After uninstalling, please make sure that the program files were successfully removed by the setup program. Any left-over files and directories in the folders c:\program files\alaska software (32-bit operating systems) and c:\program files (x86)\alaska software (64-bit operating systems) should be deleted prior to installing CTP4.
To install Xbase++ perform a double-click on the Microsoft Installer package xppctp4.msi. An installation wizard is started which guides you through the installation procedure.
2.1.1) Destination folder
Xbase++ is installed to two different locations on your harddrive. The Xbase++ Workbench, the Xbase++ development tools and other features are installed into the folder c:\program files\alaska software by default. On 64-bit operating systems, the destination folder is c:\program files (x86)\alaska software. Source files and examples are installed into the Documents folder of the current user. Under Windows Vista and later operating systems, sources and examples reside in the folder c:\users\<user name>\documents\xbase++.
2.1.2) Side-by-side installation
For using this preview build on computers which have an older Xbase++ version installed, we recommend to opt for a custom installation in the installation wizard's Choose Setup Type dialog. In addition, make sure that the environment is not changed by the installer. This can be done by unchecking the appropriate option in the Select Options dialog. Otherwise, the environment settings established by the package installer (eg. PATH, INCLUDE) may conflict with the ones used by the older Xbase++ version.
Note that the Xbase++ Workbench uses environment settings which can be configured in the IDE's Environment Options dialog. This allows to develop applications using this preview build while retaining your original environment used for production. To configure the environment used by the Workbench, select the menu item Tools -> Environment Options and then click on the Directories tab. Note that this environment will also be used by all processes started from within the Xbase++ Workbench! The commandline (CMD) opened via the Tools menu hence can be used as if the environment was configured for the whole machine. For example, invoking the project builder (PBUILD) in this commandline allows to build 2.0 projects even though Xbase++ 1.9 might be used as the development environment elsewhere on the computer.
3) Requirements
It is recommended to install a PostgreSQL server in order to be able to use the features included in this preview build. For developing web or connected mobile applications, a web server such as Microsoft Internet Information Server or Apache is required.
4) Obtaining and installing the PostgreSQL server
An installation archive for installing the PostgreSQL server is available as a separate archive and can be downloaded in the Community Preview section of the Alaska Software website. Please download the corresponding ZIP archive to your computer, and unpack its contents to your hard drive. Afterwards, double-click on the file postgresql-8.3.msi to begin the installation process.
5) Redistributables
The Community Technology Preview installation package does not install any redistributables into the runtime folder. This is by intention as the CTP is not suitable for usage in a production environment.
6.1) Internet Information Server (IIS) 7 or higher
In this section, you can find information about installing the IIS on the Windows operating system. Before you begin, please establish whether you are using a desktop or a server operating system. Vista, Windows 7 and later versions belong to the desktop operating systems group. Windows 2008 and later are server operating systems. The installation procedure differs sligthly between these groups and is outlined in individual sections below. Further information on IIS configuration and administration can be found on http://www.iis.net. Once the IIS web server is properly installed, the installation package will properly install the <CXP/> technology and will also apply proper configuration on the IIS web server for <CXP/> usage.
6.1.1) Vista and later
Open the Control Panel and select the item Programs. Under Programs and Features select Turn Windows features on or off. Then accomplish following steps. Please follow strictly the order below:
Ensure that the item Internet Information Service is selected. If this is not the case select the item Internet Information Service.
Also make sure that support for CGI executables is enabled which also enables the FastCGIModule. The CGI feature can be found at the following location in the feature tree:
=> Internet Information Services
=> World Wide Web Services
=> Application Development Features
=> CGI
6.1.2) Windows 2008 and later
Open the Server Manager and scroll down to Roles Summary. Click Add Roles. Select the role Web Server (IIS) and click Next. Ensure that the role service CGI is selected which also enables the FastCGIModule. The role service CGI can be found on the following location:
=> Web Server
=> Application Development
=> CGI
Click Close to complete the installation.
6.1.3) Verify IIS7 installation
Start a web browser on the machine the IIS7 web server has been installed. Then navigate to http://localhost. The IIS7 welcome page will be displayed if IIS7 was installed successfully.
7) Verify installation
PostgreSQL server: Use the PgAdmin administration utility to verify you can connect to the PostgreSQL server. To do this, run PgAgmin and right-click on your server in the tree view. In the context menu which opens, click Connect. Specify the credentials of the Postgres administrator user (usually postgres) and click Ok. Verify that the server state changes to “connected”.
Development platform: open your command line and type XPPLOAD VERSION [ENTER]. Verify the version numbers listed for the various runtime files match the one listed on the top of this README file.
<CXP/> infrastructure and IIS: Start a web browser and navigate to http://localhost/cxpinfo.cxp. The <CXP/> info page will be displayed if <CXP/> was installed successfully.
8) Support for projects with targets in multiple directories
Beginning with this version, complex project scenarios involving targets located in different directories are fully supported. This required changes in the way the targets and the source files included in a project are handled by the project builder pbuild. Consequently, you should verify your .xpj files for semantical correctness if your projects are laid out in the manner described.
Performing the following steps is not required for projects whose targets reside in the same folder as the project file (xpj)!
In previous versions, the location of the targets and the source files was specified relative to the folder which contained the project file. This approach had serious side-effects which basically made managing multi-target/multi-directory projects impossible. Beginning with this version, the location of the source files is specified relative to the corresponding target in the project file. This means that your existing projects may have to be modified before they can be used with this version.
This section explains the steps required to adapt your projects so that they can be used with the new Xbase++ version.
If you plan to use your project concurrently with an older Xbase++ version, create a copy of the file for usage with the older version.
Adapt the path of the source files in the project file
The following example shows an old-style project file with two targets, an executable (app.exe) and a DLL (helper.dll) which is located in a sub-folder:
[PROJECT]
Project.xpj
[Project.xpj]
app.exe
sub\helper.dll
[app.exe]
main.prg
common.prg
usual.ch
[sub\helper.dll]
sub\dllmain.prg
sub\resources.arc
sub\special.ch
common.prg
Because source files are now specified relative to the target, the relative path sub\(file) now expands to a folder which does not exist (sub\sub\(file)). Furthermore, assuming the DLL and the .exe target are built using the same source file common.prg, this source file must be prefixed with "..\" for the DLL target. This instructs the project builder to use the file in the target's parent directory. The required modifications are highlighted in the following example:
[PROJECT]
Project.xpj
[Project.xpj]
app.exe
sub\helper.dll
[app.exe]
main.prg
common.prg
usual.ch
[sub\helper.dll]
dllmain.prg
resources.arc
special.ch
..\common.prg
Use the new TARGET_DIR define to specify where a target shall be placed.
In previous versions, the project target location was used as some kind of deployment location to have all EXEs and DLLs of an Xbase++ project deployed at a single location which holds data files and other auxiliary files. With Xbase++ 2.0 the project target and the project binaries target location can be different. The benefit of this approach is that no intermediate files are created at the binary target location. Furthermore different targets can have source files with the same name without conflict. With previous versions, having different targets with identical prg/ch/arc filenames broke the dependency management of the Xbase++ Project builder. As a workaround “pbuild –a” was used, leading to unnecessary large build cycles.
The following example shows an old-style project file with the target app.exe that shall be created in the folder ..\bin:
[PROJECT]
Project.xpj
[Project.xpj]
..\bin\app.exe
[..\bin\app.exe]
app.prg
src\util.prg
To migrate an old-style Xbase++ project to a 2.0 project file simple remove the folder ..\bin from your project as well as project target node. Then add a TARGET_DIR definition to each of your project targets and specify the project target binary location using TARGET_DIR=..\bin
[PROJECT]
Project.xpj
[Project.xpj]
app.exe
[app.exe]
TARGET_DIR = ..\bin
app.prg
src\util.prg
9) Technical support
Alaska Software provides support for all issues related to this preview build and the Xbase++ 2.0 CTP through a dedicated news group. Please use the news group nntp://news.alaska-software.com/preview.xbase++.20 to discuss issues related to this preview build and the CTP. Because the news group is password protected, you need to configure your news reader to use the login information associated with your Alaska Software customer account when connecting to the news server.
Should you encounter problems with the installation routine, please post a message to the preview.xbase++.20 news group attaching the installer log file. To obtain the log file, run the installer from the command line using the following parameters. Please replace <installationpackage> with the name of the installation package:
msiexec /i <installationpackage>.msi /L*V install.log
10) How to contact Alaska
You can contact Alaska Software using the contact addresses outlined below:
Customers located in Europe, Middle east, Africa
E-mail: info@alaska-software.com
FAX: +49 (0)6196 779999-23
Phone: +49 (0)6196 779999-51
Mail: Alaska Software Inc., Germany
Industriestr. 9
65760 Eschborn
Germany
Customers located in the Americas, Asia, Pacific Rim, Australia use:
E-mail: info@alaska-software.com
FAX: +1 (646) 218-1281
Phone: +1 (646) 218-1280
Mail: Alaska Software, Inc.
1133 Broadway Suite 706
New York, NY 10010
U.S.A.
12) Trademarks
Xbase++, Xbase++ Workbench, Arctica, <CXP/> and the <CXP:xxx/> namespace logotype are trademarks or registered trademarks of Alaska Software.
Visual FoxPro, Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows Server 2012, IIS7 and ASP are trademarks or registered trademarks of Microsoft Corporation.
All other trademarks are trademarks or registered trademarks of the respective companies.
With best regards,
Your Xbase++ Team...
Nolberto Paulino
Regards
Regards