Re: Linux, Mono and Windows Services, MSMQ and WCF

"Greg" <[email protected]>
Newsgroups gmane.comp.windows.off-topic
Message-ID <[email protected]>
Using the Synaptic Package manager I was able to apply an upgrade for System.Messaging and now that warning is gone and it shows up in the GAC on the Ubuntu box.

System.ServiceModel does not show up in the Package list or the GAC though so I am trying to figure out how to get this one. 



--- In [email protected], "Greg" <gregarobinson@...> wrote:
>
> I copied the .sln over  to the Unbuntu box, did a build with MonoDevelop, ran mono again pointing to the exe built by MonoDevelop...same result...warnings on System.ServiceModel and System.Messaging. And then I ultimately see:
> 
> =================================================================
> Got a SIGSEGV while executing native code. This usually indicates
> a fatal error in the mono runtime or one of the native libraries 
> used by your application.
> =================================================================
> 
> Aborted
> 
> So I am missing something here. Everything I am readying states ServiceModel and Messaging is supported in Mono. 
> 
> 
> 
> --- In [email protected], "Greg" <gregarobinson@> wrote:
> >
> > After doing a build in VS 2008 on a windows box, I copied the exe and dll dependencies over to the Ubuntu box. I opened a terminal and used mono to run the exe. 
> > 
> > First warning:
> > 
> > WARNING **: Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.
> > 
> > I got the same warning for System.Messaging. 
> > 
> > All of my Googling suggest WCF and MSMQ Messaging are supported in Mono so what am I missing here?
> > 
> > Stuart, I will do as you suggest and do a build with MonoDevelop. 
> > 
> > 
> > 
> > --- In [email protected], "Stuart Laughlin (Lists)" <lists@> wrote:
> > >
> > > On Thu, May 6, 2010 at 7:56 AM, Greg <gregarobinson@> wrote:
> > > >
> > > > I finally got a copy of the source code from the outsource vendor yesterday and was able to get a clean build. I ran MoMA on the build, expecting to see all kinds of warnings and errors. Instead I saw:
> > > >
> > > > "MoMA was unable to find any potential issues in this application."
> > > >
> > > > My first response: Woo Hoo!
> > > >
> > > 
> > > Hear that? That's the sound of Open Source winning.
> > > 
> > > > My next response; no way this is possible.
> > > >
> > > 
> > > Hear that? That's the sound of a developer made cynical by years of
> > > Microsoft servitude.
> > > 
> > > > So now I plan to figure out how to actually port the .NEY source code over to the Ubuntu box and figure out how to run it under Mono.
> > > >
> > > 
> > > Basically you'll want to open the solution with MonoDevelop and build
> > > it. Then copy the resultant executable over to the Ubuntu machine and
> > > execute it.
> > > 
> > > If that works straight away then you'll want to send an email to your
> > > boss to let him know that it's going to be a lot of hard work, but
> > > that hopefully you ought to be able to get this app ported by the end
> > > of the month. Next, send a gushing email to
> > > mono-devel-list@ offering to buy beer if/when any of
> > > them turn up in your city. Finally, in your newly-found free time,
> > > take long strolls in the park, think things over, and enjoy life
> > > again.
> > > 
> > > (What would you guys do without me on this forum??)
> > > 
> > > 
> > > --Stuart
> > >
> >
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.