Hi,
This question came from the development of our (3rd party) product, but is completely development unrelated.
We used to start MicroStation (V8i) with the -WU<our product>(.cfg) which MicroStation took in account and our application had everything configured via our configuration file.In CONNECT there no such an option.
I now explored the options that the -WK<WorkSpace> and -WW<WorkSet> switches bring to me and even after going through quite a lot of the articles and discussions here, I wasn’t able to solve the main requests:
Is there perhaps a variable that would tell MicroStation to stop insisting on the DGN file association?
Or is there another way how to achieve the above described requirements?
In case there is already an answer to my question, please redirect me to that, I wasn’t able to find it.
Thank you in advance,Miroslav Mandl
In CONNECT the file that redirects to the network is "C:\ProgramData\Bentley\<applicationName>\Configuration\ConfigurationSetup.cfg".
It is recommended and should be possible to customise without editing any of the CFG files in "C:\Program Files\Bentley\OpenBuildings CONNECT Edition\<applicationName>\Config".
The following blogs go into some detail on the topic, I hope they are helpful:
Deploying or Updating ConfigurationSetup.cfg
Configuration Tips : Should I edit ConfigurationSetup.cfg?
Configuration Tips: What does _USTN_USER_CONFIGURATION do?
Regards
Marc
Thank you for this tip. Originally I didn't think of using the -WC switch, but it turned out to be the only option for me.
I’d just point out one detail about the -WC vs. -WU difference for other readers:
Regarding the "file branding" I noticed I don’t have to care if any DGN file gets associated with the “No WorkSet” workset.
For me: case closed.
Thank you
Miroslav
-WU is used to preset a User configuration. That is no longer an option, since there are no more discrete users to choose from; CONNECT is based on the active Windows user.
You can use the -WC switch to include your own configuration file, which may be able to bypass or redefine many of the preset, out-of-box configurations without actually changing those original files.
While I do not believe there is a way to disable Microstation "file branding", I did find a very interesting discussion in this thread: https://communities.bentley.com/products/administration/f/product-administration-forum/181749/connect-disable-workset-verification/638763#638763
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2