.Net XPeriences
2002-02-20 18:37:34+01 by
Dan Lyke
6 comments
Dave Winer has some musings on the News.com article about Microsoft backpedaling on .Net. I know I've been trying to install Visual Studio .Net under XP, and it sure ain't "apt-get install vs-net". Web pages which have complex "open this control panel, make sure this setting is on" sort of things. Hidden directories that I can type in to get to, but can't figure out how to set the browser to show. Now the installer is in a state that it always thinks part of it is running, even after I've restarted. Clear that there's a lot of work left to be done before .Net and XP are usable.
[ related topics:
Business Dave Winer Microsoft Current Events Work, productivity and environment
]
comments in descending chronological order (reverse):
#Comment made: 2002-02-22 16:45:40+01 by:
Dan Lyke
Aha! It seems that unzipping the self-extracting archive to the location it suggests is a bad idea, that that location has special meaning and something gets confused about finding files in the place it's running from.
#Comment made: 2002-02-21 16:33:53+01 by:
Mike Gunderloy
If it's not too late, there is a utility called MsiZap that can wipe out the Installer service's memory of a failed install. That will return you to a relatively clean state to try again.
On the other hand, if things are that bad a wipe & restart are probably in order anyhow.
#Comment made: 2002-02-21 16:14:26+01 by:
Dan Lyke
Argh. Well, I don't know what else to do, I'm down to "wipe the disk and start over", I guess. Sigh. It takes me years to get a Linux system into that state of bit-rot.
#Comment made: 2002-02-21 06:35:31+01 by:
Dan Lyke
I've got Visual Studio's install telling me it can't start component setup right now. I've a sneaking suspicion that "restart" doesn't mean "restart", so I've shut down the machine and I'll try again in the morning.
#Comment made: 2002-02-21 06:35:30+01 by:
Mike Gunderloy
I told you not to use WinXP :)
Clearly, mileage varies. I rebuilt a server yesterday with Win2K + SQL Server 2K + .NET + up-to-date security patches and service packs, and though it took FAR too long, it all worked fine. It wasn't apt-get, but I did take almost entirely defaults and had no special problems.
#Comment made: 2002-02-21 06:35:29+01 by:
Dan Lyke
To try when I get home: http://zappadoodle.com/ has some extremely simple C code to BSOD a Win 2000/XP box.
We will not edit your comments. However, we may delete your
comments, or cause them to be hidden behind another link, if we feel
they detract from the conversation. Commercial plugs are fine,
if they are relevant to the conversation, and if you don't
try to pretend to be a consumer. Annoying endorsements will be deleted
if you're lucky, if you're not a whole bunch of people smarter and
more articulate than you will ridicule you, and we will leave
such ridicule in place.