Bone head decision: .NET 2.0 Not For Windows XP Pro SP1

[Scott M.]

You feel better now Jim? Breathe buddy, breathe. I only posted again as an
FYI since I am using ZA Pro. on XP Pro. machines that seem to be of the same
age as yours. Just thought others reading this shouldn't be put off of SP2
just because they may have a system that matches your specs.

I really suspect that the problems you've encounters are more likely related
to the other software that was already on the system (not the OS itself) at
the time of the upgrade attempt. It also doesn't sound like the age of the
PC or its specs. were the issue either.

IMHO

-Scott

 

[Gabriel Magaña]

Dude, just do the adult thing: Don't install the SP2 and deal with the
consequences of your actions and inactions... We all do it every day.

 

[Richard Grimes]

2) The real reason - right now, "Smart Client" applications developed
with VS 2005 will not be compatible with a significant number of XP
Pro systems. How do we deal with this issue and, more importantly,
why has Microsoft put us in this position in the first place?

Well, my contribution is that I have a XPSP2 machine but only room for
one version of VS so I uninstalled VS2003, installed VS2005 and then
installed ActiveSync 4.1. Oh dear. It was only after doing that when I
discovered that the compact framework 2.0 did not work on my (aging)
iPaq 3630, so I cannot develop compact framework apps for my iPaq. Oh
and ActiveSync 4.1 has removed some of the synchronization settings too


Luckily I have another machine with VS2003 on it but it just goes to
show that you should not be too hasty when upgrading your software.

Richard