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

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

2010-05-26 Thread Matt Dargavel

When I was trying some WCF stuff out I found some scenarios where the
app.config settings didn't work, but using their code based
counter-parts did.  But Atsushi-san is the man in the know, so it looks
like the Credentials types will only work for some basic http
authentication.



Matt.

 

From: Greg Robinson [mailto:gregarobin...@gmail.com] 
Sent: 25 May 2010 9:10 PM
To: Matt Dargavel
Cc: mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] System.NotImplementedException: The
requestedfeature is not implemented.
atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfigur
ation

 

Matt,

 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. 

So are you stating Mono is not app.config file friendly? So it's
possible if we hard code these bits will run under Mono?




On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel m...@shout-telecoms.com
wrote:

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.5profile=2.0assembly
=System.ServiceModel

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

 

Regards,

 

Matt.

 

 

From: mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Greg
Robinson
Sent: 25 May 2010 7:09 PM
To: Stifu
Cc: mono-devel-list@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 st...@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 mig...@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.bergg...@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 gregarobin...@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

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

2010-05-26 Thread Greg Robinson

Atsushi Eno, are you on thew Mono development team? Great feedback, just
curious.

On Wed, May 26, 2010 at 5:19 AM, Matt Dargavel m...@shout-telecoms.comwrote:

When I was trying some WCF stuff out I found some scenarios where the
app.config settings didn’t work, but using their code based counter-parts
did. But Atsushi-san is the man in the know, so it looks like the
Credentials types will only work for some basic http authentication.

Matt.

*From:* Greg Robinson [mailto:gregarobin...@gmail.com]
*Sent:* 25 May 2010 9:10 PM
*To:* Matt Dargavel

*Cc:* mono-devel-list@lists.ximian.com
*Subject:* Re: [Mono-dev] System.NotImplementedException: The
requestedfeature is not implemented.
atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfiguration

Matt,

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.

So are you stating Mono is not app.config file friendly? So it's possible
if we hard code these bits will run under Mono?

On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel m...@shout-telecoms.com
wrote:

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.5profile=2.0assembly=System.ServiceModel

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

Regards,

Matt.

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

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 st...@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 mig...@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.bergg...@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 gregarobin...@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

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

2010-05-26 Thread Atsushi Eno

I'm working on it, yes ;)

On 2010/05/26 21:06, Greg Robinson wrote:
Atsushi Eno, are you on thew Mono development team? Great feedback,
just curious.

On Wed, May 26, 2010 at 5:19 AM, Matt Dargavel
m...@shout-telecoms.com mailto:m...@shout-telecoms.com wrote:

When I was trying some WCF stuff out I found some scenarios where
the app.config settings didn’t work, but using their code based
counter-parts did. But Atsushi-san is the man in the know, so it
looks like the Credentials types will only work for some basic
http authentication.

Matt.

*From:* Greg Robinson [mailto:gregarobin...@gmail.com
mailto:gregarobin...@gmail.com]
*Sent:* 25 May 2010 9:10 PM
*To:* Matt Dargavel

*Cc:* mono-devel-list@lists.ximian.com
mailto:mono-devel-list@lists.ximian.com
*Subject:* Re: [Mono-dev] System.NotImplementedException: The
requestedfeature is not implemented.

atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfiguration

Matt,

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.

So are you stating Mono is not app.config file friendly? So it's
possible if we hard code these bits will run under Mono?

On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel
m...@shout-telecoms.com mailto:m...@shout-telecoms.com wrote:

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.5profile=2.0assembly=System.ServiceModel

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

Regards,

Matt.

*From:* mono-devel-list-boun...@lists.ximian.com
mailto:mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list-boun...@lists.ximian.com
mailto:mono-devel-list-boun...@lists.ximian.com] *On Behalf Of
*Greg Robinson
*Sent:* 25 May 2010 7:09 PM
*To:* Stifu
*Cc:* mono-devel-list@lists.ximian.com
mailto:mono-devel-list@lists.ximian.com
*Subject:* Re: [Mono-dev] System.NotImplementedException: The
requestedfeature is not implemented.

atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfiguration

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 st...@free.fr
mailto:st...@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
mig...@novell.com mailto:mig...@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

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

2010-05-26 Thread Greg Robinson

Awesome, thanks! I found your blog today too, Good stuff.

I would love to be able to contribute; we simply do not have the resources
to offer right now.

On Wed, May 26, 2010 at 10:31 AM, Atsushi Eno
atsushi...@veritas-vos-liberabit.com wrote:

I'm working on it, yes ;)

On 2010/05/26 21:06, Greg Robinson wrote:
Atsushi Eno, are you on thew Mono development team? Great feedback,
just curious.

On Wed, May 26, 2010 at 5:19 AM, Matt Dargavel
m...@shout-telecoms.com mailto:m...@shout-telecoms.com wrote:

When I was trying some WCF stuff out I found some scenarios where
the app.config settings didn’t work, but using their code based
counter-parts did. But Atsushi-san is the man in the know, so it
looks like the Credentials types will only work for some basic
http authentication.

Matt.

*From:* Greg Robinson [mailto:gregarobin...@gmail.com
mailto:gregarobin...@gmail.com]
*Sent:* 25 May 2010 9:10 PM
*To:* Matt Dargavel

*Cc:* mono-devel-list@lists.ximian.com
mailto:mono-devel-list@lists.ximian.com
*Subject:* Re: [Mono-dev] System.NotImplementedException: The
requestedfeature is not implemented.

atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfiguration

Matt,

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.

So are you stating Mono is not app.config file friendly? So it's
possible if we hard code these bits will run under Mono?

On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel
m...@shout-telecoms.com mailto:m...@shout-telecoms.com wrote:

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.5profile=2.0assembly=System.ServiceModel

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

Regards,

Matt.

atSystem.ServiceModel.Configuration.WSHttpBindingElement.OnApplyConfiguration

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 st...@free.fr
mailto:st...@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
mig...@novell.com mailto:mig...@novell.com
wrote:

When I

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

2010-05-25 Thread Greg Robinson

Thanks, running MoMA is one of the first things I did when I started looking
at Mono. Much to my surprise it did not find any errors.

On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel m...@shout-telecoms.comwrote:

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.

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

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

Regards,

Matt.

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 st...@free.fr wrote:

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.

On Tue, May 25, 2010 at 12:45 PM, Miguel de Icaza mig...@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.bergg...@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 gregarobin...@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.OnApplyConfiguration
(System.ServiceModel.Channels.Binding binding) [0x0]
at

System.ServiceModel.Configuration.StandardBindingElement.ApplyConfiguration
(System.ServiceModel.Channels.Binding binding) [0x0]
at
System.ServiceModel.Configuration.ConfigUtil.CreateBinding
(System.String binding, System.String bindingConfiguration)
[0x0]
at System.ServiceModel.ChannelFactory.ApplyConfiguration
(System.String
endpointConfig) [0x0

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

2010-05-25 Thread Greg Robinson

Matt,

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.

So are you stating Mono is not app.config file friendly? So it's possible
if we hard code these bits will run under Mono?

On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel m...@shout-telecoms.comwrote:

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.

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

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

Regards,

Matt.

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 st...@free.fr wrote:

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.

On Tue, May 25, 2010 at 12:45 PM, Miguel de Icaza mig...@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.bergg...@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 gregarobin...@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.OnApplyConfiguration
(System.ServiceModel.Channels.Binding binding) [0x0]
at

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

2010-05-25 Thread Alan McGovern

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.

Depending on what it is that doesn't work, it's possible that it'd
only take you a couple of days could fix your issue. That'd be
significantly less time than porting to java. You'd have to way up the
pros and cons of rewriting in java. The biggest con is that you have
doubled your maintainance burden if you have the same code in two
languages.

Alan.

On Tue, May 25, 2010 at 9:09 PM, Greg Robinson gregarobin...@gmail.com wrote:
Matt,

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.

So are you stating Mono is not app.config file friendly? So it's possible
if we hard code these bits will run under Mono?

On Tue, May 25, 2010 at 3:40 PM, Matt Dargavel m...@shout-telecoms.com
wrote:

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.

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

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

Regards,

Matt.

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

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 st...@free.fr wrote:

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 mig...@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.bergg...@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 gregarobin...@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

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

2010-05-25 Thread Atsushi Eno

Hello,

First of all, MoMA is not anything you can think this app SHOULD run on
mono because MoMA reported nothing. It is rather to find out that MoMA
reported some items that should be implemented, so this app won't run.
It is because:

- It only checks exposed API. Anything that depends on internals won't
be reported.
- It does not support configuration elements, and WCF has a lot of them.
- There are many classes/members that itself is implemented but not
supported in
combined with others. Say, when we have FooServiceBehavior, BarBinding, and
ServiceHost and the combination of all of them doesn't work, they could
still be
reported as implemented as long as they are implemented (and it's too
silly to mark
everything NotImplemented or MonoTODO).

As for Credentials types, you should not basically expect them working
except for some
HTTP authentication stuff. For example IssuedToken will never work until
we finish lots of WS-* stuff.
It is easy to implement ClientCredentialsElement.CreateBehavior() right
now, but it does not make a lot of sense so far.

Atsushi Eno

On 2010/05/26 4:40, Matt Dargavel wrote:

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.5profile=2.0assembly=System.ServiceModel

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

Regards,

Matt.

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

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 st...@free.fr
mailto:st...@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 mig...@novell.com
mailto:mig...@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.bergg...@gmail.com mailto:oskar.bergg...@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 gregarobin...@gmail.com
mailto:gregarobin...@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

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

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

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

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

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

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

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

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

8 matches

Site Navigation

Mail list logo

Footer information