Windows 7/64 + Office Professional 2007 and finally Visual Studio 2010 RC

[Just D]

Here is a pretty funny combination described above. After everything was
installed every time when I start Excel I see the warning that the Visual
Studio needs to be configured. There is a 100% correlation with Excel, no
doubt at all. Although the VS was configured, I was using it for a few
times, it starts on the first click with no questions asked, and it doesn't
require any configuration, information gathering, etc. Nevertheless, I can't
just start Excel, the system calls the Visual Studio configurator and it
endlessly loops... until I click Esc. What's going on? Did anybody else get
the same issue? What's the solution? To delete the VS2010? It is a good
idea, but the purpose was to install and test it.

Just D.

 

[Peter Foldes]

idea, but the purpose was to install and test it.

VS2010 Beta is not to be installed on a production machine,Besides VS2010 is a high
end program and from your post it does not seem you understand what it is used for.
Installing it incorrectly will get you the issue you are now experiencing

 

[DanS]

VS2010 Beta is not to be installed on a production
machine,

There's no indication of what type of machine it is.

Besides VS2010 is a high end program and from your
post it does not seem you understand what it is used for.

How do you come up with that conclusion ?

Installing it incorrectly will get you the issue you are
now experiencing

OK. What is the 'correct' way ?

 

[Just D]

\>"Peter Foldes"

VS2010 Beta is not to be installed on a production machine,Besides VS2010
is a high

We never install any Visual Studio on production servers. This is my
personal and actually my development machine.

end program and from your post it does not seem you understand what it is
used for.

The Visual Studio is High end? Then what is Microsoft Office?

Installing it incorrectly will get you the issue you are now experiencing

From your opinion what is correctly and incorrectly? Since I spent 31 years
writing programs and the half of this time assembling and trouble shooting
computers, networks, and different software systems I suppose I know how to
correctly install systems and programs. So what's your point?

Just D.

 

[Bill Yanaire]

\>"Peter Foldes"


We never install any Visual Studio on production servers. This is my
personal and actually my development machine.


The Visual Studio is High end? Then what is Microsoft Office?


From your opinion what is correctly and incorrectly? Since I spent 31
years writing programs and the half of this time assembling and trouble
shooting computers, networks, and different software systems I suppose I
know how to correctly install systems and programs. So what's your point?

Just D.

His point is that he was coming off a drug infested high and stumbled over
to the computer. He should have had more alcohol and put down the cocaine.

 

[Bill Yanaire]

VS2010 Beta is not to be installed on a production machine,Besides VS2010
is a high end program and from your post it does not seem you understand
what it is used for. Installing it incorrectly will get you the issue you
are now experiencing

Obviously you head is shoved up your ass too far. I suggest getting a
crowbar and pry it loose. Please don't completely remove your head as it
may splat on the floor.

 

[Andrew]

Here is a pretty funny combination described above. After everything was
installed every time when I start Excel I see the warning that the Visual
Studio needs to be configured. There is a 100% correlation with Excel, no
doubt at all. Although the VS was configured, I was using it for a few
times, it starts on the first click with no questions asked, and it
doesn't require any configuration, information gathering, etc.
Nevertheless, I can't just start Excel, the system calls the Visual Studio
configurator and it endlessly loops... until I click Esc. What's going on?
Did anybody else get the same issue? What's the solution? To delete the
VS2010? It is a good idea, but the purpose was to install and test it.

Just D.

I haven't had that issue but my VS2010 RC machine also has Office 2010 beta
on it.
Perhaps you could try the office install on that machine, as uninstalling VS
is a major pain.
The other thing I would suggest is running the Office 2007 setup and trying
a repair, or uninstalling Excel, and then reinstalling it.

 

[John E. Carty]

VS2010 Beta is not to be installed on a production machine,Besides VS2010
is a high end program and from your post it does not seem you understand
what it is used for. Installing it incorrectly will get you the issue you
are now experiencing

Visual Studio 2010 is no longer in Beta and has been released to
manufacturing

 

[Bill Yanaire]

Visual Studio 2010 is no longer in Beta and has been released to
manufacturing

and to the people who have MSDN.

 

[Just D]

"John E. Carty"

Visual Studio 2010 is no longer in Beta and has been released to
manufacturing

If MSDN support was that fast... We grabbed this version from MSDN just
yesterday, it's still RC.

Btw, I will never recommend anyone to install the MS Office Proofing Tools
taken from MSDN as well. I'm not sure, but the first impression that some
Asian drunk guy compiled this version for himself and then published it on
MSDN by mistake. Why Asian? I added one more language for myself, then after
I installed this so called Proofing Tool package it added me Korean,
Japanese and 2 Chinese languages, but deleted my one. I deleted these
worthless languages and reset my one. Just a couple hours after that same
history - 4 more Asian languages were added automatically. Who's so drunk in
MS publishing this stuff??? So I finished up last working day deleting the
Proofing Tools. Today morning I got one more surprise. The login screen, the
system wants me to type the password. You will never expect, that's
Microsoft! There is a keyboard switcher at the top left side of the
screen. I clicked and did regret right after I did that. There are two
languages - English and Chinese! I never installed it! I don't use neither
know it! So who is this drunk Chinese guy working for Microsoft and
publishing these traps to MSDN?

Here is how it looks like.

http://members.cox.net/dshvetsov-home/Languages!.jpg

Can't ignore the latest "improvements" made to the mail/newsgroup system so
called Live Mail. I'd better call it DeaD mAiL or something like that. If
Outlook keeps the messages in just a few files, Outlook Express keeps
messages in the number of files correlated to the number of folders inside,
the so called Live mail keeps the trash in separate files. I subscribed to
one newsgroup. The client showed me 100,000 messages. And I clicked
Catch-Up. A few minutes later it showed me the window in the center of the
screen that it will take approximately 60 seconds. Two hours later I killed
the client and restarted it. Just for curiosity got the number of files in
the mail subdirectory including the whole tree. You will never believe -
95,000 files! Separate files!!! Is that fast? No! Is that efficient to keep
these files on disk? No! Does it provide a fast maintenance? No! MS guys
have no clue about simple database formats or something? Or they just fired
the people knowing this stuff? Maybe be. Nowdays the software world is full
of contractors. I hate this approach, but this is true. The first 2-3 months
the new guy learns what's done, next 1-2 months he tries to get what the
company wants him to write. The next 2-3 months the guy spends on the
Internet searching for a new contract because this one is about to be
finished. Who writes the code and when? A big question. I see the quality of
the code dramatically changing you know to what direction. At least the
latest mail and newsgroup client is such a crap that I cant' use it that
efficiently that I was using previous clients like Outlook Express. Weird!

Just D.