[Mono-dev] After an initial investigation of porting WCF to mono, this is what I've found so far

[Miguel de Icaza]

My quick take, as I am about to bird a plane:

- ifdef out transactions
- SR missing stuff is pretty common, we have been stubbing these out, check
the recent commits to mono/mcs/class/System to get an idea
- use reference source for the landing spot.

On Tuesday, December 16, 2014, Bernie Schoch <bpschoch at gmail.com> wrote:

> References to XAML configuration #if XAML out
> References to COM  #if COM out
>
> There are references to Transaction processing in Microsoft namespace is
> this something we need to support or #if it out?
>
> There is a ton of stuff missing from System.IdentityModel:
> This is where the majority of the errors lie. 100+ items;  Should I just
> back port this into existing Mono code or use reference source versions?  I
> ask because I don't have much history on mono project and don't really know
> status of System.IdentiyModel.
>
> What is the strategy to deal with SR messages?  Right now I've just
> created an internal SR and InternalsSR class
>
> Thanks,
> Bernie Schoch
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20141216/f49763c2/attachment.html>