Re: Team Developer - Do all developers need to be on same minor version?

[Keisuke Miyako via 4D_Tech]

that is one of the beauties of components;

they can have object notation activated independent of the host's status. same 
for unicode mode.

as for the version being different, and not requiring recompilation, see 
documentation:

http://doc.4d.com/4Dv17/4D/17/Converting-databases-from-previous-versions.300-3743717.en.html

e.g.

Components4D v17 can open  v16, v15, v14, v13, v12 or v11 components, compiled 
or interpreted, directly without conversion or a confirmation dialog box. 
Remember that components are always opened in read-only mode. You do not need 
to recompile components but conversion to v17 is only possible for .4DB files 
and not for .4DC files.


> 2018/08/29 4:26、Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com>のメール:
>
>> I've noticed 4D often does not complain if the component is even from
>> a different major version (ie v15 - for example if the component was
>> purchased as a compiled project where you don't have the source code).



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Team Developer - Do all developers need to be on same minor version?

[Benedict, Tom via 4D_Tech]

Jeffrey Kain jeffrey.k...@gmail.com writes:

>Nope...

>If 4D makes a major change to the protocol they'll block it.  For deployment 
>we try to have matching versions always.
>
>> On Aug 28, 2018, at 2:24 PM, Dave Nasralla via 4D_Tech 
>> <4d_tech@lists.4d.com> wrote:
>>
>> One of our systems is developed with 4D Server (Team Developer) with
>> several coders connecting to make changes. If I move the Server from,
>> say v17.0 to v17.0 HF1 or a nightly build, do all the other developers
>> need to update their versions?

Ditto here. For Deployment we always match clients to server versions, even 
down to the build number.

Tom Benedict
Optum
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Team Developer - Do all developers need to be on same minor version?

[Dave Nasralla via 4D_Tech]

Thanks, Tim. We use the "Current version:" setting to for all the
clients to update to the same version as the server.

What do you do about components? 4D POP is a good example. Those are
not distributed as source code, but rather compiled .4DC files. As far
as I can tell there are no v17 versions on the 4D website.

dave
On Tue, Aug 28, 2018 at 1:01 PM Timothy Penner via 4D_Tech
<4d_tech@lists.4d.com> wrote:
>
> Keep in mind that 4D QA does not test mixing and matching different versions 
> of client and server - there are way too many permutations... QA only tests 
> the same build of the client with the same build of the server. It is 
> typically the expectation that the version of 4D Client will match 4D Server, 
> although, it is only enforced when there are specific changes to the protocol.
>
> I think the following tech note explains the situation and provides code 
> examples of how you can handle it via 4D code:
>
> Tech Note: Validation of Client Build Version
> http://kb.4d.com/assetid=77112
> PRODUCT: 4D Server | VERSION: 14.0 | PLATFORM: Mac & Win
> Published On: July 24, 2014
> This technical note will provide more insight on the changes between 4D 
> releases and the difference and significance between the versions and build 
> numbers. The code changes between different builds of 4D can cause errors and 
> unexpected behaviors may occur when running mismatched builds between clients 
> and servers. While 4D has a mechanism to prevent connection of mismatching 
> Clients and Server, it isn't strongly enforced for builds of the same 
> version. This Technical Note will also provide a technique and methods to 
> address this problem.
>
>
> -Tim
>
>
>
> **
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **



-- 
David Nasralla
Clean Air Engineering
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Team Developer - Do all developers need to be on same minor version?

[Jeffrey Kain via 4D_Tech]

Hardly ever.  Only if we make changes to it.

> On Aug 28, 2018, at 3:01 PM, Dave Nasralla via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Do you recompile each component with each
> deploy for minors?
> I've noticed 4D often does not complain if the component is even from
> a different major version (ie v15 - for example if the component was
> purchased as a compiled project where you don't have the source code).

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: Team Developer - Do all developers need to be on same minor version?

[Timothy Penner via 4D_Tech]

Keep in mind that 4D QA does not test mixing and matching different versions of 
client and server - there are way too many permutations... QA only tests the 
same build of the client with the same build of the server. It is typically the 
expectation that the version of 4D Client will match 4D Server, although, it is 
only enforced when there are specific changes to the protocol.

I think the following tech note explains the situation and provides code 
examples of how you can handle it via 4D code:

Tech Note: Validation of Client Build Version
http://kb.4d.com/assetid=77112
PRODUCT: 4D Server | VERSION: 14.0 | PLATFORM: Mac & Win
Published On: July 24, 2014
This technical note will provide more insight on the changes between 4D 
releases and the difference and significance between the versions and build 
numbers. The code changes between different builds of 4D can cause errors and 
unexpected behaviors may occur when running mismatched builds between clients 
and servers. While 4D has a mechanism to prevent connection of mismatching 
Clients and Server, it isn't strongly enforced for builds of the same version. 
This Technical Note will also provide a technique and methods to address this 
problem.


-Tim



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Team Developer - Do all developers need to be on same minor version?

[Dave Nasralla via 4D_Tech]

Thanks Jeff. For the Deployment, we use the server machine, so the
clients will always have matching versions (Windows and Mac).
What about the components? Do you recompile each component with each
deploy for minors?
I've noticed 4D often does not complain if the component is even from
a different major version (ie v15 - for example if the component was
purchased as a compiled project where you don't have the source code).

dave
On Tue, Aug 28, 2018 at 12:42 PM Jeffrey Kain via 4D_Tech
<4d_tech@lists.4d.com> wrote:
>
> Nope...
>
> If 4D makes a major change to the protocol they'll block it.  For deployment 
> we try to have matching versions always.
>
> > On Aug 28, 2018, at 2:24 PM, Dave Nasralla via 4D_Tech 
> > <4d_tech@lists.4d.com> wrote:
> >
> > One of our systems is developed with 4D Server (Team Developer) with
> > several coders connecting to make changes. If I move the Server from,
> > say v17.0 to v17.0 HF1 or a nightly build, do all the other developers
> > need to update their versions?
>
> **
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **



-- 
David Nasralla
Clean Air Engineering
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Team Developer - Do all developers need to be on same minor version?

[Jeffrey Kain via 4D_Tech]

Nope... 

If 4D makes a major change to the protocol they'll block it.  For deployment we 
try to have matching versions always.

> On Aug 28, 2018, at 2:24 PM, Dave Nasralla via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> One of our systems is developed with 4D Server (Team Developer) with
> several coders connecting to make changes. If I move the Server from,
> say v17.0 to v17.0 HF1 or a nightly build, do all the other developers
> need to update their versions?

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Team Developer - Do all developers need to be on same minor version?

[Dave Nasralla via 4D_Tech]

Hi all,

One of our systems is developed with 4D Server (Team Developer) with
several coders connecting to make changes. If I move the Server from,
say v17.0 to v17.0 HF1 or a nightly build, do all the other developers
need to update their versions?

4D does not complain when you connect, as long as your major version
is the same (not sure about, say 16.1 vs 16.2)

dave

-- 
David Nasralla
Clean Air Engineering
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**