Two projects, policy objects with the same name... Can you openboth at once?
So I have seen this in Designer 3.01, not yet seen it in 3.5, but this
can be quite annoying.
I have two projects, with identical named policy objects and drivers,
Dev and Prod, as is very common.
So I finished some work in Dev, and need to stage it out to Dev.
Open a policy object, say [Amce] MemberUid Maintenance in Dev, copy the
contents that I want out of it, switch to the Prod version, open the
same policy, so I can paste it in, and .... Well, Designer flips me
over to Dev copy of the rule, which I can tell because the DN of the
object has Dev or Prod in the tree name, as appropriate.
I have to paste to an intermediate text editor, close the Dev copy of
the policy, open the Prod, which then works, paste in.
As you can imagine, Staging this way is painful enough, but this just
makes it worse.
Anyone else seen this? I have not yet switched my big projects over to
3.5 due to shared content with 3.01 users via SVN, and I need to get
everybody on board at once...
PS: On the SVN checkin after a project is converted from 3.01 to 3.5,
does EVERYTHING get updated? Or just the regular changes? (I.e. If the
underlying file format changes, how does SVN handle that?)
Does that mean it is better to create a new SVN sub-repo once we move to
3.5?
|
Threaded Mode
