For some of our cad builds, we have user prefs in a custom location. All re-direction seems work well in U17, except for the configuration.xml file. From prelim testing, the file has to be correct and exist in the C:\Users\...\AppData\Local\Bentley\MicroStation\10.0.0\prefs\configuration.xml location for our cad build to work correctly.
Can someone from Bentley confirm that is the case? And if it is, is that supposed to be WAD or an oversight?
Also, it would be greatly appreciated if a full documentation regarding the configuration.xml file be made available asap, including it's known limitations. The information provided in the post below is nowhere enough to integrate U17 into a production CAD system:
https://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/marc_thomass_blog/posts/configuration-tips---manage-configuration-utility
Example of missing information: the <Path> tag can be omitted and replaced by using the <ConfigurationVariable> tag, which is a far better option to use from an admin point of view.
Best regards,
Tuan Le
similar discussion here:
https://communities.bentley.com/products/microstation/f/microstation-forum/232129/connect-edition-17---how-can-i-remove-unwanted-configurations-from-gui
not necessarily putting it in another location, but change how it is used for the whole configuration.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Hi Tuan,
Tuan Le said:Example of missing information: the <Path> tag can be omitted and replaced by using the <ConfigurationVariable> tag, which is a far better option to use from an admin point of view.
My understanding is that the path statement defines the value of _USTN_CONFIG_<Title> so cannot be omitted from configuration.xml.
Please provide more detail of what you have found?
We are looking at providing a variable to define the location of configuration.xml.
Regards
Marc
Hi Marc,
Below is the custom xml I used to get our cad build to work properly. It seems as along as the right configuration variable is used, the <path> tag can be skipped.
Full documentation would be REALLY helpful. Since this is going to be part of our world moving forward, we need the knowledge to apply it properly.
I second the ability to control the location of this file.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Marc Thomas said:We are looking at providing a variable to define the location of configuration.xml.
Please make it a priority and get this variable implemented before you release the next version of ORD.
Rod WingSenior Systems Analyst