|
Ravi Bhavnani wrote:
I guess it's very different if you're supporting an SDK/lib.
You bet!
|
|
|
|
|
Nishant Sivakumar wrote:
the same code base on VC++ 6 and one or both of VC++ 2003, VC++ 2005?
Nah. Ported all code to VC++ 7.1 two years ago with only minor to moderate problems.
However, it seems I'll have to port some of it to GCC on Linux. Now, that's going to be fun.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
The current VC6 projects are all legacy.
But our shared codebase, exactly code modules that are shared between the projects is also used in the old VC6 projects.
The greatest problem is the loop conformance, but we started years ago with the following define thats fixes the problem:
#if _MSC_VER < 1300
#ifdef MFX_USE_STANDARDFOR
#define for if(0);else for
#endif
#endif
So loop conformance was never a problem for us.
templates are... 
|
|
|
|
|
Yep, the VCF runs on VC6 (this is what I use to develop it on at home), and several of the other members make sure it builds and runs on VC7.0, and VC7.1. No word on 2005 yet.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
SELECT * FROM User WHERE Clue > 0
0 rows returned
Save an Orange - Use the VCF!
|
|
|
|
|
Do people use VS2005 for developing commercial applications? It's still a beta so I feel like it's a little bit premature to use it, isn't it?
Marc Soleda
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
marcdev wrote:
Do people use VS2005 for developing commercial applications? It's still a beta so I feel like it's a little bit premature to use it, isn't it?
I guess you could start develoiping with the Beta and when it's officially launched, you can re-compile your code in the final version. It'll give you a head-start. On the other hand, if you wait till it's released, you lose precious time.
|
|
|
|
|
Nishant Sivakumar wrote:
if you wait till it's released, you lose precious time.
I lost precious time getting the code to compile on the betas because they were, to put it mildly, garbage. Finally, with the RC build, VS2005 doesn't get confused with the project dependencies, finds the meta data, etc.
I'm more than happy to wait for the release version of VS2005. And my clients have all said, "don't use .NET 1.1 and VS2005 until the official release", followed by "and we're quite happy with .NET 1.1. Let's see if there are stability problems with .NET 2.0 / VS2005."
So, it's fun to play with, but the reality is, my clients are slow adopters.
Marc
My website
Traceract
Understanding Simple Data Binding
Diary Of A CEO - Preface
|
|
|
|
|
Yeah, that's my feeling about it. That's why I ask it for, to know about the people that vote for VS2005.
Marc Soleda.
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
Yes, I understand this as you can't release any commercial app with a beta but as it's still a beta, people should be encountering with some problems that might cause them hours of its time that might be very important in the cost of projects.
Marc Soleda.
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
|
You can't use VS2005 for commercial development, since the runtime is beta and not distributable. Q.E.D.
Software Zen: delete this;
|
|
|
|
|
|
Paul Watson wrote:
VS2005 and .NET 2.0 are already GoLive.[^]
Also, even if they weren't, you would only be porting your code to the new compiler (each new C++ compiler breaks code that compiled in the previous). You wouldn't be actually releasing it. By the time the final release is out, you'd have ported most of it and then you could quickly do a full rebuild with the final compiler [just to be safe it's all ok] and release your product.
|
|
|
|
|
Hmm. OK, I'll grant that it's licensed.
Regardless, in my case, we do not develop or distribute using beta products as a matter of policy. We've gotten burned in the past (mainly by hardware vendors) where we've used beta products, and have then been forced to re-engineer something once the final version is released. This may mean we're a step behind the times, but it does reduce our risk.
Once Visual Studio 2005 is released, I wouldn't be surprised that we install it and start testing with it almost immediately.
Software Zen: delete this;
|
|
|
|
|
We've not committed to it for development, but we're doing test builds with our codebase to catch any porting issues before they become an "issue"...
As we write extensibility products for VS we're also of course testing with VS2005 as a platform, using code written in VS2003.
Anna ![Rose | [Rose]](https://codeproject.freetls.fastly.net/script/Forums/Images/rose.gif)
Riverblade Ltd - Software Consultancy Services
Anna's Place | Tears and Laughter
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
|
|
|
|
|
If your software project is due out after the release, why not.. you get all the goodies now. Just depends on how much risk you are prepared to have...
|
|
|
|
|
Eddie de Bear wrote:
you get all the goodies now
But, what I was thinking of is if all are goodies or there are quite a lot of problems that may be solved after the final release of VS ...
Marc Soleda.
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
What other environment can I use for MFC development?
/Gywox
|
|
|
|
|
NT4.
I still have to code for it. 
-------------------------------
DEBUGGING : Removing the needles from the haystack.
|
|
|
|
|
VC++ 5, VC++ 4 and older versions
|
|
|
|
|
PWB, programmers workbench 
Blogless
|
|
|
|
|
After trying to use PWB (a verrrrry long time ago), I find it hard to believe anyone ever built anything with it. It was a monster PITA.
Software Zen: delete this;
|
|
|
|
|
Pocket PC/Windows CE 
|
|
|
|
|
me too using eVC++ 3.0 and eVC++ 4.0 compilers.
|
|
|
|
|
Isn't linux possible using grashopper??
John
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
