To each is own. I love the IDE editor and am very productive in it.
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
The new version sounds like it is overly concerned about safety, but
#pragma warning() can
disable those warnings, so that should be a non-issue.
I don't use IntelliSense because it really doesn't work too well; any
system that shows
the parameter as UINT without giving me a list of the flags I can set or
OR into it is
pretty useless, so I have to look the function up anyway, and besides,
the editor sucks
(nobody at Microsoft has a clue how to write a text editor, but they
keep pretending,
release after release, to have one. I use an external editor which has
no Intellisense
and works just fine).
As I commented in another thread, the desire to use .NET and
"trustworthy programming" is
not a justification for a crappy interface; you can program Java with a
decent interface
(see, for example, Eclipse as a platform). People who have never seen
VS6 immediately
recognize that VS.NET sucks, because they understand how interfaces
SHOULD be built, when
they are built by mature designers, or at least when built by designers
who have adult
supervision.
Most of my clients are hardcore VS6 users, because it was the last
usable version of VS
that Microsoft produced. Some have been forced to move to VS.NET
because it really does
have a great compiler and there are lots of really good features in the
newer versions of
MFC, and they need one or the other of these (sometimes both), but they
well-and-truly
despise the IDE. It is an IDE that only its designer can love. And
apparently does
[further commentary along these lines is not suitable for a family
newsgroup, but feel
free to use your imaginations]
joe
On Tue, 13 Jun 2006 18:23:38 -0700, "Sgt. York" <york@frontlines.org>
wrote:
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
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm