Please could you explain - if this is possible- how can you share your organization standards between AECOsim CONNECT and Microstation CONNECT ?
I have a networked drive with the MS CONNECT workspaces (Organization, Workspaces containing Worksets).
But it is a total mess if you mix with AECOsim. Where do you put shared Datasets ? What about the dgnlibs: the have different names (levels*.dgnlib, DisplayStyles*.dgn,...for AECOSIM, not for MS).
My goal is quite simple: I want to share a single Workspace and a single Workset along with an Organization folder, all set on a networked drive.
All MS CONNECT seats and all AECOsim seats must share the same dgnlibs: levels, textstyle, dimstyles, display styles,keyboard shortcuts, custom ribbons,.... almost everything
I installed MS connect and AECOsim connect with custom configuration option pointing to my shared drive, but clearly this is not enough (but it should be).
What exactly happens when both applications are pointing to the same set of resources? And, are you saying that you want a single storage location, but for each application to load/use different files?
I would imagine others here may have done something similar but it's not something that I've personally come across before.
sorry for delay, i was not in the office these days.
Both applications are pointing to the same location: \\NAS\Connect but i have problems with the dgnlibs.
Just one example: for the level hierarchy, AECOsim seeks MS_dgnliblist_levels = levels*.dgnlib, but MS CONNECT doesn't.
And i can not track every variable in both applications to check what is working and what is not.
I assumed that pointing to a unique set of ressources when i installed the applications would at least share my Organiszation standards but i fear it is not so easy. And i don't want to tweak every workstation
I really big help would be a Connect version of Bentley Configuration Explorer.
Bentley Configuration Explorer (BCE) is available for CONNECT, the current download is version 10.00.00.11, however we have a couple of problems with BCE:
One can be resolved by following the instructions in CONNECT Edition - Using Configuration Explorer with Update 4.
The other is that BCE currently does not parse UNC paths. However if you map a drive to \\NAS\ you will be bale to use that for analysing the configuration with BCE.
I will reply further regarding the sharing of resources, this can be achieved. In the meantime please take a look at CONNECT Edition - Configuration : Customization Guides for some guidance.
Thank you Marc,
I used all your knowledge ("looking under the bonnet") when i configured Aecosim V8i. It helps me a lot but still i think this is by far too complicated for small business as mine.
Allowing very fine and subdivided configurations (Organization level, Workspace level, Workset level, user level,...) for big companies (DOT for example) is certainly mandatory for Bentley. But you should narrow the process for small business. And i know you try to: pointing to a shared ressources directory during installation was encouraging.
But there are so many variables and some of them are even hidden - see my last post about MS_luxology_History. On top of this i suppose trying to mix Microstation and Aecosim is foolish (vanilla install of Aecosim with a foreign dataset is already quite erratic).
I will read with great interest your coming post about sharing ressources. If you could give us an example of installing MS Connect and AECOsim with a unique simple shared networked directory ( one Organization folder, one dataset, one workspace, one workset ) i guess it would help a lot.
While most of my blogs, in the middle of updating for CE, are V8i based, the information in them is still very relevant to CE. I've got quite a bit on how I split out applications like AECOsim into company and client standards. Happy to help if I can.