I've been doing Windows Forms work in VS2005 but as part of my Windows app I needed to publish my Web Services site to a remote host. What a weird, new world in ASP.NET 2.0! So much for how wonderful XCOPY was as one of .NET 1.0's big selling points.
I needed to get my ASP.NET 2.0 Web Services application up and running on a server at HQ and for the life of me couldn't figure out how in the heck I was supposed to do it. Anyone who's ever done this may wonder why I'm wasting bandwidth on describing the process, but I know it will help other guys like myself who may be clueless when the time comes to load their first site on a remote host.
We "publish" sites in ASP.NET now. Forget a simple 1-to-1 copy or an ftp drag-n-drop. Fortunately there's a menu option in VS2005 and a simple dialog box to get the job done. My computer connected to the Internet is not running the .NET 2.0 Beta, and my .NET 2.0 Beta machine is not connected to the Internet, so I copy from my .NET 2.0 machine to a network share, then up to the host. Not an issue at all. Even better, it works!
