Re: VC++2005???

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

My question is do we need to go to VS2005 if everything seems to be working
fine in 6.0 and 2003 versions? I am recompiling my application in 2005 and I
am getting 3285 warnings which are mostly because of all the deprecated
functions.

You dont have to upgrade but the upgrade is relatively painless. Only
thing I found to be problematic was that the default time is 64 bin in
VS2055. Deprecation of functions was not a big deal.

If I am not going to be using multiple languages should I just keep myself
to the 6.0?

This is a non issue if you are unmanaged. If you are using MC++, you
get a choice of moving to CLI.

Also I am getting problems with the other libraries that are linked to my
applicaton!

What problems? Make sure you compile all projects with VS2005.

On the other hand, are they going to keep the MFC? Or MFC will be deprecated
in some future version....

Very very unlikely. Almost impossible. Even if they do, you dont have
to use the new compiler. Old compiler/code will continue to work.

---
Ajay

.

Relevant Pages

  • Re: SDK 9
    ... Outside of a few compile issues ... Phil Taylor wrote: ... > a backport on any interesting samples, as long as they dont use new D3DX ... then you have to upgrade. ...
    (microsoft.public.vc.language)
  • Re: SteppedComboBox problem
    ... > and when i compile it using JDK 5.0 with -Xlint:deprecation i get the ... > deprecation warning about the SteppedComboBoxUI.showmethod being ... > public void setVisible{ ...
    (comp.lang.java.gui)
  • Re: [PATCH] sysctl: Allow /proc/sys without sys_sysctl
    ... This should catch any remaining user space code that cares, ... ** the sysctlbinary interface. ... So the combination of the two patches and makes the deprecation official, ... and makes it a compile time option so we can disable sys_sysctl now, ...
    (Linux-Kernel)