My AddIn processes a list of DGN files. For each file, it uses Session.NewDesignFile(). In many cases, that pops modal dialog No Workspace Alert...
I want to eliminate that dialog so the list can be processed with no human intervention. In another post about C++, Yongan.Fu suggested unpublished function mdlSystem_setBatchProcessingState(). Is there a .NET equivalent?
Hi Jon Summers,
At the bottom of one of YongAn's wiki (Use Google Translate for alternate languages), is an update note mentioning MSCE U15 and later provide a new configuration variable that may also be considered: MS_SUPPRESS_FILE_WORKSET_ASSOCIATION.
I will check to see what .NET APIs may too be able to offer.
Robert Hook said:is an update note mentioning MSCE U15 and later provide a new configuration variable that may also be considered: MS_SUPPRESS_FILE_WORKSET_ASSOCIATION.
I think this variable is not what Jon asks for, even though it can help partially.
Jon (and as visible in this discussion, also some others) would like to remove the dialog (the workset assignment check), whereas the variable controls whether the association is created.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
The variable should prevent the dialog from being presented for MSCE U15 and all PowerPlatform based products built on top of it - keyin: version to id platform version. Unfortunately I don't have the most recent source sync'd so I cannot be more certain; however I do not see any .NET code setting anything special for "batch processing" as of yet. Of course the MDL function could be called from .NET though a cleaner call is desired overall. Sorry that is all I have and can report for the moment but will try to dig up more info if available.
Answer Verified By: Jon Summers
Robert Hook said:MSCE U15 and later provide a new configuration variable that may also be considered: MS_SUPPRESS_FILE_WORKSET_ASSOCIATION
Thanks: that seems to do what I want.
However, if the workset is ignored then the DGN resources may not be available for that session.
Is there a way to tell a newly-opened DGN file to use the workset with which it is branded, so MicroStation doesn't need to open that dialog?
Regards, Jon Summers LA Solutions