Hello everyone,

I have an applciation that uses remoting. When the application is run
via a
local copy it works. When it is run via an HTTP address
RemotingConfiguration.Configure fails. Apparently this method can not
find
the configuration file even though other parts of my application can
use
ConfigurationSettings.AppSettings with no problem.


I have seen one other post on this topic but there really was no
solution.
Has anyone solved this problem?

This is my exception:
Additional information: .Config file
http://localhost/PFX/Client.exe.config
can not be read successfully due to exception System.ArgumentException:
URI
formats are not supported.


at System.IO.Path.GetFullPathInternal(String path)


at System.ConfigTreeParser.Parse(String fileName, String configPath)


at
System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ParseConfigF­i

le(String filename)


at
System.Runtime.Remoting.RemotingConfigHandler.LoadConfigurationFromXmlFile(­S

tring filename).

Hi,

The RemotingConfiguration.Configure method does not support URI formats for
the filename parameter, just like the exception states.

One workaround may be to use ClickOnce deployment instead.

I have an applciation that uses remoting. When the application is run
via a
local copy it works. When it is run via an HTTP address
RemotingConfiguration.Configure fails. Apparently this method can not
find
the configuration file even though other parts of my application can
use
ConfigurationSettings.AppSettings with no problem.


I have seen one other post on this topic but there really was no
solution.
Has anyone solved this problem?

This is my exception:
Additional information: .Config file
http://localhost/PFX/Client.exe.config
can not be read successfully due to exception System.ArgumentException:
URI
formats are not supported.


at System.IO.Path.GetFullPathInternal(String path)


at System.ConfigTreeParser.Parse(String fileName, String configPath)


at
System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ParseConfigF­i

le(String filename)


at
System.Runtime.Remoting.RemotingConfigHandler.LoadConfigurationFromXmlFile(­S

tring filename).

A god workaround is available at the followinf url:

http://bloggingabout.net/blogs/rick/archive/2006/01/16/10787.aspx.

bye bye

.NET, Clipboard, and metafiles
Strange problem
Garbage collection and async operations
VSNET: Problems adding VS 2005 extensions for .Net 3.0
VB vs. C# language challenge question