We use PDSOE (OE 11.5.1) with Perforce.
We have a very weird scenario in play:
One programmer created a GUI4.Net form (A) with a particular layout and checked it in (v.1).
Another retrieved it (A1) from the repository to build a test release.
The first guy then changed this program and checked it in (v.2). Then he copied it to another program to another program (B) and made significant changes to B. He then checked B in (v.1).
If I retrieve the latest version form the repository, I get A2 and B1. When I open it in the designer, I get the expected layout.
But when the programmer that created the programs opens either one or run the system, he gets the layout and behaviour of B1 where we expect A2.
When the person who built the test release check it out, he gets A2 and B1, but when he opens it in PDSOE, he gets the layout of A1 where we expect A2.
If we compare the source on the three machines, it is identical.
Did anybody see this behaviour before? Can anybody explain it? Does anybody know how we resolve it?
I would suggest the team members that are seeing previous versions of the file ensure that the editor windows for the files in question are first closed in PDSOE. Next, right-click in the Project View and select 'Refresh'. Finally, as a precaution, restart the project AVM.
-------- [collapse]Original message -----[/collapse]
PDSOE has some weird caching issues - I'd suggest doing an F5 to
refresh the project source and see what that does.
On Fri, Jul 3, 2015 at 7:33 AM, Simon L. Prinsloo
> When the person who built the test release check it out, he gets A2 and B1,
> but when he opens it in PDSOE, he gets the layout of A1 where we expect A2.
> If we compare the source on the three machines, it is identical.
> Did anybody see this behaviour before? Can anybody explain it? Does anybody
> know how we resolve it?
Tim Kuehn: Senior Consultant - TDK Consulting Services
President - Ontario PUG
Program Committee Chair - PUG Challenge Americas,
Course Instructor: Intro to OO Concepts for Procedural Programmers