madmac

We have just finished and released our 1st software project using Visual Studio 2005 MC++, the source code for this has magically turned into a deprecated syntax during the products development lifecycle.

We are using /clr: oldsyntax to keep our existing code working but for how much longer I doní»t know.

For example we cant even add any new forms to our flagship software product with out hacking the project etc.

Will you ever attempt to finish the Managed Extensions for C++ to C++/CLI conversion tool

I have tried it out and it does not do anything usefull with our code at all : (

Can you offer services to take existing MC++ code and convert to the new Visual Studio 2005 SP1 C++/CLI syntax

It seems you have very little interest in helping people like us.

I have read all the migration checklist etc and tried a manual code conversion but the complexity of converting our existing code seems impossible : ( or at least very time consuming and prone to errors

Just manaualy converting the old style "__property" syntax to the new "property" syntax is overwhelming : ( thousands of them to do etc.

This is just one of the problems listed.

Any help would be appreciated, and sorry for being so negative.



Re: Visual C++ Language Managed Extensions for C++ to C++/CLI conversion tool

Sheng Jiang

you can download the VC++ 2003 Managed Extensions to VC++2005 C++/CLI Conversion Tool and have a try




Re: Visual C++ Language Managed Extensions for C++ to C++/CLI conversion tool

madmac

Thank you for the idea/reply but i did say in my post ..............

>>Will you ever attempt to finish the Managed Extensions for C++ to C++/CLI conversion tool

I have tried it out and it does not do anything usefull with our code at all : (

>>Can you offer services to take existing MC++ code and convert to the new Visual Studio 2005 SP1 C++/CLI syntax

I guess It is my fault for not putting my question at the top of the post.

I am in big trouble now... manualy editing 40% of the code lines in our product is something I should not have to do because of an enforced syntax change to your compilers : (

Again sorry for the negativity.

PS.....

A Link to A One File Example And Crash Log Can Be Found Here

http://madmac.pwp.blueyonder.co.uk/SurfaceProperty.zip

The tool crashes and makes no output at all. The source code example file will show you why I cant face manayaly converting. We have loads of files like this : (





Re: Visual C++ Language Managed Extensions for C++ to C++/CLI conversion tool

Sheng Jiang

You can open your assembly in .Net Reflector and view/copy/paste/disassemble the source code. You need to install the C++/CLI plugin and the FileDisassembler plugin (http://www.codeplex.com/reflectoraddins).






Re: Visual C++ Language Managed Extensions for C++ to C++/CLI conversion tool

madmac

Thank you for that information

I am realy impressed with refelector and the c++/cli++ plugin

Saddly it cant ever become a conversion tool : ( to many made up names, deadfull formatting and weird byte offsets BUT...

I am sure l help me when i get stuck manualy converting all this source code

I am supprised that no other coders seem to care about migrating MC++ to C++/CLI maybe they jsut freeze MC++ and rewrite dunno : (

Ill stop talking now and get on with it bye