Hello everybody,
in our organization we work in a workspace/workset configuration within our cad operators have to load/open different dgn files not assigned to any worksets.
Is there an environment variable/method/function im CONNECT to suppress the workset verification? Because the dgn files were manipulated from different worksets. An assignment to only one workset isn't practical.
I moved the dgn files to directories the variables MS_WORKSETMISMATCH_ALERT_EXCLUDE_* are pointing to but at all times the workset alert message appers.
best regards
Daniel
Hi Geoff, can you contact me directly about this VBA code?
I have not been able to get this to work.
Thanks!
bfegyverneki@enmax.com
We cant keep the messagemy use case is this.Data and workspace reside in Projectwise (not always ours) different projects too.Files pulled from PW and run through scripts - many many many reasons 1000's of files and oftenDialog prevents script from running (have to acknowledge dialog each file)= automation is not available without significant effort recreating workspaces that arent ours = significant additional costs
We just need a variable to ignore the dialogWe have had no movement or time frame on this its impacting large massive scale projectsPhil Conard is this something you can expedite please?
Done, thanks for the tip. (+) Need help with vb.net ustation.dll pinvoke declaration - Developers and Programming Forum - Developers and Programming - Bentley Communities
Hi Steven, please can you ask this question in the Developers and Programming Forum. You will get a more programming oriented audience there.
Regards
Marc
Any suggestions on how to get the mdlSystem_setBatchProcessingState/ustation.dll declaration/signature to work in vb.net? I keep getting the "Unable to load DLL 'ustation.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)" error, regardless of how I change the code.
Apparently this means that the DLL is found, but unable to load. I am unable to find the "mdlSystem_setBatchProcessingState" method in ustation.dll using dnSpy or ildasm. I thought perhaps there is a dependency problem, so I ran the dependency walker... however there 571 missing files (most look like "EXT-MS-WIN-*.DLL). I find it hard to believe that I would have to resolve all of these prior to using the .dll.
If there is another way of entering batch processing using vb.net that would also work!
Thanks for your time.