<< My best wishes for the future of EWB! >>

Thanks Uli.  Couldn't have done it without yours, and many others, help.
The feedback was extremely valuable.

Tim Young
Elevate Software
www.elevatesoft.com

Rick,

<< Build 2 indeed fixes the install destination issue but it still wants to
use "Elevate Web Builder" as the default start menu folder which may
interfere with EWB1. I just added a 2 on the end during install so no
problem but may be worth looking at. >>

That's intentional, or at least, it's something that we just have to
tolerate for now because the build system won't allow it and it's a big
change to make it do so (it assumes that 2.00 is the same product name as
1.00, which is correct most of the time).  And no, it shouldn't hurt
anything since the menu items are all named differently.

Tim Young
Elevate Software
www.elevatesoft.com

Doc,

<< With the new version 2.0b2 that installs together with EWB1 I tried a new
clean install.
I choosed a different directory to the orignal installation and ran into the
following problem:
On IDE start I get the error:
Unexpected error encountered while building the component library
Cannot open file {OldPath}\WebLabels.wbs
I didn't find an ini file or a registry entry referring to {OldPath}.
The only solution at the moment is to use the {OldPath} again. >>

You'll have to make sure that you close the IDE, delete the ewbide.ini file
here:

C:\Users\<UserName>\AppData\Local\Elevate Software\Elevate Web Builder 2

and then restart the IDE.

Tim Young
Elevate Software
www.elevatesoft.com

On 24/06/15 03:56, Tim Young [Elevate Software] wrote:
> << Build 2 indeed fixes the install destination issue but it still wants
> to use "Elevate Web Builder" as the default start menu folder which may
> interfere with EWB1. I just added a 2 on the end during install so no
> problem but may be worth looking at. >>
>
> That's intentional, or at least, it's something that we just have to
> tolerate for now because the build system won't allow it and it's a big
> change to make it do so (it assumes that 2.00 is the same product name
> as 1.00, which is correct most of the time).  And no, it shouldn't hurt
> anything since the menu items are all named differently.
>

I understand Tim. However the "License Agreement" and "Release
Information" items are named the same for both EWB1 and EWB2. These
items display different information depending on the version so I
suspect that they would be overwritten if the same start menu folder is
used.

--
Rick

"Tim Young [Elevate Software]" wrote:
You'll have to make sure that you close the IDE, delete the ewbide.ini file
here:
C:\Users\<UserName>\AppData\Local\Elevate Software\Elevate Web Builder 2
and then restart the IDE.
________________________________________

Thank you, Tim, that did the trick for me, I didn't find this ini file before.
Shouldn't EWB2 do the changes itself? At first start from new destination it shows:
The library search paths spedified for the IDE do not reference the necessary component library units/interfaces. Would you like to have the IDE automatically reset the library search patchs (should be paths ?) to the default values that match your installation ?
I click Yes, but it seems not to do the job correctly. EWB1 did.

Rick wrote:

> are named the same for both EWB1 and EWB2.

My suggestion is to rename the EWB1 version's items or group. Most
users going forward will be EWB2 users, and only legacy users will be
using EWB1. I'll be moving my EWB1 use to a VM at some point for safe
maintenance until I can replace my code with EWB2 code. (And I really
like that I can have my web shop in EWB1 as the default but can run the
EWB2 version alongside on the server with a different page name!)

--

Matthew Jones

Rick,

<< I understand Tim. However the "License Agreement" and "Release
Information" items are named the same for both EWB1 and EWB2. These items
display different information depending on the version so I suspect that
they would be overwritten if the same start menu folder is
used. >>

Yes, I know.   This all came up the night before the release - no time to
change the build system, so for now we'll have to live with the minor
inconsistencies.

Tim Young
Elevate Software
www.elevatesoft.com

Doc,

<< Shouldn't EWB2 do the changes itself? >>

The setup has to leave the .ini file around in case it's a re-installation.

<<At first start from new destination it shows:
The library search paths spedified for the IDE do not reference the
necessary component library units/interfaces. Would you like to have the IDE
automatically reset the library search patchs (should be paths ?) to the
default values that match your installation ? >>

I've corrected that (patchs).

<< I click Yes, but it seems not to do the job correctly. EWB1 did. >>

What library/interface search path values did it use (Environment
Options/Component Library) ?

Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:
What library/interface search path values did it use (Environment
Options/Component Library) ?
_________________________________

As I wrote the error read:
Cannot open file {OldPath}\WebLabels.wbs
where {OldPath} was the the old installation directory + \library

Opening a form of a project in the IDE now leads to an error Access violation in ewbide.exe

When I got to Environment - Options - Component Library and look for the Search Paths they are shown as the correct (new) paths !
The problem lies in the later section of the ini file begining with [Component_TLabel]. Here the entries all have the old path.
This problem can be easily reproduced by uninstalling EWB2 and installing it to another location. Same her on my private PC, Office PC and Notebook.

Doc,

<< As I wrote the error read:
Cannot open file {OldPath}\WebLabels.wbs
where {OldPath} was the the old installation directory + \library >>

Sorry, missed that.

The problem here is that you're confusing the library search paths with the
installed component unit paths.

EWB will check the library search paths, but it only checks for the
existence of the installed standard library components by name.  I'll have
to see about adding path checking for the standard components, but for now
just do a search and replace on the ewbide.ini file to correct the component
paths.

Normally, this wouldn't be an issue with a new install.  It's only an issue
because the preview used a different installation path and so there was
left-over information from the preview in the ewbide.ini file that is
affecting the standard installation.  But, it could be an issue if someone
changes around their installation directory in the future, so I'll add a fix
for it.

Tim Young
Elevate Software
www.elevatesoft.com