MDL CONNECT Migration tool ignore some files

Hi all,

We are trying to use the MDL CONNECT migration tool (migrate.bat) to convert some V8i mdls to CONNECT, but it looks the process igore some files.

Does anybody have any tip or idea to solve it? Is there any specific requirement to include the cpp files into the process?

Here is the text I receive in the migration report:


START: Migration remapping

##### PROCESSING STARTED: 28/10/2016 12:07:13,02
INFO: Backing up source code
INFO: Starting Batch Remapping of Source File Types: .c .cpp .h .fdf .hpp

##### PROCESSING FILE [1]

COMMAND: C:\Python27\python.exe
ARG1:  C:\MDLBAS~3\MigrationTools\ApiRemapper.py
ARG2:  C:\MDLBAS~3\MigrationTools\0811to1000Published.remap
ARG3:  C:\Fuentes\PRUEBA~1\MIGRAC~1\DWGAPP~1.CPP
RESULT:
                                                                               
1 files (21 Kbytes) read - 0 files changed

##### PROCESSING FILE [2]

COMMAND: C:\Python27\python.exe
ARG1:  C:\MDLBAS~3\MigrationTools\ApiRemapper.py
ARG2:  C:\MDLBAS~3\MigrationTools\0811to1000Published.remap
ARG3:  C:\Fuentes\PRUEBA~1\MIGRAC~1\L8000001.cpp
RESULT:
                                                                               
0 files (0 Kbytes) read - 0 files changed

##### PROCESSING FILE [3]

COMMAND: C:\Python27\python.exe
ARG1:  C:\MDLBAS~3\MigrationTools\ApiRemapper.py
ARG2:  C:\MDLBAS~3\MigrationTools\0811to1000Published.remap
ARG3:  C:\Fuentes\PRUEBA~1\MIGRAC~1\T8010002.cpp
RESULT:
                                                                               
0 files (0 Kbytes) read - 0 files changed


##### PROCESSING FINISHED: 28/10/2016 12:07:15,66

Start  Time: 28/10/2016 12:07:13,02
Finish Time: 28/10/2016 12:07:15,66

IDENTIFIED: [3] Valid source code files extensions for processing: .c .cpp .h .fdf .hpp

MODIFIED FILES:


FINISH: Migration remapping

Thanks in advance,

Eduardo

Parents
  • Hi Eduardo,

    Migrating MicroStation V8 code to MicroStation CONNECT (v10) presents a number of choices to make and coding advancements and opportunities to be leverage.  The product itself is 64-bit, is extremely customizable with delivered tools, presents many new and improved features and workflows, and programming options (native code C++ and C MDL applications, .NET managed add-ins, MicroStation VBA/COM, MicroStation Basic Recorder "MBR") to name a few.  With all these choices it is recommended to become familiar with what the new product currently offers (features, workflows, utilities) and determine if prior custom code is required or is in need to adapt to any new design and workflow changes.  At this point possibly consider performing a staged migration of required code; e.g. first 1 to 1 migration (function to method remap), or preferred - explore and use new and powerful API classes (native C++ or managed .NET add-ins), or consider leveraging simpler and very productive and effective task oriented options like: MicroStation VBA or MBR.

    Thank you for providing the above output logging details since it provides information on configuration and processing performed.

    The purpose of MigrationTools (migrate.bat) is to provide developers a way to perform 1 to 1 "old function or type" to "new static method or property" replacements.  Though there are approximately 2500 such search and replacement remap entries, this approach only helps achieve a minimal amount of migration efforts required in a semi-automated manner.

    1. You appear to have a properly configured environment since the migrate.bat was able to properly detect the installed and required version of Python and there are no Python specific errors.
    2. The 4th line of output shows you valid file types the script currently processes
    3. Each "ARG3:" line shows what file type was included in processing
    4. Each line following "RESULT:" will show how many 1 to 1 remap replacements were able to be performed
    5. If the "RESULT:" line reports "(0) files changed" then the remap search and replace file (0811to1000Published.remap) was not able to identify any 1 to 1 remap replacement candidates in your source code file.

    For any migration topics or specific function recommendations I highly encourage you to first search the MicroStation Programming forum (via search text box at the top middle section of any page) then ask/post your questions.  You should find the developers on the Bentley Programming Forums to be very helpful in helping you make prompt and correct choices moving forward and helping solve most issues presented.

    HTH,
    Bob



    Answer Verified By: Eduardo Cortes 

Reply Children
No Data