Re: does VS C++ 2005 actually work????
Of course, this is a different issue from those raised by the OP.
But I've also dealt with these tons of new warnings. On the one hand, it's
irritating to have to deal with tons of warnings in working code. But on the
other hand, I think the goal is worthwhile. Microsoft gets a lot of
justified criticism regarding the reliability of Windows. Most of these
problems are due to faulty software running on Windows, most written by
folks who would claim they know how to program just fine.
Early versions of C compilers did not warn when unprototyped functions were
called. The compiler just assumed undefined functions returned an int. Over
the years, compilers have got more and more picky in an effort to impose
additional type safety. I think it is reasonable to expect this trend to
continue.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
"Sgt. York" <york@frontlines.org> wrote in message
news:79Odnad30YoV-RLZnZ2dnUVZ_sidnZ2d@scnresearch.com...
Yeah. Well, our company got the 90-day trial DVD and three of us
volunteered to install the beast for a trial run. We proceeded to import
several MFC projects originating from vs.net 2003. In return we were
bombed with warnings about the c functions (which is condescending---we
know the risk but chose to take it anyway, stop pestering us) and
intellisense only worked sometimes (even after rebuilding it numerous
times). In fact, I personally found intellisense failing far more often
than it ever did in 2003 and given its new, even more enormous size, you'd
think nothing would escape it.
This is a paraphrase (we had many other issues), but in the end we opted
not to upgrade. Admittedly we are a c++ shop that is still not impressed
with the evangelical attitude of MS toward .NET (we are also
cross-platform), but the whole "feel" of VS 2005 was one of "yeah, this
great .NET tool still does some incidental c++ on the side." No thanks,
Microsoft.
Tom Serface wrote:
I also didn't experience any problems. I've been using it for many
months now full time and it has worked fine. You could try totally
uninstalling it and reinstalling just to make sure something didn't go
whacky during installation.
Tom
"Ian" <Ian00Bell@yahXX.com> wrote in message
news:LUFjg.23372$U84.473812@wagner.videotron.net...
I recently purchased Microsoft VS 2005 and just cannot seem to get it
working.
1. I tried converting a VS 2002 solution to VS 2005. It took a while
to realize there is a bug in Intellisense. The only solution was to
disable Intellisense.
2. It seems class view has been rendered inoperable now that
Intellisense has been disabled. So this means browsing by namespaces
and classes is not possible.
3. I tried debugging the application but it seems the debugger cannot
find certain debug libraries such as 'MFC80UD.DLL'. I posted a message
and hope someone will know what is happening. I reviewed a number of
postings which seemed to suggest it may be necessary to modify the
manifest file. I also reviewed several postings regarding
redistributable files. But is this all really necessary? After all,
I'm just trying debug the application using the IDE.
4. So I downloaded the sample program DBViewer to see if I could run the
debugger on this application. The compiler skipped the entire set of
files and refused to build it.
I am very disappointed with this product and feel like I've wasted my
time and money on it. If asked, I would strongly discourage anyone
from buying to VS 2005.
I really don't know what question to ask at this point. If I cannot
even compile and debug a sample program provided by Microsoft then where
do I begin???? I've uninstalled and reinstalled VS several times.
Are there any Microsoft folks willing to take a stab at helping me out.
I suppose if I really wanted a working solution, I should have paid
several thousands of dollars for a support contract....
My system: 2.26GHz Pentium 4, 2gig RAM, WinXP Pro, VS 2005 Pro
Ian