Time Machine.
-
I spend my day switching back and forth between VS2008/C#/.NET/WPF and VS2003/C++/MFC. and they wonder why I twitch...
Software Zen:
delete this; -
I didn't realize that MS made any non-trivial changes to C++/MFC since 2k3, what's blocking your upgrading the legacy apps to the new compiler?
The European Way of War: Blow your own continent up. The American Way of War: Go over and help them.
Mainly a moderate amount of recoding needed to get around the deprecated C runtime library functions, changes to ATL functionality, plus all the regression testing required. Our legacy application is approximately 500,000 lines of C++/MFC, which would probably require 2-3 months to port to the new environment with no net benefit. The Big New Thing™ is being developed using C#/.NET/WPF for the UI, and new service code developed in C++ using some utilities ported from the legacy stuff. The funny thing is, it took less time for me to write the utilities in C# from scratch than it took to make the ported legacy code compatible with the VS2008 C++ compiler :rolleyes:.
Software Zen:
delete this; -
Mainly a moderate amount of recoding needed to get around the deprecated C runtime library functions, changes to ATL functionality, plus all the regression testing required. Our legacy application is approximately 500,000 lines of C++/MFC, which would probably require 2-3 months to port to the new environment with no net benefit. The Big New Thing™ is being developed using C#/.NET/WPF for the UI, and new service code developed in C++ using some utilities ported from the legacy stuff. The funny thing is, it took less time for me to write the utilities in C# from scratch than it took to make the ported legacy code compatible with the VS2008 C++ compiler :rolleyes:.
Software Zen:
delete this; -
Is The Big New Thing™ going to replace the legacy app, or are you just pillaging its codebase...
The European Way of War: Blow your own continent up. The American Way of War: Go over and help them.
Hopefully/eventually yes to the first, and partially yes to the second. "Pillaging" might be a tad judgmental a term for what we're doing. We've got a very mature and nicely capable library of C++ utilities for the type of distributed process control applications we develop. It includes utilities for building Windows services, thread management, TCP/IP socket communications, etc. That library is what we've ported from VS2003 to VS2008. We've left behind the prior UI and its COM-based plug-in architecture, along with the remainder of the existing service code.
Software Zen:
delete this; -
Why?
Jammer wrote:
I've just been reassigned to a new project
Jammer wrote:
VS2003
That kinda argues that it's not a new project.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Why?
Jammer wrote:
I've just been reassigned to a new project
Jammer wrote:
VS2003
That kinda argues that it's not a new project.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
I believe that VS2003 comes with WTF. :)
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
Nuh they deprecated that too
Multi famam, conscientiam pauci verentur.(Pliny)
-
Jammer wrote:
've just spent the last 1.5 years working with WPF ... I've just been reassigned to a new project ... that requires me to ... install ... urgh! ... VS2003 ...
great! they didn't ask you to work on visual studio 5 or cobol :-)
-
Hey man, it could be worse, I went from VS 2008 and some sweet WCF stuff straight to .... wait for it ... VB 6 in classic asp! I didn't even know it still existed. At least I was able to use VS 2005 for it. It's really still too soon for me talk about it.
-
-
I spend my day switching back and forth between VS2008/C#/.NET/WPF and VS2003/C++/MFC. and they wonder why I twitch...
Software Zen:
delete this;I have spent the last 4 years going between the most current version of VS and VS 2002 then VS 2003 because management does not consider it important enough to take the time to move to the newer CLR. Instead we pander to every customers wild whim building on to the 1.1 platform project which they never use. Phew, I feel better. The job pays well enough (benefits could be better), I like the people I work with, work is flexible, and things are looking up as for going to the new platform maybe we will get their by VS 2010! Remember you are unique just like everyone else. (this came to me when a teenie bopper was digging through a bin of consumo crap and said as she pull one out "Wow, Mom! This is unique." and her mother replied "Yes, and it is special too." as they both stood in front of a bin of about 200 identical items.) That and the line from The Princess Bride Inigo Montoya: "You keep using that word. I do not think it means what you think it means."
-
I spend my day switching back and forth between VS2008/C#/.NET/WPF and VS2003/C++/MFC. and they wonder why I twitch...
Software Zen:
delete this; -
Why?
Jammer wrote:
I've just been reassigned to a new project
Jammer wrote:
VS2003
That kinda argues that it's not a new project.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Hey man, it could be worse, I went from VS 2008 and some sweet WCF stuff straight to .... wait for it ... VB 6 in classic asp! I didn't even know it still existed. At least I was able to use VS 2005 for it. It's really still too soon for me talk about it.
-
I just spent the last week coding in VS2003 VB after 2 years of VS2005 C#. Still feel burnt but the changes are running now. Spent a lot of time back spacing over the ; and getting the equivalent of "You can't get there from here"
-
I just spent the last week coding in VS2003 VB after 2 years of VS2005 C#. Still feel burnt but the changes are running now. Spent a lot of time back spacing over the ; and getting the equivalent of "You can't get there from here"
Just remember that VS2003 will not install on VISTA! We've tried it and then knew we had to stay with XP for another (good) reason. For our project, there is no reason to "move on" to a newer version of Visual Studio. Outside of using the VS 6 serial port control, we have everything we need in VS2003 -- we actually had it all in VS6, but my partners said we "had" to catch up with the rest of the world. For what it's worth: I still use FORTRAN and have no problem with COBOL. Now C is language for OS writers and masochists.
Charles Wolfe C. Wolfe Software Engineering
-
Just remember that VS2003 will not install on VISTA! We've tried it and then knew we had to stay with XP for another (good) reason. For our project, there is no reason to "move on" to a newer version of Visual Studio. Outside of using the VS 6 serial port control, we have everything we need in VS2003 -- we actually had it all in VS6, but my partners said we "had" to catch up with the rest of the world. For what it's worth: I still use FORTRAN and have no problem with COBOL. Now C is language for OS writers and masochists.
Charles Wolfe C. Wolfe Software Engineering
The project is installed on my home desk top still running xp. No body else in the office still has a copy of vs2003. I have become the VB guru. I actually can't do it in the office because the firewalls prevent me from reaching this server. It is the only project running this because it is on another companies server which is why it is in VB. I am sticking with XP because I still have other clients running something called DATAEASE which I support.
-
-
Why?
Jammer wrote:
I've just been reassigned to a new project
Jammer wrote:
VS2003
That kinda argues that it's not a new project.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
atleast u got to work on WPF. I am stuck with 1.1 since I started off. My client refuses to move forward even to 2.0 On top of that VS 2008 has so many gr8 features for development which too I am missing on