|
I am right there with you, buddy! -But only so far...
Moving from Turbo C++ and Turbo Pascal (1.0/DOS) to the Windows-based ones was quite an experience...! Remember Memory Models and using Overlays for larger executables?
My road only goes down as far as using cassettes for storage on TRS-80s and C= machines... None of that punch-card-deck or paper-tape stuff for me; that is before my time! Although I have used hard-copy terminals before! -Not for development work.
Peace!
-=- James
Tip for inexperienced drivers: "Professional Driver on Closed Course" does not mean "your Dumb Ass on a Public Road"! Articles -- Products: Delete FXP Files & Check Favorites
|
|
|
|
|
James R. Twine wrote:
Overlays for larger executables
Must. resist. flashback. Oh no...
My senior project in college (Wright State University, 1984) was a demonstration of a 3D hidden surface removal algorithm using Binary Space Partitioning[^] trees. It included several other significant algorithms in the rendering process.
Since this was done on a 64K CP/M system, rendering a single image took 5 overlay swaps, and about 2 minutes.
Software Zen: delete this;
|
|
|
|
|
Hmm, BSP trees are still quite often used in modern games, although there not used for the traditional reasons probably used back in the 80s
|
|
|
|
|
And I had no idea VS97 existed. I remember buying the student version of VC5, and when I started working there was a brand new VC6.
--
Weiter, weiter, ins verderben.
Wir müssen leben bis wir sterben.
I blog too now[^]
|
|
|
|
|
No more doing surveys after midnight.
You're right though - I was getting VC and VS mixed up.
cheers,
Chris Maunder
|
|
|
|
|
Michael Dunn wrote:
I thought Visual Studio 97 was version 5, then MS went back to version numbers again with v6 in 1998.
I was using VS/VC 5.0 until my company switched to VS.NET. To me there are only two and a half versions of VS/VC prior to VS.NET, 1.51, 4.0 (used only briefly), and 5.0, the rest do not exist.
My articles and software tools
|
|
|
|
|
I would like to vote for VS 2005 but I've only seen it in the Channel 9 demos and not actually used it. (I won't let myself use beta software for development)
Having to go back and use VS 6 is painful but thankfully I've only got one active project that still uses it.
Although I still feel that the resource editor for C++ projects is better in VC6 rather than the one in VS2003 - especially when trying to copy resources between projects. Oh and editing icons is a lot nicer in VC6 too.
The only annoying thing in VS2003 is the dynamic help. Everytime you think you've turned it off, back it comes again.
Michael
CP Blog [^]
|
|
|
|
|
|
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.1\Dynamic Help\Never Show DH on F1=YES
|
|
|
|
|
Fastest, without double-bufferred owner drawn interface, including the most lightweight versions of mfc and atl.
P.S. Especially convenient in combination with WndTabs and Visual Assist.
#define __ARMEN_H__
|
|
|
|
|
Hear hear to that!
Also:
Far better than anything later, for the visually impaired.
Panes that go where you put them, and stay there.
An altogether cleaner interface with less stuff getting between me and what I want to do.
Rob in the West Riding
|
|
|
|
|
|
VS.NET 2003 is good in it's own right, but they really screwed up the resouce editor.
If you need c++ developement and need to use the resouce editor, VC6 is the best.
|
|
|
|
|
I used VS .NET (whatever the first release was) for awhile, but the problem was that my principle language is C++ and there were too many little problems. After that I went back to VS 6.0 and am yet to dive back into .NET of any kind.
|
|
|
|
|
My vote is for 6.0
In 6.0 there are 4 toolbar buttons: "Call Graph", "Callers Graph", "Derived Classes and Members", and "Base Classes and Members" that I have used constantly for years. I have only been able to find the latter capability ("Base Classes and Members") in VS.NET
Sonork ID 100:25668 Home Page
|
|
|
|
|
Manish K. Agarwal wrote:
have only been able to find the latter capability ("Base Classes and Members") in VS.NET
So I'm not the only one then, Call and Callers graph were so useful, what were MS thinking by removing them, Duh!
Phil Harding
|
|
|
|
|
I think my vote will change shortly after I get and use the final release of Visual Studio 2005.
Some of the developer features (refactoring for instance) look really helpful but the last build I tried was a bit of a hog (and that wonderful choice of a background gradient in the toolbars made my eyes water.)
For now VS.NET 2003 is doing nicely.
regards,
Paul Watson
South Africa
The Code Project
|
|
|
|
|
|
Oh twister of words and wielder of dot dot dot! :P
From what I have seen, shortly after I get VS 2005, it will become my favourite. Till then I'll keep VS 2003 charged and ready.
regards,
Paul Watson
South Africa
The Code Project
|
|
|
|
|
Yeah, from what I've heard that will be true but there is no way in hell were going to spend a second on 2005 until it's been out long enough for the initial bug fixes. Were just too busy to take a chance like that.
Besides I'm just getting used to the endless rebuilding of the entire project when I make a change to a business object in my solution and my UI suddenly doesn't see any intellisense or autocomplete (or whatever that feature is called) any more for *all* my business objects.
What is odd is that I have yet to see any bit of VS 2005, but our latest update to the Infragistics UI framework has that as a style option for every control so I can imagine what it's going to look like.
|
|
|
|
|
When will the public version of vs 2005 be released?
Don't try it, just do it!
|
|
|
|