|
"30% of the people are very easy to fool." - Abraham Lincoln.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
pwasser wrote: "30% of the people are very easy to fool." - Abraham Lincoln.
I really doubt he said that.
Oh, wait a second. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I'm 30% convinced you're human.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
And 70% convinced that he is a terminator, 
Shuvro
|
|
|
|
|
|
ridoy wrote: For the first time in the history of AI, a computer beats the famous "Turing Test"!
No.
Eugene pretended to be 13 years-old and from a different Country. Thus giving an excuse for his bad English and not understanding questions.
Turing made reference to a child, but only as a process stage to developing a fully functional 'adult' machine.
|
|
|
|
|
This is very preliminary information gathering at present; but I've found out I may be tasked with upgrading an elderly windows app, currently running on NT4 and untouched in a decade, to work with modern versions of Windows. So far the discussion's only been at the upper management level; but from the dates involved (and knowing that IIRC our .net app from 05 was the customers first) we're assuming it was written in Visual C++/MFC; a platform I dabbled with in school but never used for anything real.
Since MS no longer offers anything prior to VS2002 via MSDN I'm wondering how much pain I'm likely to be in for in just getting it to compile under newer tools.
PS I'm really hoping it's not so old as to be a win16 app. I've never written win16 code; but from what I've read on The Old New Thing, it's enough of a Codethulu-elephant that by the end of porting something from then I'd probably be able to drink Nagy under the table. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Visual C++/MFC is still a supported and active environment up to and including the latest version of Visual Studio. My guess is that you should be able to upgrade the project in the latest Visual Studio and should be able to build ok. Make sure you install MFC when setting up studio (I noticed in VS2013 that was an option during install). Tools/frameworks come and go but MFC keeps chugging right along 
|
|
|
|
|
Dave Calkins wrote: Make sure you install MFC when setting up studio (I noticed in VS2013 that was an option during install)
Looks like I'm good here. I fired up VS2012, picked MFC app from the new project dialog and got a working hello MFC app when I clicked the run button.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
so then you should be able to open the solution file in VS2012 (or since its an older project maybe the workspace file or whatever it was called then) and let it upgrade it. you might then just be able to build and run.
|
|
|
|
|
Probably lots of warnings and some deprecated functions but it is even possible that it will work without touching anything (nah, I was joking in this last part  )...
|
|
|
|
|
If it comes to pass you should consider an article for CP.
Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master. ~ George Washington
|
|
|
|
|
Mike Mullikin wrote: If it comes to pass you should consider an article for CP.
I suspect work related NDAs would scuttle any hope of a useful article unless I scoured the internet to find someone elses VC6 legacy project I could use as an example in a writeup. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Dan Neely wrote: I suspect work related NDAs would scuttle any hope of a useful article...
Yeah, I'm in the same boat.
Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master. ~ George Washington
|
|
|
|
|
"I do cool stuff but if I told you about it we'd both have a really bad case of the attack lawyers where the sun don't shine" is rather limiting as small talk at times. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Mm, I've got some interesting things to say as well and can only do really high level articles (though there might be one of those in the pipeline).
|
|
|
|
|
If it's VC6 then it is unlikely that it is a 16-bit app. VC4 on is 32-bit. As pointed out by others, your biggest problem is likely to be 3rd party libs.
Da Bomb
|
|
|
|
|
if it's all standard MFC with no external 3rd party libs, it should be a fairly straightforward conversion. and if you can stick to Win32, the job will be much simpler.
|
|
|
|
|
Dan Neely wrote: it's enough of a Codethulu-elephant that by the end of porting something from then I'd probably be able to drink Nagy under the table
Ever wondered what project Nagy encountered?
|
|
|
|
|
Now isn't that a scary thought. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
One thing that's prevented me from using anything more modern than VC6 for this[^] app is my reliance on CString, whose size increased over the years. Rather than fight this, I decided to convert the app to .NET in its next incarnation.
Also see this[^] MSDN link for additional data points.
/ravi
|
|
|
|
|
If it was passed by reference instead of by value, the code works seamlessly. What I find is a lot of the VC6 code normally pass CStrings by value.
|
|
|
|
|
I was referring to serialization of CString breaking between VC6 and VS2005+.
/ravi
|
|
|
|
|
I've converted several apps from earlier version of Visual Studio to the latest, including a 16-bit app. Quite often, I've solved several bugs along the way due to improved error checking by the compiler. It isn't that difficult and requires patience and being methodical. (I found it easier to concentrate on one file at a time. Once I get it working with Warning Level 3, I go to Warning Level 4 and apply a set of additions and exceptions I've found work really well.)
|
|
|
|
|
You're likely to find some issues because you're moving from pre-98 Standard C++ to C++ 11(ish) if you're going to migrate to VS2013... I started developing a project with VC6 back in 2001/2 that I've maintained ever since. It moved to VS2003 in 2005, VS2008 in 2010, VS2010 in 2012 and to VS2013 in the last month. I had the most problems moving from VC6 to VS2003, but after that, VS2010 to VS2013 had the most issues, all due to improved C++ standards compliance. Oh - and some deprecated Platform SDK / C runtime functions - but those deprecation warnings can be turned off with macros (or you can modify your code to conform with the warnings, of course).
However...take a copy of the project. Open it in VS2013. Rebuild. Fix compile errors. Rinse & repeat... Just do it, I suspect it'll be easier than you might think.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
