Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Faced with the same task, my strategy would be something like:</p> <ol> <li><p>Identify what we hope to gain by moving to 2010 development - it could be</p> <ul> <li>improved quality assurance: unit testing, mocking are part of modern development tools</li> <li>slicker UI: WPF provides a modern look and feel.</li> <li>productivity: in some areas, .NET development is more productive than C++ development</li> <li>support: new tools are supported with improvements and bugfixes.</li> </ul></li> <li><p>Identify which parts of the system will not gain from being moved to C#: </p> <ul> <li>hardware access, low-level algorithmic code</li> <li>pretty much most bespoke non-UI working code - no point throwing it out if it already works</li> </ul></li> <li><p>Identify which parts of the system need to be migrated to c#. For these parts, ensure that the current implementation in C++ is decoupled and modular so that those parts can be swapped out. If the app is a monolith, then considerable work will be needed refactoring the app so that it can be broken up and select pieces reimplemented in c#. (It is possible to refactor nothing, instead just focus on implementing new application functionality in c#.)</p></li> <li><p>Now that you've identified which parts will remain in C++ and which parts will be implemented in c#, (or just stipulate that new features are in c#) then focus turns to how to integrate c# and c++ into a single solution</p> <ul> <li>use COM wrappers - if your existing C++ project makes good use of OO, this is often not as difficult as it may seem. With MSVC 6 you can use the ATL classes to expose your classes as COM components.</li> <li>Integrate directly the native and c# code. Integrating "legacy" compiled code requires an intermediate DLL - see <a href="http://www.codeproject.com/KB/mcpp/mixnetnative.aspx" rel="noreferrer">here</a> for details.</li> </ul></li> </ol> <p>Mixing the MFC UI and c# UI is probably not achieveable, and not adviseable either as it would produce a UI mix of two distinct styles (1990s grey and 2010 vibe). It is simpler to focus on achieving incremental migration, such as implementing new application code in c# and calling that from the native C++ code. This keeps the amount of migrated c# code small to begin with. As you get more into the 2010 development, you can then take the larger chunks that cannot be migrated incrementally, such as the UI.</p>
    singulars
    1. This table or related slice is empty.
    1. PORecommended migration strategy for C++ project in Visual Studio 6
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmdma
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORecommended migration strategy for C++ project in Visual Studio 6
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHmm, not really a reason to move to 2010. The same can be had by moving to Qt and keeping C++. That might be a lot easier
      singulars
      1. PO
      1. USStephan Eggermont
    2. CO@Stephan - not really "a reason" to move? - I gave more than one reason - which are meant as examples to prompt thinking about why this task is necessary, which I think is prudent before embarking on a any large effort - the OP doesn't say, but may have his own reasons for migrating. Even so, please explain why you don't think they are reasons to move to 2010.
      singulars
      1. PO
      1. USmdma
    3. COIn the sense of: can be had without moving to 2010
      singulars
      1. PO
      1. USStephan Eggermont
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload