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

[Atsushi Eno]

Janne Rantala wrote:
> 2006/7/3, Atsushi Eno <atsushi at ximian.com>:
>>
>> Hello,
>>
>> > Another error about web services is this which I usually get when 
>> trying
>> to
>> > initialize client:
>> >
>> > Unhandled Exception: System.TypeInitializationException : An exception
>> was
>> > thrown
>> > by the type initializer for System.Xml.Serialization.XmlSerializer --->
>> > System.
>> > ArgumentException: exePath must be specified when not running inside a
>> > stand
>> > alo
>> > ne exe.
>> > in <0x00253>
>> > System.Configuration.ConfigurationManager:OpenExeConfigurationInter
>> > nal (ConfigurationUserLevel userLevel,
>> > System.Reflection.Assemblycalling_assemb
>> > ly, System.String exePath)
>> > in <0x0003b>
>> > System.Configuration.ClientConfigurationSystem:System.Configuration
>> > .Internal.IInternalConfigSystem.GetSection (System.String configKey)
>> > in <0x0001f> System.Configuration.ConfigurationManager:GetSection (
>> > System.String
>> > sectionName)
>> > in <0x0001f> System.Configuration.DefaultConfig:GetConfig
>> > (System.Stringsection
>> > Name)
>> > in <0x00017> System.Configuration.ConfigurationSettings:GetConfig (
>> > System.String
>> > sectionName)
>> > in <0x001cd> System.Xml.Serialization.XmlSerializer:.cctor ()--- End of
>> > inner ex
>> > ception stack trace ---
>>
>> Bug #78750 reminded me that ConfigurationManager uses internal
>> ClientConfigurationSystem which is based on Assembly.GetEntryAssembly().
>> The exception above happens when there is no entry assembly information,
>> which is also likely to happen around web services.
>>
>> If you use xsp2 and still get this error, please file a bug on
>> bugzilla.
>>
>> Atsushi Eno
>>
> 
> But my assembly tries to access web service, it is not web service itself.
> Does it still need xsp2 to work?

Oops, then no ;-) Just noticed that you ran the application from
embedded environment, which means GetEntryAssembly() will return null.
My guess is that System.Configuration classes should also work under
such an environment, it is likely to be a bug there. Let me dig into
this (second) problem.

Atsushi Eno