Joel:
It depends on what you are testing locally? If you need to test IIS as if it
were production, you would be best with Windows 2003 as OS, as that is the
same as your environ. If you have a QA test environ, Windows XP with IIS
will work. If you also have an "integration/development" environment, then
using the file based web option is fine, as you can test IIS in the
integration environment.
For ease of use, the file based web is easiest, as everyone can easily set
up their machine. Under VS 2005, it is far easier to use IIS in a
distributed group, as the solution file contains particulars, not the
project file, so team development is very possible, esp. if everyone checks
out source to the same physical location on their box.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************************************************
Think outside the box!
*************************************************
[quoted text, click to view] "Joel Barsotti" <joelbarsotti@hotmail.com> wrote in message
news:utzxxXVFGHA.2444@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> I'm trying to determine the best way to setup vs2005 and my network for
> web development.
>
> It seems the most integrated method for development would be to use the
> local IIS. This would be alright in my single developer enviroment, but it
> seems less than ideal for a multi developer enviroment. But given that I
> really want to have use the remoteOnly option for error messages I feel
> almost locked into this option.
>
> Which brings me to a second issue with using local IIS, only one website
> supported under XP. Should I upgrade my OS to server 2003?
>
> I guess I'm just trying to figure it out. I was using remote website
> under vs2003 but using frontpage extensions always seemed clunky and it's
> much worse under 2005 so I'm really trying to streamline the integration
> between my development site and my development tools.
>
> Thanks,
> Joel
>
