Time Machine.
-
-
<Sarcasm>That'll teach you to keep up with the latest.</Sarcasm> :-D
-
Don't complain - Some people here would love to be in your shoes, anything to get away from WPF.
-
You might be better off...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
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.”
-
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 :-)
-
<Sarcasm>That'll teach you to keep up with the latest.</Sarcasm> :-D
-
Don't complain - Some people here would love to be in your shoes, anything to get away from WPF.
-
Just search at the top of the screen "Why WP sucks" and you will see why some people (like JSOP ) will envy you!
-
There's ah uge difference between doing what MS want you to do, which WPF does very well, and doing what you want to do. The lower the level, not that C# is low level, of the language, the more flexible it becomes. On the flip, the higher level requires less lines of code for /standard/ operations.
Panic, Chaos, Destruction. My work here is done.
-
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 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.