TL;DR; Explains how to transmit a .NET assembly over HTTP in a WCF service call, focusing on serialisation and deserialisation without using byte streams.
I want to send a .NET assembly as either an System.Reflection.Assembly or as a string over the wire through a Windows Communication Foundation web service. It seems that the class System.Reflection.Assembly can serialize, but is unable to deserialize at the other end. How can this be achieved without sending as a straem of Byte.
I would prefer:
<OperationContract(IsOneWay:=True)> _
Sub AddEventHandlerAssembly(ByVal Assembly As System.Reflection.Assembly)
Or:
<OperationContract(IsOneWay:=True)> _
Sub AddEventHandlerAssembly(ByVal Assembly As String)
But not:
<OperationContract(IsOneWay:=True)> _
Sub AddEventHandlerAssembly(ByVal Assembly As Byte())
I have tralled the web for a while now, trying to find a solution. I have even decompiled the Assembly class and the problem is that it implements System.Runtime.Serialization.ISerializable but does not provide the constructor for the deserialize.
Does anyone have a solution for this?
Technorati Tags: .NET
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Sage
Kongsberg Maritime
Lockheed Martin
ProgramUtvikling
Milliman
Boxit Document Solutions
Brandes Investment Partners L.P.
Graham & Brown
Big Data for Humans
MacDonald Humfrey (Automation) Ltd.
Jack Links
Workday
Qualco
Xceptor - Process and Data Automation
Epic Games
DFDS
Boeing
Trayport
Royal Air Force
New Hampshire Supreme Court
Ghana Police Service
Washington Department of Transport
Washington Department of Enterprise Services
Department of Work and Pensions (UK)
Bistech
Genus Breeding Ltd
Schlumberger
Illumina
Microsoft
Lockheed Martin