This post originated from an RSS feed registered with .NET Buzz by Robert Hurlbut. Original Post: ASP.NET and RemotingConfiguration.Configure() Feed Title: Robert Hurlbut's .Net Blog Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/rhurlbut/Rss.aspx Feed Description: Development with .Net, Rotor, Distributed Architectures, Security, Extreme Programming, and Databases Latest .NET Buzz Posts Latest .NET Buzz Posts by Robert Hurlbut Latest Posts From Robert Hurlbut's .Net Blog

Ingo mentions a solution I found this week for setting up ASP.NET as a .Net Remoting client (it is actually a bug fix):

If you use ASP.NET as a Remoting client, you should not use this code in your app.config:

protected void Application_Start(Object sender, EventArgs e)
{
   RemotingConfiguration.Configure(Server.MapPath("client.exe.config"));
}

Using Server.MapPath(), some requests might fail if the application is recycled and the first request is not for a file in the application's root directory but in a subdirectory (i.e. "http://yourhost/somedir/default.aspx" instead of "http://yourhost/default.aspx". Robert suggested to use the following (and of course, he's totally right):

protected void Application_Start(Object sender, EventArgs e)
{
   RemotingConfiguration.Configure(Request.PhysicalApplicationPath 

        + "client.exe.config");
}