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

2018-08-28 Thread 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:

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

2018-08-28 Thread 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>

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

2018-08-28 Thread 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

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

2018-08-28 Thread 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

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

2018-08-28 Thread 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

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

2018-08-28 Thread 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

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

2018-08-28 Thread 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 >

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

2018-08-28 Thread 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