Recommend Xbase 2.0CTP3 setup using Express++

[Cliff Wiernik]

Roger,

What do you recommend as the best setup for a side by side setup with Xbase++ 2.0 CTP3.

For 1.9 build 355, I have my directory in program files (x86)\alaska and I use c:\exp for express. I have a folder for build 255 and 258 that I swap back and forth between exp as I complete testing 258.

For Xbase++ 2.0, they have on the alaska newsgroup a procedure for side by side 1.9 and 2.0, and it requires use of the Xbase++ Workbench for 2.0. What to you recommend as normally we have not been working inside the Xbase++ ide for version 1.9/express programming.

Cliff.

[Auge_Ohr]

hi,

as i understand CTP VX is using it´s own Envioment and Registry Settings

"HKEY_CURRENT_USER\Software\Alaska Software\Visual Xbase++\2.0\Directories"
"HKEY_CURRENT_USER\Software\Alaska Software\Visual Xbase++\2.0 CTP\Directories"

when edit / build / run from inside CTP VX it will use those Path.

Problem : when start from CMD Box it will use System Envioment

"HKEY_CURRENT_USER\Environment"

"INCLUDE"
"LIB"
"PATH"
"XPPROOT"
"XPPRESOURCE"

my Solution is to store Envioment Value in DBF and "write" it to "HKEY_CURRENT_USER\Environment" ... but it need re-boot. i did have present my Tool "VxPath" in Alaska Newsgroup.xbase20 1/2 Year ago. also read what Andreas have written at that time.

[rdonnay]

Cliff -

I treat Xbase++ 2.0 in the same way I have dealt with all other previous Xbase++ releases.
I simply have a set of batch files that sets my path, lib and include statements, even though Xbase++ 2.0 is installed differently than other releases.

I have tried Visual Xbase++ in the past and found that it did not improve my development time. It offers nothing to me that I can pass on to you or other eXpress++ customers. It does not improve the end application that we sell to our customers, and that is the most important thing. What I will use in Xbase++ 2.0 are new functions, the new SQL stuff, and CX/P.

Xbase++ 2.0, in my opinion, was not really motivated by the needs of the Clipper community or the existing Xbase++ community. Instead, it was motivated by the needs of the FoxPro community, and (ironically) none of the FoxPro developers at the last conference chose to attend the Alaska presentations. Steffen Pirsig has high hopes that the Fox community will jump on board like the Clipper developers did, but this is going to be a tough sell for him. These guys have been assimilated by Microsoft and they don't know how to think independently. Can you imagine any one of them writing code the way we write code in eXpress++? Never in a million years. They want their drag and drop tools and their IDE's.

I will stick with the eXpress++ method and WTF and will develop supportable applications faster than any of the .NET guys or the FoxPro guys.

[Cliff Wiernik]

I will do something similarly. Instead, I keep the same environment variable settings, but simple rename the directories via a batch file.

Will continue that I guess until I find a need to change.

Cliff.

[bwolfsohn]

Cliff, i did that, and found it was much more confusing.. if i needed to change a file in a specific version, wasn't always quickly apparent which file it was...

[Cliff Wiernik]

Brian,

Since I was working with only one Alaska version currently, was not really a problem. Each express version is its own directory. Worked okay when we were in the 1.8/1,9/1.9sl1 stage of testing Xbase++ also.

Each version is still stand alone, just like roger's method. But instead of changing pointers via a batch file, it just renames the directory. I will look at Roger's methodology so see how it works in our processing.

Thanks for the comments and have a great new year.

Cliff.