I am having problems laying out the project configuration file. When I use the same configuration file on two separate computers, I get different results. How do I make sure the configuration is pointing ONLY to the locations which I want it to for line styles, cells, and fonts?
Hi,
Unknown said:I am having problems
What kind of problem do you have. Can you provide more information and explanation why you treat the situation as the problem? As Tim wrote in his answer, the output from DEBUG would be valuable.
Unknown said:on two separate computers, I get different results
It's expected behaviour. The final setting of MicroStation workspace includes a processing of more configuration files and tens of configuration variables, where some of them are conditional. The question is how big the differencies are.
Unknown said:How do I make sure the configuration is pointing ONLY to the locations which I want it to for line styles, cells, and fonts?
What is your knowledge how workspace setting is created from the configuration files? If you will create msdebug file and will read it, you will see how particular variables are created and by different configuration files, so you will be able to decide what and how to set to reach you aim.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
My knowledge is VERY limited, but I am determined to understand how this works. Debug does not seem to work.
I think the discussion should be split into two topics: (A) Why your current configuration doesn't work as expected and (B) How your workspace should be implemented in a right way. I think (A) is not so important now, because your try has substantial weaknesses, so we should focus on (B).
A few notes:
You have defined that the basic features are:
What I think you can do (or at least try):(It's a simplified template you can try and to modified accordingly to your needs.)
As you can see, you don't have to do anything with pcf file. It's because the system how variables are evaluated is defined in a hierarchic way, so the only way you have to do is to start MicroStation with own definition where project files (pcf file + project folder) are placed.
If you add another project (pcf file + project folder with standardized subfolders) into this shared folder, it will be automatically available in MicroStation open file dialog immediately (after MicroStation restart).
One more note (there is always one more note ;-)
Another approach is to share the whole workspace folder (everything under Workspace) on a network, which can be done by changing _USTN_WORKSPACEROOT configuration variable. But in my opinion it's more complex because many more files are shared, so I think you should start with simplier "project only" sharing.
What is wrong with the definitions I currently have designating "MS_DRY=P:/...../12-01 AE-UPTOWN/" and "MS_COLD=S:/BENTLEY/V8/WORKSPACE/System/"
The intent is to keep all of the used cells, tables, fonts, etc. on the server and refer back to them as new projects come in (City, Client, TxDOT, etc). This description sounds like the intent is to copy all the cells, etc. to each project as it comes about, which would lead to the duplication of files.
Even with the Project configuration set to look for on location, why is it that when the configuration has different results when placed in one place versus another?
Unknown said:What is wrong with the definitions I currently have designating "MS_DRY=P:/...../12-01 AE-UPTOWN/" and "MS_COLD=S:/BENTLEY/V8/WORKSPACE/System/"
May be nothing, usually the way is to use existing configuration as much as possible and to create the new ones when it unambiguously simplify the solution. I just offered you the idea of the solution that works for sure and doesn't require to use nothing else than standard variables. If you decided to use own solution, but don't define exactly what is the overall concept of your solution (what is where, what file is shared on what level), you cannot expect somebody will invest substantial time and effort to examine the whole your system and workspace and investigate the problems.
Unknown said:The intent is to keep all of the used cells, tables, fonts, etc. on the server
Done.
Unknown said:and refer back to them as new projects come in (City, Client, TxDOT, etc). This description sounds like the intent is to copy all the cells, etc. to each project as it comes about, which would lead to the duplication of files.
From your description I understood the files are project files, so they will be used in one project, not shared between more projects. If they are the same for all projects, they would belong to Standard (and never ever into System).
Unknown said:Even with the Project configuration set to look for on location, why is it that when the configuration has different results when placed in one place versus another?
No way how to answer your question other than you use differently set configuration files (at least one of them), there probably cannot be any different reason. But you don't provide any valuable information (msdebug log from these two computers but with the same user + project + interface), that can help to asnwer the question.The only solution is to create msdebug files with completely the same workspace, compare it side by side (any advanced text editor can do it) and check, where they are different.
Regards,
I am sorry, I did not mean to offend. I just didn't understand the process. Lets walk through your solution:
I am just looking for consistency.