Dear Team,
We are migrating old MicroStation V8 tools(.ma) to CONNECT EDITION 14.
Our old v8 tools contains .rsc resources only but for migration we need .r files it seems.
can i migrate my old v8 tool with .rsc file or i need .r file as mandatory ?
Thanks in advance.
Hi Daniel,
please be aware you posted your question to general Developers and Programming forum, but probably more specialized forums like MicroStation Programming forum or MicroStation forum would be better (Product Administration forum is yet another alternative). To move existing post, use More > Move tool available under your original post.
Daniel Bollavarapu said:We are migration old microstation V8 tools to connect edition 14.
Can you please provide more details what exactly do you migrate? It's not very clear, because of several different formulations:
Based on what should be migrated, the right forum can be selected.
Daniel Bollavarapu said:Our old v8 tools contains .rsc resources only
The information "contains .rsc only" is in conflict with information about MDL.
Daniel Bollavarapu said:can i migrate my old v8 tool with .rsc file or i need .r file as mandatory ?
Without knowing details requested above the question cannot be answered:
With regards,
Jan
P.S. I recommend to be more careful about proper naming and capitalization (not microstation but MicroStation, not Connect but CONNECT Edition or CE...), because text looks better, more professionally and also can be read easier (because we all are used to the names ;-)
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Answer Verified By: Daniel Bollavarapu
Dear Jan,
we have developed one custom tool to reshape the element using MDL's.
Our tool contains below files.
Using 'mdl load builder' dialog box was designed.
All the Dialog Box design code will be in .rsc file.
We cannot view or edit .rsc file we need <toolname>Dlg.r file for editing, so we are using 'mdl load sourcer' tool in V7 to generate .r file from .rsc file.
So without .r file (dialog box code) can i migrate my tool to CONNECT EDITION ?
Thank you.
Daniel Bollavarapu said:so we are using 'mdl load sourcer' tool in V7 to generate .r file from .rsc file.
Yes, it was the only way how to create r from rsc. Can it be used to create missing .r from dialog rsc definitions too?
Daniel Bollavarapu said:So without .r file (dialog box code) can i migrate my tool to CONNECT EDITION ?
You need a complete project that can be compiled from scratch (nor rsc files in a middle) to migrate it to CONNECT Edition.
Frankly, I am a bit surprised you have not needed the source files in the past. It's possible to use rsc files only, but they are black boxes, and such project cannot be treated as a standard project in my opinion.
Hi Jan,
Yes it is creating missing dialog source code .r file from binary .rsc file.
Complete project must contain dialog source .r file for migration ?
Daniel Bollavarapu said:Complete project must contain dialog source .r file for migration ?
As I wrote above: You need complete project with all source codes. Rsc files are not source codes, they are compiled from .r (plus other like .h) files using resource compiler.
Summary: You have to have project, containing source files (text files like .mc, .h, .r...) only and to be able to compile the application using V8 SDK development shell.
I agree with Sedat Alis: Everything is possible, including to use rsc files without source codes, but it's (A) not the way supported officially and (B) requires special knowledge. To use standard way is always recommended.
But not only! As visible from your screen capture, your project is pseudocode (compiled from .mc files), that is obsolete I guess for last 10 years (from XM Edition?) and not supported in CONNECT Edition. So the migration is not about missing .r files only, but also to migrate the code from pseudocode to native code (Visual Studio 2017 Professional) based on CE API.
When your application is "just one tool", it's a question whether it's not simpler to implement it from scratch, e.g. in C#, which is more limited comparing to C++ API, but provides faster and simpler implementation.
Regards,