ANN: VS.NET 2003 SP1

[Pieter]

On my machine it sat there literally 10 minutes before it came up and
asked me if I wanted to install it, then sat there another I don't know
how many minutes before I gave up and cancelled it. It wasn't pretty.

Matt

Same thing here.
But after 20 minutes it installed

 

[Andrew Morton]

Hi Bo,

Here is my guess: your file is corrupted and some sort of caching
(proxy?) gives you the same corrupted file.
Try downloading on another computer...

The MD5 Sum (using winmd5sum from solidblue software) for
VS7.1sp1-KB918007-X86.exe is
d5210672e8fe06c7f870476dc08f4393

if you want to check the integrity of the download (although I thought the
installer checked its own integrity).

Andrew

 

[Bo Persson]

HI all

I am getting an error message when installing the VS2003 sp1.
The error is "PCW_CAB_VS" is corrupt .

I have tried 2 DVD installation disks from MSDN and still no result.
Any help with this issue would be appreciated.

I have seen the same thing with the download version, so that rules
out a media problem.

No idea what the real problem is though. :-(


Bo Persson

 

[Bo Persson]

The MD5 Sum (using winmd5sum from solidblue software) for
VS7.1sp1-KB918007-X86.exe is
d5210672e8fe06c7f870476dc08f4393

if you want to check the integrity of the download (although I
thought the installer checked its own integrity).

Andrew

Ok I tried that now, it checks out.

Some other ideas?


Bo Persson

 

[Guest]

Note to folks:

Many of the project settings need to be set back to their initial
configuration after upgrading.

For instance, the startup project for my solution changed.

Also, the Debug Information Format for one of my files was disabled... which
made using the debugger a challenge until I figured it out.

So, if there's weirdness, double check your project properties.

Also... where is the right place for submitting issues? I also had a wierd
(not yet repeated) psuedo-crash when I tried to run the debugger. Graphical
garbage (partially drawn windows, etc.) flickered and nothing else happened
until I stopped the debug. I restarted VS and I haven't seen it since.

-j

 

[md]

Hmmm... apparently I need to be more patient. I just wish it at least
indicated it was doing something.

Matt

 

[Andrew Morton]

Ok I tried that now, it checks out.

Some other ideas?

Have you done a repair of your VS.NET installation through control
panel->add/remove programs? (It runs more smoothly if you first put in the
first VS.NET install CD - the dialog box that comes up asking for it can
easily get lost so you end up waiting ages for nothing to happen. Grrrr.)

Andrew

 

[Guest]

Yeah, it totally pisses me off that SPs on such an important tool would take
3 years to release. By the time they get released it wont matter too much to
us anymore since we will probably be working on the next version of VS
anyway. They *are* working on the next 2 or 3 versions of VS as I write this,
so I'm not sure if they will ever give much TLC to SPs.

Either, it's not worth it to them for us to be on the cutting edge of
frameworks or we should just "take it like a programmer" and not whine about
it.

Such a BEAUTIFUL piece of work ruined by such horribly annoying bugs...

 

[Bo Persson]

Have you done a repair of your VS.NET installation through control
panel->add/remove programs? (It runs more smoothly if you first put
in the first VS.NET install CD - the dialog box that comes up asking
for it can easily get lost so you end up waiting ages for nothing to
happen. Grrrr.)

Andrew

Ok, so I tried this too.

Didn't help!


Bo Persson

 

[Andrew Morton]

Ok, so I tried this too.

Didn't help!

The file in the error message (dbgurt...blah blah blah) is something to do
with the .NET SDK
(http://msdn.microsoft.com/msdnmag/issues/01/02/bugslayer/).

Any chance you could uninstall the .NET SDK so SP1 doesn't try to do
anything with it? I have no files named dbgurt* on my computer (WS2003) and
VS.NET 2003 updated OK.

Otherwise, you may have to resort to waving a large instruction manual at
the computer in a threatening manner

Andrew

 

[Bo Persson]

The file in the error message (dbgurt...blah blah blah) is something
to do with the .NET SDK
(http://msdn.microsoft.com/msdnmag/issues/01/02/bugslayer/).

Any chance you could uninstall the .NET SDK so SP1 doesn't try to do
anything with it?

I am not really using the .NET SDK, so I uninstalled it. There was no
dbgurt file though.

I have no files named dbgurt* on my computer (WS2003) and VS.NET
2003 updated OK.

Neither have I, either before or after uninstallning the SDK

Otherwise, you may have to resort to waving a large instruction
manual at the computer in a threatening manner

Probably.

Now the installation complained that some other file was missing from
the same CAB...

I don't think I bother with this upgrade anymore, as I am mostly using
VS2005 on another computer. Just thought it was a good idea to apply
the upgrade, just in case. Seems that it was not!



Thanks for your help.


Bo Persson

 

[rickyno]

Hi.

I installed this service pack 1 on VS.NET 2003 and i now have something
weird happening. I hope someone can help me on this, i really don't
know if it's normal or not.

When the computer boots and the classic logon box appears, i also see a
visual studio Splash Screen and the logon box loses the focus, though
the devenv.exe GUI is not shown. When logged in, I can see, in the task
manager, the devenv.exe running under the SYSTEM account. After a few
minutes it shuts down by itself...

I went through the registry but could not find any place where
devenv.exe, or it's GUID, would be loaded at machine boot.

Also, after the first reboot after having installed the SP1, many icons
in my machine were mixed-up:
- .xml were now "Windows Script File" and had the .vbs icon
- .sln were now "Windows Service Description Language" and had a wsdl
icon.
and many others too.

Everything was fine before the SP1.
I can still develop without problems but i really don't like what
happened and the devenv.exe at boot up.

Anyone knows if this was reported by other people?
Is there something i simply forgot to read? (i read the release notes)

Rick

 

[mike.loux]

I'm running into a strange issue that seems to be new to SP1. Every so
often (I've seen this twice in the week since I've installed SP1) when
in design mode, all of my formatting menu items and toolbar items
(Align, Make same size) as well as Cut, Copy, Paste, etc are completely
disabled, and I have to shut down and restart VS.NET completely in
order to get those abilities back. It happens without warning; I'll be
designing a form and all of the sudden I can no longer paste, or align,
or whatever.

Has anyone else run into this? Is anyone else as irritated as me that
they didn't really fix anything useful (it's still as slow and
unpredictable as it always was, only worse) in the intervening 3 years
since this thing was released? Sheesh! I'm almost afraid to do
anything in VS 2005, for fear that it will be even worse!

 

[Pieter]

it actually is much much worse in VS 2005 :-(

 

[Andrew Morton]

I installed this service pack 1 on VS.NET 2003 and i now have
something weird happening. I hope someone can help me on this, i
really don't know if it's normal or not.

When the computer boots and the classic logon box appears, i also see
a visual studio Splash Screen and the logon box loses the focus,
though the devenv.exe GUI is not shown.

<snip>

It may be a left-over .bat file from the updater. Get yourself a copy of the
Startup Control Panel from www.mlin.net and use it to look for the obvious.

Andrew