[Mono-dev] Web service client - SendOrPostCallback could not be loaded

Atsushi Eno atsushi at ximian.com
Tue Jul 25 12:12:26 EDT 2006


Hi,

>> OK, try the following steps:
>>
>> - change the error message in OpenExeConfigurationInternal()
>>    in the first "throw ArgumentException" in ConfigurationManager.cs
>>    in mcs/class/System.Configuration/System.Configuration, to
>>    whatever you like.
>> - Rebuild all, and install
>> - Run your application and make sure that your change is reflected.
>>
>> Your stacktrace is indeed weird to me. There is a line
>>
>> >
>>
>> System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection 
>>
>> (System.String configKey) [0x00000]
>>
>> which indicates that it invokes a method in an *interface* without
>> any implementation class information. It makes me impossible to
>> precisely keep track of the actual code execution (I haven't
>> ever experienced such a situation).
>>
>> There is nothing other than ClientConfigurationSystem that invokes
>> OpenExeConfigurationInternal(), thus I can only guess that the
>> invoker is ClientConfigurationSystem, which uses GetCallingAssembly()
>> which you said does not return null.
>>
>> Atsushi Eno
>>
> 
> Hi,
> 
> I changed error message to another one, and now I get that error I wrote. I
> tried reading ConfugurationManager.AppSettings and it definitely seems that
> doing that causes that error.

I noticed that ClientConfigurationSystem still uses GetEntryAssembly()
which however looks correct. What does that method return in your code?

If GetEntryAssembly() returns null and you don't have a configuration
file, then maybe we should just remove that ArgumentException
from OpenExeConfigurationInternal(). I'm far from sure if it is
the right thing (as I'm not the one who wrote the original code),
especially it will bring a risk that a corresponding config file
could be ignored at any time in embedded scenarios, but I have no
other ideas to move this bug away.

Atsushi Eno



More information about the Mono-devel-list mailing list