There is an old C ++ Builder program and a desire to upgrade to Visual C ++. I always believed that the current Embarcadero is similar to the C ++ WinForm project in VS. However, in the VS 2013 Community version, with which I started trying, there are no such projects (only WinForms for C # and VB).

What does this mean? What is now the usual windows-based C ++ applications no longer do this way? And then what instead allows you to create a form and drag components onto it? Microsoft advertises WPF, but this is again not for C ++, but only for C # and VB.

I read the references to StackOverflow and it turns out that most people advise using Qt at all. Total: what is the "right" way to translate an old C ++ Builder program to VS or other software?

Update:
The reason why you want to abandon C ++ Builder is simply unreliability (the last feather is the error of LME288 linker). If it were not for this, the program is excellent.

Closed due to the fact that it is necessary to reformulate the question so that it was possible to give an objectively correct answer by the participants αy , pavel , aleksandr barakin , Mirdin September 3, '16 at 13:39 .

The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .

2 answers 2

In a simple way, VCL guinyu under WPF/WinForms/Qt you still do not translate. Those. Of course, you can borrow design, but you have to do all the stuff in a new way. Business logic should be transferred without any problems if we are talking about preserving the C ++ language , that is, without switching to C # or something else. So if the decision to abandon Embarcadero is final, it is the easiest of all to go over to the implementation under Qt .

PS In general, this question is not quite suitable for StackOverflow.

    If you have an old C ++ builder program, then it is probably also a big one, and uses a ton of components from the VCL, which are not found in either Visual C ++ or in QT or C #.

    The ability to visually edit windows forms is in many development environments, but VCL (Delphi and C ++ Builder) is by far the leader in the number of visual components.

    If you have a desire to "translate" your program from one language to another, then first you need to decide on the purpose of this event. The goals may be different:

    1. Cross Platform
    2. Beauty code
    3. Involvement of programmers specializing in certain languages ​​and technologies
    4. Appearance of the application
    5. Speed ​​and optimization
    6. And much more.

    Each environment and framework has its pros and cons. VCL has a huge amount of visual components (many of them have no analogs in other frameworks), including for working with databases, C # has that C # is the language with the highest syntax sugar and very elaborate .net framework , QT - cross-platform, etc.

    In any case, you need to be ready, which is great , or even most of the code, you have to write again.

    I would not advise you to start transferring a large program to any other platform without first getting acquainted with its pros and cons.

    • I really didn’t want to refuse VCL, but the LME288 linker’s error could not be steadily overcome. Coupled with a bunch of other shortcomings had to decide. If you do not change C ++ to another language and focus only on Windows, what do you mean by "many development environments"? What if not Qt? - Ali58