[Mono-list] Why Mono developers merged System.ServiceModel.Activation.dll to System.ServiceModel.dll?
mauzik at centrum.cz
Sun Sep 8 07:43:51 UTC 2013
I have ported .NET application to Mono. One of our subprojects use under
.NET System.ServiceModel.Activation.dll assembly, but Mono has implement
functionality in different assembly (System.ServiceModel.dll). No problem I
added reference for System.ServiceModel.dll and application runs.
Complications occurs in third party libraries which use
System.ServiceModel.Activation.dll. I edited it and changed code for Mono
support. My question is why? Why Mono team decided for merge assembly? In my
opinion this is road to hell. Maybe there are serious reasons for this
Thank for your response,
have a nice day.
View this message in context: http://mono.1490590.n4.nabble.com/Why-Mono-developers-merged-System-ServiceModel-Activation-dll-to-System-ServiceModel-dll-tp4660819.html
Sent from the Mono - General mailing list archive at Nabble.com.
More information about the Mono-list