I've been using Notepad++ for several years now and it is a brilliant text editor. There are others with similar abilities, Notepad++ has worked for me so far so I've stuck with it. It is updated frequently with new features.
The styling it applies to the various files formats as mentioned in my earlier piece on using it with configuration files makes complex files far more legible.
What I really like are its enormously…
In part 3 I put the Company dataset on the network. However you will have noticed that the COMP_DATASET = E:/Dataset_Company_OnNetwork/ variable pointing to the network is contained in the Project Configuration File (PCF) on the C drive located in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss4\WorkSpace\Projects\BuildingExamples\.
Copying the modified PCF to every machine, whilst functional, is a poor solution…
Updated 11 August 2014.
There are a number of ways to redirect AECOsim (and MicroStation) to the network.
The most common is to modify the mslocal.cfg file found in C:\Program Files (x86)\Bentley\AECOsimBuildingDesigner V8i Ss4\AECOsimBuildingDesigner\config\.
The disadvantage of this is when troubleshooting to check the mslocal.cfg version is correct you have inspect the file attributes or open it to confirm the contents…
From adding the Company Dataset in part 2 it is a short step to share the Company Dataset on the network.
1. Continuing from part 2, copy the Dataset_ Company folder from
C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss4\WorkSpace\BuildingDatasets\Dataset_ Company
to a network location and rename it to avoid confusion.
I'm using E:/ so end up with:
Having established MyDataset_NM and MyProject_NM_Light_01 in part 1 I’ll now show you how to add a Company Dataset to isolate any changes you make from the delivered dataset. This is going to involve a long list of configuration variables, however this list is nowhere near as complicated as it may look at first glance!
While all of Bentley’s configuration files are text files that will open with Windows Notepad…