When I convert 6.0 ui to later version, can I make use of new ui controls/methods in old dialogs?

Question

0.00/5 (No votes)

See more:

Hi,
If I convert/import an old Visual Studio 6.0 project into a new VIsual Studio (10 or 12), can I access newer UI controls/methods to be used on the older (and now imported) dialogs?

For instance, the old CListCtrl was cumbersome to use. Everything had to be set up programmatically to sort, column hide, resize etc. If I import a tool into Vis Studio 10 or 12, and access a dialog from that tool which contains a CListCtrl, can I now make use of newer methods of CListCtrl on this older dialog? Do I need to remove my current CListCtrl, and put the newer one there, or do I just call the new methods to make sue of them? Or is it more cumbersome than that, where I cannot make use of new stuff on older dialogs, and I have to re-create my dialog, with new controls?

Do my questions make sense? I'm tryng to figure out what level of effort it will be to get better List Controls into old tools.

And Finally, even after looking at the msdn pages for CListCtrls in Visual Studio 10, I cannot easily tell when functionality comes for "free"... looks like I still have to code up my own sorting, resizing.. etc... is that true?

Thank you very much for your time.

Posted 12-May-15 3:41am

Member 11684563

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2015-05-12T05:32:00

You should start by building the project under the new system and fixing any errors/incompatibilities. Once you have it clean you can look at each control to see what new features are available and how it may be improved. Take a look at https://msdn.microsoft.com/en-us/library/ff657751(v=vs.85).aspx[^] for some Microsoft guidance on improving the look and feel.