Re: Does Microsoft Still Support MSVC V6?

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

Actually, I have people who are still putting in my contract that development must be in
VS6 (my standard contract says "The appropriate contemporary release of Microsoft Visual
Studio). They can't afford to "move on" because there are so many problems in the MFC
runtime, library differences, etc. that when they compile code in VS.NET it simply doesn't
work (I even have one example myself!) and they (and I) don't have time to go back and
figure out what part of what library broke. As one client told me, and this is probably a
very accurate paraphrase of his comments, "if we recompile in VS.NET we risk destabilizing
our product. We know it doesn't work correctly when compiled with VS.NET. We don't have
time to figure out what has gone wrong, and we don't know what has gone wrong that we
haven't yet detected. We need a stable development environment so we know that any
problems are due to our most recent changes and not some artifact of a bug in the
development or runtime environment of VS.NET. And we don't have time retrain our entire
staff in a new environment".

It would have been nice if the developers of this interface had encountered real users
with real issues.

While I think we have to move on to VS.NET 2005, I don't have to like it. I use VS.NET
2003 for new development (someday I hope to see my MSDN subscription arrive, before it
expires, and move on to VS.NET 2005), but not everyone with a large code base follows
Microsoft's delusional system that as soon as version X of anything is delivered, all
users of version X-1 instantly change to version X.

We have various products in our company. All but one, are on VC6. I am
an advocate for moving on to new platform(to stay current), but the
resistance has been great. So I now work with VC6 and VS2005 at the
same time. IOW, code is compatible across these two compilers. It hasnt
been too bad actually.

---
Ajay

.

Relevant Pages

  • Re: Equivalent of Cs "global/static" variables
    ... > This message, however, suggests a bug in CMUCL - whereas is perfectly ... > the particular non-null lexical environment it was given, ... what it actually says, in teh descriptuon for COMPILE, is: ...
    (comp.lang.lisp)
  • Evaluating/compiling forms in the current lexical environment.
    ... it's not possible EVAL or COMPILE forms within a lexical environment of one's ... EVAL is not implemented through COMPILE, usually has an environment, and one ... (defpackage lexical-eval/compile ... "Obtain a list of names of the local lexical variables in the ENV ...
    (comp.lang.lisp)
  • RE: DBI connect(,/,...) failed: ERROR OCIEnvInit
    ... Are you changing your environment between the two connects? ... Andy Hassall / Space: ... > When making a connection to an 8i instance, ... > Do I need to compile specifically against the 9i libraries to ...
    (perl.dbi.users)
  • Re: VC++2005 executables much slower than VC++6????
    ... so your benchmark is very sensitive to the speed of the standard ... the "Secure SCL") that are probably slowing you down. ... Another thing that's changed since VC6 is the use of the small block heap. ... apples to apples (i.e. compile the same code with both compilers), ...
    (microsoft.public.vc.language)
  • Re: What should (ignore-errors ((foo))) do?
    ... that )) should be an error at compile time. ... statically valid programs are more consistent when it's always treated ... (what is visible in which environment, ...
    (comp.lang.lisp)