Installation of Visual studio.net on xp home

[Guest]

Hi,
I'm trying to install visual studio.net on my home machine (running xp home)
to try and get some work done at home. But I am road blocked when I try and
install the pre-requesites (as requested by the initial vis studio
installation form). I get the error "procedure entry point
setupapi.CM_Disable_DevNode not located..."
This is a new machine with all the latest patches on it but my msdn
membership disks are a few months old. I will probably use this machine for
email as well as development so the use of the msdn included operating
systems appears inappropriate (i.e license allows VisStudio use on multiple
machines but msdn included op systems are for development only) I am supposed
to be able to run VisStudio on XPHome (albeit with restrictions). All
ideas/suggestions/advice greatfully received
Thanks Bill
(p.s. installation 8 months ago on win 2000 was forgettably uneventful!)

 

[Guest]

I don't know if I'll get an answer to this, but for what its worth... I've
now installed VisStudio 2005 beta 2 without a hitch on XP home, BUT I still
get road blocked with the 2003.net install. I was hoping that the DVD install
of 2005 would have fixed up anything needed for 2003 CDrom install (you never
know your luck). The problem is still with the missing entry point (see
below). Although 2005 beta 2 is up and running I do need to install 2003
still. Hi Ho Hum

All thoughts greatfully received
Regards
Bill

 

[Guest]

This is a bit like taliking to myself but just in case someone else gets this
problem....I borrowed another msdn members DVD of VisStudio.net 2003 and this
DVD version installed without a hitch. So... I must assume that there is a
problem with the CDROM version installing on XP Home. I know few msdn members
will be using XP Home so possibly installing VisStudio.net from the msdn
CDROM set onto XP Home has never been tested. But it is something that MS
might like to look at. Finally, just to clarify matters, the attempted
install from cdrom did not appear to fail due to bad media but an
incompatability on a procedure call.