473,246 Members | 1,886 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,246 software developers and data experts.

MSDN Library problem

dw
Hello, all. I have a problem with VS.NET 2003: Everytime it's starting up,
it brings up a window saying: "Please wait while Windows configures MSDN
Library for Visual Studio .NET 2003." It then takes a good 10 minutes to do
its configuration. I've uninstalled VS and MSDN and re-installed both; I've
run the repair on both, but no results. It's like the registry is messed up
and not getting cleaned with the uninstalls. I spend all day today
uninstalling/installing to no avail. It's very frustrating. The problem
seems to have started when I installed Visual Studio Web Developer 2005
Beta. That's been uninstalled along with .NET 2.0, but still no solution.
Any ideas? Thanks.
Nov 18 '05 #1
8 1177
I had this problem once with a 2003 beta. It took a manual cleansing
of the registry to get everything back to normal. I can't find any
documents now to describe the process.

One tool you might be able to use is REGMON from sysinternals.com. You
can see what is being accessed and try to clean up - unfortunately,
it's a lot of work. I keep all the beta stuff on a virtual machine now
to avoid the headaches..

--
Scott
http://www.OdeToCode.com

On Sun, 12 Sep 2004 22:21:51 -0400, "dw" <co***************@uncw.edu>
wrote:
Hello, all. I have a problem with VS.NET 2003: Everytime it's starting up,
it brings up a window saying: "Please wait while Windows configures MSDN
Library for Visual Studio .NET 2003." It then takes a good 10 minutes to do
its configuration. I've uninstalled VS and MSDN and re-installed both; I've
run the repair on both, but no results. It's like the registry is messed up
and not getting cleaned with the uninstalls. I spend all day today
uninstalling/installing to no avail. It's very frustrating. The problem
seems to have started when I installed Visual Studio Web Developer 2005
Beta. That's been uninstalled along with .NET 2.0, but still no solution.
Any ideas? Thanks.


Nov 18 '05 #2
dw
Thanks, Scott. The beta tools caused headaches both on my home and work
systems. I now have them on a Virtual PC to keep my main system clean. Alas,
for this problem, it's too late. I'll download the regmon and see what I can
find out. Thanks.

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:mg********************************@4ax.com...
I had this problem once with a 2003 beta. It took a manual cleansing
of the registry to get everything back to normal. I can't find any
documents now to describe the process.

One tool you might be able to use is REGMON from sysinternals.com. You
can see what is being accessed and try to clean up - unfortunately,
it's a lot of work. I keep all the beta stuff on a virtual machine now
to avoid the headaches..

--
Scott
http://www.OdeToCode.com

On Sun, 12 Sep 2004 22:21:51 -0400, "dw" <co***************@uncw.edu>
wrote:
Hello, all. I have a problem with VS.NET 2003: Everytime it's starting up,it brings up a window saying: "Please wait while Windows configures MSDN
Library for Visual Studio .NET 2003." It then takes a good 10 minutes to doits configuration. I've uninstalled VS and MSDN and re-installed both; I'verun the repair on both, but no results. It's like the registry is messed upand not getting cleaned with the uninstalls. I spend all day today
uninstalling/installing to no avail. It's very frustrating. The problem
seems to have started when I installed Visual Studio Web Developer 2005
Beta. That's been uninstalled along with .NET 2.0, but still no solution.
Any ideas? Thanks.

Nov 18 '05 #3
dw
Would a registry tool like Tunup Utilities from http://www.tune-up.com/
help? I've used that before and it's the least destructive of all registry
cleaners.

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:mg********************************@4ax.com...
I had this problem once with a 2003 beta. It took a manual cleansing
of the registry to get everything back to normal. I can't find any
documents now to describe the process.

One tool you might be able to use is REGMON from sysinternals.com. You
can see what is being accessed and try to clean up - unfortunately,
it's a lot of work. I keep all the beta stuff on a virtual machine now
to avoid the headaches..

--
Scott
http://www.OdeToCode.com

On Sun, 12 Sep 2004 22:21:51 -0400, "dw" <co***************@uncw.edu>
wrote:
Hello, all. I have a problem with VS.NET 2003: Everytime it's starting up,it brings up a window saying: "Please wait while Windows configures MSDN
Library for Visual Studio .NET 2003." It then takes a good 10 minutes to doits configuration. I've uninstalled VS and MSDN and re-installed both; I'verun the repair on both, but no results. It's like the registry is messed upand not getting cleaned with the uninstalls. I spend all day today
uninstalling/installing to no avail. It's very frustrating. The problem
seems to have started when I installed Visual Studio Web Developer 2005
Beta. That's been uninstalled along with .NET 2.0, but still no solution.
Any ideas? Thanks.

Nov 18 '05 #4
Hmm - could be - I've never used that tool.

On Mon, 13 Sep 2004 12:57:15 -0400, "dw" <co***************@uncw.edu>
wrote:
Would a registry tool like Tunup Utilities from http://www.tune-up.com/
help? I've used that before and it's the least destructive of all registry
cleaners.


--
Scott
http://www.OdeToCode.com
Nov 18 '05 #5
dw
Found something interesting: When I let VS.NET go through its process of
"configuring" the problem and then I run the Tune-Up utility, it shows the
problem keys in the registry. I'm planning to write them down and clean them
manually. The program cleans them, but then VS.NET sets about doing its
funky stuff.

My issue is this: Why isn't it clearly stated on the download page for the
beta tools that they could screw up our machines so bad we'd have to resort
to this kind of stuff? I know when we agree to the EULA we let them do
anything they want, but still, a little heads-up warning would be nice for
those of us dumb enough to think this stuff is safe to install on anything
other than Virtual PC.

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:3q********************************@4ax.com...
Hmm - could be - I've never used that tool.

On Mon, 13 Sep 2004 12:57:15 -0400, "dw" <co***************@uncw.edu>
wrote:
Would a registry tool like Tunup Utilities from http://www.tune-up.com/
help? I've used that before and it's the least destructive of all registrycleaners.


--
Scott
http://www.OdeToCode.com

Nov 18 '05 #6
> My issue is this: Why isn't it clearly stated on the download page for the
beta tools that they could screw up our machines so bad we'd have to
resort
to this kind of stuff? I know when we agree to the EULA we let them do
anything they want, but still, a little heads-up warning would be nice for
those of us dumb enough to think this stuff is safe to install on anything
other than Virtual PC.


the word BETA says it all
Nov 18 '05 #7
yes BETA products mean... this is what its going to look like but hey... we
havent finalised anything (specially when you refer to beta 1) and keep your
fingers crossed that it doesnt screw up you PC..

i have win 2k3 64 on a gig of ram with vs.net 2k5 and sql 2k5 beta 2.. runs
at 500+ megs plus without me doing anything... if i do anything .. it
complains about running out of virtual memory.. so one more thing... they
are not optimised... neither for processor nor for memory.

and lastly welcome to beta product testing... its fun... after a while you
keep your system clean by re-installing and then get onto using driveimage
etc to start fresh.

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:O4**************@TK2MSFTNGP10.phx.gbl...
My issue is this: Why isn't it clearly stated on the download page for the beta tools that they could screw up our machines so bad we'd have to
resort
to this kind of stuff? I know when we agree to the EULA we let them do
anything they want, but still, a little heads-up warning would be nice for those of us dumb enough to think this stuff is safe to install on anything other than Virtual PC.


the word BETA says it all

Nov 18 '05 #8
dw
Thanks, Greg and Hermit. I love Microsoft products; I use them every day and
could not get my work done without them. I guess I hadn't paid enough
attention to the word "Beta" -- nor was I using Virtual PC at that time. I
love beta products -- did beta testing for Corel some years back. You get to
be on the cutting edge of technology. I've learned a hard lesson to install
and use Virtual PC on all my systems before I go putting beta products on
them.

"Hermit Dave" <he************@CAPS.AND.DOTS.hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
yes BETA products mean... this is what its going to look like but hey... we havent finalised anything (specially when you refer to beta 1) and keep your fingers crossed that it doesnt screw up you PC..

i have win 2k3 64 on a gig of ram with vs.net 2k5 and sql 2k5 beta 2.. runs at 500+ megs plus without me doing anything... if i do anything .. it
complains about running out of virtual memory.. so one more thing... they
are not optimised... neither for processor nor for memory.

and lastly welcome to beta product testing... its fun... after a while you keep your system clean by re-installing and then get onto using driveimage
etc to start fresh.

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:O4**************@TK2MSFTNGP10.phx.gbl...
My issue is this: Why isn't it clearly stated on the download page for the beta tools that they could screw up our machines so bad we'd have to
resort
to this kind of stuff? I know when we agree to the EULA we let them do
anything they want, but still, a little heads-up warning would be nice for those of us dumb enough to think this stuff is safe to install on anything other than Virtual PC.


the word BETA says it all


Nov 18 '05 #9

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
by: Jimmy | last post by:
Hi folks, I'm hoping someone has a suggestion to solve this. I've been using Visual Studio Enterprise 6 (just the VB6 part) on my Dell laptop (PIII-700) running Win Me for a few years now, with...
3
by: Kenneth Lai | last post by:
After installed MSDN Library Oct 2003. I got a HTML error "Action Cancel" on the first page and no contents can be loaded. I try reinstall several time and still got this problem. Anyone...
2
by: Chien Lau | last post by:
When using the MSDN library (July 2004 edition), I click the funnel icon to set the language filter to C#. For some reason, it's not retaining my selection. Each new page that I visit requires me...
0
by: TomB | last post by:
I'm using VB.net standard that came with the book "Visual Basic .net step by step" MS Press version 2003. I found out I was missing the MSDN library from book. I contacted MS Press who send them....
14
by: Roland Hall | last post by:
I have two(2) issues. I'm experiencing a little difficulty and having to resort to a work around. I already found one bug, although stated the bug was only in ODBC, which I'm not using. It...
14
by: VMI | last post by:
Everytime I open my machine's MSDN and look for a subject, when I double-click on anything, I get "The page cannot be displayed" . What's wrong?
1
by: brian.oneil2 | last post by:
Is there a way to install this onto a network file share and allow a team to access it? I would say share a CD from a networked CD drive, but there are multiple CD's that would have to be inserted....
1
by: gerry | last post by:
I wrote up a couple of simple SiteMap providers based on the MSDN documentation and examples, in particular the AccessSiteMapProvider example found at...
5
by: Herbert Lukas | last post by:
Hi, during the setup of german MSDN library VS 2006 juli (Disc 3619) the VS 2005 DVD was requested. I inserted both VS 2005 DVD German (Disc 3185) and English (Disc 3070) without success. ...
0
by: abbasky | last post by:
### Vandf component communication method one: data sharing ​ Vandf components can achieve data exchange through data sharing, state sharing, events, and other methods. Vandf's data exchange method...
0
by: stefan129 | last post by:
Hey forum members, I'm exploring options for SSL certificates for multiple domains. Has anyone had experience with multi-domain SSL certificates? Any recommendations on reliable providers or specific...
0
Git
by: egorbl4 | last post by:
Скачал я git, хотел начать настройку, а там вылезло вот это Что это? Что мне с этим делать? ...
0
by: MeoLessi9 | last post by:
I have VirtualBox installed on Windows 11 and now I would like to install Kali on a virtual machine. However, on the official website, I see two options: "Installer images" and "Virtual machines"....
0
by: DolphinDB | last post by:
The formulas of 101 quantitative trading alphas used by WorldQuant were presented in the paper 101 Formulaic Alphas. However, some formulas are complex, leading to challenges in calculation. Take...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: Aftab Ahmad | last post by:
Hello Experts! I have written a code in MS Access for a cmd called "WhatsApp Message" to open WhatsApp using that very code but the problem is that it gives a popup message everytime I clicked on...
0
by: Aftab Ahmad | last post by:
So, I have written a code for a cmd called "Send WhatsApp Message" to open and send WhatsApp messaage. The code is given below. Dim IE As Object Set IE =...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.