[Mono-dev] System.NotImplementedException: The requestedfeature is not implemented. atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfiguration

Matt Dargavel matt at shout-telecoms.com
Tue May 25 15:40:00 EDT 2010


Hi Greg,

 

Have you tried running MoMA (http://www.mono-project.com/MoMa) against
your application?  This should give you an idea of how much is missing
from Mono. 

 

With respect to WCF and the specific problem you saw, I've not used the
security stuff at all but it looks like most of the ClientCredentials
class is done so you might be able to configure the necessary
ClientCredentials in code rather than using .config files.  I don't
think the System.ServiceModel.Configuration namespace is as complete as
some of the other bits.  You can find information on the implementation
status at the links below.

 

http://go-mono.com/status/status.aspx?reference=3.5&profile=2.0&assembly
=System.ServiceModel

http://www.mono-project.com/WCF

 

                Regards,

 

                                Matt.

 

 

From: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Greg
Robinson
Sent: 25 May 2010 7:09 PM
To: Stifu
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-dev] System.NotImplementedException: The
requestedfeature is not implemented.
atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfigur
ation

 

Understood, and that was my first thought. Was just wondering if there
were alternative solutions. 

I am thinking of a Java/.NET split if you will where we keep what we can
that WILL run under Mono and port the rest to Java. That assumes we can
get the two to play nicely together. 

Is there a way to see if someone is already working on the bits in Mono
we need? 




On Tue, May 25, 2010 at 2:05 PM, Stifu <stifu at free.fr> wrote:


The obvious answer: contribute to Mono and help implement it. Or pay
someone
to do it.
That's what some companies do. If you can afford it, that's an option
(which
might turn out to be cheaper than rewriting everything in Java; that
said, I
have no idea how much work is needed here).



Greg Robinson wrote:
>
> I am new to Linux, new to Mono. I am really hoping we can use Mono for
our
> .NET application to Linux port/migration.
>
> The other option on the table is to totally re-write in Java.
>
> So what do folks usually do at this point; the point where they find
that
> something they need, our .NET Server application calling a WCF Service
> using
> System.ServiceModel bits, not implemented in Mono? It seems a shame to
> just
> give up and do a port to Java; is that my only solution though?
>
>
>
> On Tue, May 25, 2010 at 12:45 PM, Miguel de Icaza <miguel at novell.com>
> wrote:
>
>>
>> > When I go to:
>> >
>> > http://mono-project.com/DistroPackages/Ubuntu
>> >
>> > it tells me Mono comes installed by default. We are running Ubuntu
>> > 10.04.
>> >
>> > What do I need to do to upgrade to Mono 2.6 on Ubuntu 10.04?
>>
>> I am told that there are no 2.6 packages available for Ubuntu by the
>> Debian/Ubuntu community.
>>
>> The bad news is that you need to compile from source code;   The good
>> news is that this is a trivial process (as long as you use released
>> tarballs):
>>
>> http://www.mono-project.com/Parallel_Mono_Environments
>>
>> Migue.
>>
>> >
>> >
>> >
>> > On Mon, May 24, 2010 at 8:50 AM, Oskar Berggren
>> > <oskar.berggren at gmail.com> wrote:
>> >         2.2 is fairly old. Have you checked with 2.4 or 2.6?
>> >
>> >         Try searching for "moma" and "mono class library status".
>> >
>> >         /Oskar
>> >
>> >
>> >         2010/5/24 Greg Robinson <gregarobinson at gmail.com>:
>> >
>> >         >  I have been making good progress on moving our .NET
server
>> >         application over
>> >         > to Mono 2.2 running on Ubuntu 2.2.
>> >         >
>> >         >  Friday, I ported the WCF pieces over where all the
server
>> >         application does
>> >         > is make calls to a WCF service running on a windows
server
>> >         outside of our
>> >         > office.
>> >         >
>> >         >  I am getting the following, which suggests to me these
>> >         pieces of "client
>> >         > side" WCF are not implemented in Mono 2.2:
>> >         >
>> >         >  System.NotImplementedException: The requested feature is
>> >         not implemented.
>> >         >  at
>> >         >
>> >
>>
System.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfigurat
ion
>> >         > (System.ServiceModel.Channels.Binding binding) [0x00000]
>> >         >  at
>> >         >
>> >
>>
System.ServiceModel.Configuration.StandardBindingElement.ApplyConfigurat
ion
>> >         > (System.ServiceModel.Channels.Binding binding) [0x00000]
>> >         >  at
>> >         System.ServiceModel.Configuration.ConfigUtil.CreateBinding
>> >         > (System.String binding, System.String
bindingConfiguration)
>> >         [0x00000]
>> >         >  at System.ServiceModel.ChannelFactory.ApplyConfiguration
>> >         (System.String
>> >         > endpointConfig) [0x00000]
>> >         >  at System.ServiceModel.ChannelFactory.InitializeEndpoint
>> >         (System.String
>> >         > endpointConfigurationName,
>> >         System.ServiceModel.EndpointAddress
>> >         > remoteAddress) [0x00000]
>> >         >  at
>> >         >
>> >
>>
System.ServiceModel.ChannelFactory`1[OurCompanyName.Common.WebServiceRef
erence.OurCompanyNameWCFServiceProxy.IOurCompanyNameService]..ctor
>> >         > (System.String endpointConfigurationName,
>> >         > System.ServiceModel.EndpointAddress remoteAddress)
[0x00000]
>> >         >  at System.ServiceModel.ClientBase`1[TChannel].Initialize
>> >         > (System.ServiceModel.InstanceContext instance,
System.String
>> >         configName,
>> >         > System.ServiceModel.EndpointAddress remoteAddress)
[0x00000]
>> >         >  at System.ServiceModel.ClientBase`1[TChannel]..ctor
>> >         > (System.ServiceModel.InstanceContext instance,
System.String
>> >         configname)
>> >         > [0x00000]
>> >         >  at System.ServiceModel.ClientBase`1[TChannel]..ctor
>> >         > (System.ServiceModel.InstanceContext instance) [0x00000]
>> >         >  at System.ServiceModel.ClientBase`1[TChannel]..ctor ()
>> >         [0x00000]
>> >         >  at
>> >         >
>> >
>>
OurCompanyName.Common.WebServiceReference.OurCompanyNameWCFServiceProxy.
OurCompanyNameServiceClient..ctor
>> >         > () [0x00000]
>> >         >  at
>> >         >
>> >
>>
OurCompanyName.Common.WebServiceReference.OurCompanyNameServiceProxyAgen
t.CreateServiceProxy
>> >         > (Boolean useLimited) [0x00000]
>> >         >  at
>> >         >
>> >
>>
OurCompanyName.Common.WebServiceReference.OurCompanyNameServiceProxyAgen
t.CreateServiceProxy
>> >         > () [0x00000]
>> >         >  at
>> >         >
>> >
>>
OurCompanyName.Common.WebServiceReference.OurCompanyNameServiceProxyAgen
t.GetConfiguration
>> >         > (System.String loggerSAN) [0x00000]
>> >         >  at
>> >         >
>> >
>>
OurCompanyName.Common.WebServiceReference.OurCompanyNameServiceProxyAgen
t.GetConfiguration
>> >         > () [0x00000]
>> >         >  at OurCompanyNameWCFClientTest.Program.Main
>> >         (System.String[] args)
>> >         > [0x00000]
>> >         >
>> >         >
>> >         >
>> >         >
>> >         > Any idea if\when this will be implemented? is there a
>> >         workaround?
>> >         >
>> >         >
>> >         >
>> >         >
>> >         > Thanks
>> >         >
>> >         >
>> >         >
>> >         > --
>> >         > Greg
>> >         >
>> >         > My Blog: http://dotnetrocks.blogspot.com/
>> >         > My Techy Blog: http://weblogs.asp.net/grobinson/
>> >         > Amy's Blog: http://amyshome.blogspot.com/
>> >         > LinkedIn: http://www.linkedin.com/in/gregarobinson
>> >         >
>> >
>> >         > _______________________________________________
>> >         > Mono-devel-list mailing list
>> >         > Mono-devel-list at lists.ximian.com
>> >         > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>> >         >
>> >         >
>> >
>> >
>> >
>> > --
>> > Greg
>> >
>> > My Blog: http://dotnetrocks.blogspot.com/
>> > My Techy Blog: http://weblogs.asp.net/grobinson/
>> > Amy's Blog: http://amyshome.blogspot.com/
>> > LinkedIn: http://www.linkedin.com/in/gregarobinson
>> > My Company:
>> >
>>
http://www.richmondbizsense.com/2010/05/04/health-monitoring-company-is-
well-aware-of-richmond%E2%80%99s-benefits/
>> > _______________________________________________
>> > Mono-devel-list mailing list
>> > Mono-devel-list at lists.ximian.com
>> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
>>
>
>
> --
> Greg
>
> My Blog: http://dotnetrocks.blogspot.com/
> My Techy Blog: http://weblogs.asp.net/grobinson/
> Amy's Blog: http://amyshome.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/gregarobinson
> My Company:
>
http://www.richmondbizsense.com/2010/05/04/health-monitoring-company-is-
well-aware-of-richmond%E2%80%99s-benefits/
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>

--

View this message in context:
http://mono.1490590.n4.nabble.com/System-NotImplementedException-The-req
uested-feature-is-not-implemented-at-System-ServiceModel-Confin-tp222851
5p2230442.html
Sent from the Mono - Dev mailing list archive at Nabble.com.

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list




-- 
Greg 

My Blog: http://dotnetrocks.blogspot.com/
My Techy Blog: http://weblogs.asp.net/grobinson/
Amy's Blog: http://amyshome.blogspot.com/
LinkedIn: http://www.linkedin.com/in/gregarobinson
My Company:
http://www.richmondbizsense.com/2010/05/04/health-monitoring-company-is-
well-aware-of-richmond%E2%80%99s-benefits/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20100525/383b5f8e/attachment-0001.html 


More information about the Mono-devel-list mailing list