>>>>>>>I think you can install IIS on XP Pro but not on Home (unless you want to live dangerously):http://adamv.com/dev/articles/iis-on-xp-home/
>>>>>>
>>>>>>I'm virtually illiterate when it comes to the non-programming aspects of computers. Please bear with me.
>>>>>>
>>>>>>This is a work computer so I assume XP Pro. But how can I tell for sure? If I go to a DOS prompt and type VER I get
>>>>>>
>>>>>>Microsoft Windows XP [Version 5.1.2600]
>>>>>>
>>>>>>Any other way to find out if it's Home or Pro?
>>>>>
>>>>>If I look at Help/About Windows from, say, Windows Explorer it says Windows XP Professional in the banner at the top. I assume if it's XP Home you'll see similar.
>>>>>
>>>>>>I'm also reasonably sure that IIS is installed and running on this computer. But, again, anything that would help verify is appreciated.
>>>>>
>>>>>Control Panel/Add Remove Programs / Add/Remove Windows Components should list 'Internet Information Services' as a component If it ain't ticked it ain't installed (g). Just select it and carry on to install.
>>>>>
>>>>>>Assuming that IIS is running, can you give me some guidance (links, etc) on what needs to be done so that I can test the application from outside the Visual Studio environment?
>>>>>
>>>>>TBH I've never used IIS on an XP box so not sure what you'll come up against.
>>>>>Is the box using a fixed IP address? If not I'd suggest setting one up for IIS use.
>>>>
>>>>If you want other users to test the site, you really do want a fixed IP address. If you are using DHCP you can have whomever your domain administrator is set up a reserved IP for your machine on the DHCP server, or you can stop using DHCP and just set a fixed IP address.
>>>
>>>Hi,
>>>Was this meant for Rich. IAC if there's a DHCP server out there then just setting a fixed address on the box will be risky if that address is still in the DHCP pool......
>>
>>I copied it to Rich. In DHCP you can set a reserved IP for a particular network MAC address (network adapter). This effectively gives the network adapter a fixed address while still letting DHCP control all other network parameters (subnet, gateway, DNS, etc).
>
>I know that. But you said 'OR you can stop using.....' My point was that if you simply set a fixed IP address on the box without excluding that address from the DHCP pool you are likely to soon end up with duplicated IP addresses on the network.

Yes. If you do not use DHCP you use addresses outside any defined DHCP scope.

>
>>
>>>
>>>>
>>>>
>>>>>There's an option in .NET to publish the site (Build/Publish). I guess see how far you get and shout if you get stuck :-}
>>>>>
>>>>>>
>>>>>>Please bear in mind that I'm both an old person who doesn't learn very well anymore and that I'm brain-damaged from having been kicked in the head by my twin brother on the way down the birth canal. "Hurry up and get out of here, I'm next" (or words to that effect)
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Thanks a bunch..........Rich