While we are still working in V8i, we are also watching Connect Edition developments as we know we will eventually wind up there.
What I am looking for a some type of explanations and guidance on Connect Edition Workspaces and what is new, what has been migrated. I'm pretty comfortable in my V8i Workspace and modifying them. But Connect seems to be a new beast, with new terminology and I was hoping that there is some guidance available, rather than having to brute force my way into Connect Workspaces.
caddcop said:But Connect seems to be a new beast
you are right that CONNECT Edition workspace is the new beast and in my opinion it's a right approach. I agree with John the new system allows better organization and related organization concept are well designed. My feeling is that many confusion expressed in MicroStation and Administration forums come from incorrect thinking "CE workspace is just V8i workspace with different naming". It's valid for many features, but not for all, so it can looks like it does not work fine.
caddcop said:What I am looking for a some type of explanations and guidance on Connect Edition Workspaces
Contrary to old tmies, now plenty of CE features are quite well described and explained (or at least better than for V8i). In addition to webinar linked by John I recommend also to ready:
Labyrinth Technology | dev.notes() | cad.point
Answer Verified By: caddcop
On a more basic level, I might recommend setting up the workspaces and worksets from scratch versus using Bentley's "wizard or whatever they call it". I was lazy and just let the software do it, ended up with some stuff that caused problems (like carryover vba stuff I didn't even realize was there).
Connect r14 10.14.00.109 self-employed
I'll qualify for a PHD in Configurations after digesting all of this. It's too bad I had to do a lot of "seat-of-the -pants" learning to get my skill set for V8i to where it is. Some of it even originated on CLIX!
The "Build from scratch" approach sounds scary, but I played with the wizard on an earlier release and I must say, the results were not pretty.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
A general concept with the new configuration is that each thing (CFG) knows about its things. So all the users settings are stored local to the user. All the workset settings are in the workset cfg, etc. You can still have higher up concepts like ms_dgnliblist= P:/$(Worksetname)/dgnlib/ but in general it was built so that the individual cfgs would tell it where to get it's things. This makes archiving and restoring things easier. If the WorkSpace.cfg knows about all its things then archival of a single workspace is easy. Of course this concept and direction may have changed.
Shaylesh has included a table of contents for configuration blogs which helps with navigation.
Some fundamental points are:
Standards can be defined and stored at any of these three levels depending on the granularity/control/variation required. These choices may also be guided by archiving requirements as John has indicated.
The start from scratch approach has a lot to commend it, build the structure then pull resources from V8i into the appropriate places. Obviously that is a simplification, but it should filter out configuration "tricks" that were needed to work around V8i that are hopefully not relevant to CE?