I have XPPro on my desktop with VS.Net and since I'm developing ASP.Net apps
I need more IIS than XPPro gives me, so Win2003 had to be bought, along with
a server to run it on.

Now the obvious thing would be to keep development files on the server,
since that's where the webs are yes?

So why it is so complicated?

I start a new web app in VS.Net and point to
http://newserver/webapplication1 instead of http://localhost/webapplication1
then jump through dozens of hoops before it will actually accept that that's
where I want stuff to be - setting up the web app in IIS6 on the server and
mapping folders, shares and virtual directories until VS.Net is happy to
proceed.

I set about building some basic pages (just to convince myself that all that
effort was worth it), but when I come to start the app I find debugging
isn't configured! DOH!

So I try to start it without debugging (I'm now so desperate for some
positive feedback - I just want to see "hello world" in a browser) and get
a"resource not found" error. DOH!

So I look in the virtual folder - EMPTY!

VS.Net has stored my files on my C drive and the web server has never seen
them!

Now this may sound like sacrilege, but DreamWeaver has a quite intuitive way
of specifying settings for the local folder, and a set for a test server,
and another for a production server, and handles synchronisation in a very
slick way. (Loads of other stuff DWMX does is shyte, especially when it
comes to ASP.Net)

I could set up a new web folder on the web server and point IIS at it, and
set up a project folder on my file server and then set up a new site in
DreamWeaver using these folders in a few minutes. VS.Net seems to make
things overly complicated.

Or is there an easy way I just haven't seen?

Brian Lowe
---------@