I am trying to analyze and troubleshoot some workspace issues. Some of these are stored in a location that is accessed using the Custom Configuration options. Haw does one get the Configuration Explorer to include any Custom Configurations?
I did just noticed that the workset.cfg is not read. That seems odd.
Also, I discovered that a workset from a ProjectWise Session gets written to the personal.ucf file and then can impact the results from an msdebug.txt.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
If I want to debug a particular workspace/workset I'll create a custom icon using -ww and -wk along with debug to force it to select the workspace and workset.
But honestly lately I just open a file in the proper workset then use the "show configuration" key-in. That gives you the summary info which frequently is all I want. Only really detailed troubleshooting do I go back to debugs anymore. (especially with ProjectWise managed workspaces where a debug doesn't list all configuration file by file but some weird dump that just shows the level)
Just an aside. Interesting "feature". I tried out the "show configuration"
_MSCONFIG_VERSION_BUILD: System = 02 _MSCONFIG_VERSION_MAJOR: System = 10 _MSCONFIG_VERSION_MINOR: System = 15
I have Update 16 though? Is the Configuration showing one version behind, or is this correct?
Greg SmithAirways New Zealand
Opinions expressed are my own and not necessarily those of my employer
I believe that's correct as it's the version of the configuration itself, not the application.