First things first: I hate that ASP.NET forces you to put all assemblies in a bin subdirectory. To make matters worse, there is no way to change the private probing path in an ASP.NET application. Couple this with the directory structure that VS.NET creates for projects (e.g. MyProject\bin\Debug), and you end up with the fact that you can't simply create a virtual directory that points to the location of your assemblies that were generated by doing a build in VS.NET

I couldn't find anything to easily deploy my project with remote objects and a web.config to an ASP.NET virtual directory. I did see some documentation about Visual WebDeveloper, but I don't have that installed here. Perhaps I didn't install it when I installed VS.NET. Regardless, I really don't want to go back to install this since I'm not creating aspx pages and the like, but I do want to host my remoting objects in IIS (more details on this in a later post).

What I ended up doing was using the post-build Build Event to create events to copy the files over to the IIS directory, e.g.:

copy $(TargetDir)\*.* \inetpub\wwwroot\tipnet\bin
copy $(ProjectDir)\web.config \inetpub\wwwroot\tipnet

At least this way, my IIS files stay in sync with what I just compiled. It might not be the most beautiful thing ever, but it works.