Vista - BinaryFormatter problem

I faced some problem with BinaryFormatter.
Deserialize method doesn't work when I run it from PowerShell Cmdlet, while
it works normally in test application.
I have found only one solution - place dll in GAC, is it correct way?

Here is example. It fails on deserialize method telling that it cannot load
assembly.

[Serializable]
public class Test
{
private int num;
public int Num
{
get { return num; }
set { num = value; }
}
}

ProcessRecord method of cmdlet.
protected override void ProcessRecord()
{
BinaryFormatter sr = new BinaryFormatter();
MemoryStream st = new MemoryStream();
Test t = new Test();
t.Num = 100;
sr.Serialize(st, t);
st.Position = 0;
Test t2 = (Test)sr.Deserialize(st);
st.Close();
this.WriteObject(t2);
}

Presumably the dll you want to use contains the .NET assembly. You could put
it in the GAC then use

$null=
[System.Reflection.Assembly]::LoadWithPartialName(partial_name_of_assembly)
or load it direct
$null = [System.Reflection.Assembly]::LoadFrom(full_path_to_assembly)
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Andrew" wrote:

> I faced some problem with BinaryFormatter.
> Deserialize method doesn't work when I run it from PowerShell Cmdlet, while
> it works normally in test application.
> I have found only one solution - place dll in GAC, is it correct way?
>
> Here is example. It fails on deserialize method telling that it cannot load
> assembly.
>
> [Serializable]
> public class Test
> {
> private int num;
> public int Num
> {
> get { return num; }
> set { num = value; }
> }
> }
>
> ProcessRecord method of cmdlet.
> protected override void ProcessRecord()
> {
> BinaryFormatter sr = new BinaryFormatter();
> MemoryStream st = new MemoryStream();
> Test t = new Test();
> t.Num = 100;
> sr.Serialize(st, t);
> st.Position = 0;
> Test t2 = (Test)sr.Deserialize(st);
> st.Close();
> this.WriteObject(t2);
> }

Sorry - misread your post.

If you are creating a cmdlet - you need to put a reference to the assembly
in your project and a using statement in the code
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Andrew" wrote:

> I faced some problem with BinaryFormatter.
> Deserialize method doesn't work when I run it from PowerShell Cmdlet, while
> it works normally in test application.
> I have found only one solution - place dll in GAC, is it correct way?
>
> Here is example. It fails on deserialize method telling that it cannot load
> assembly.
>
> [Serializable]
> public class Test
> {
> private int num;
> public int Num
> {
> get { return num; }
> set { num = value; }
> }
> }
>
> ProcessRecord method of cmdlet.
> protected override void ProcessRecord()
> {
> BinaryFormatter sr = new BinaryFormatter();
> MemoryStream st = new MemoryStream();
> Test t = new Test();
> t.Num = 100;
> sr.Serialize(st, t);
> st.Position = 0;
> Test t2 = (Test)sr.Deserialize(st);
> st.Close();
> this.WriteObject(t2);
> }

There is only one assembly (Cmdlet) containing class Test (that must be
serialized and deserialized) and Cmdlet.
Exception is like this:

Unable to find assembly xxx'.
at
System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at
System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String
objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[]
typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32
objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at
System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
at
System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryHeaderEnum binaryHeaderEnum)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at
System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler
handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain,
IMethodCallMessage methodCallMessage)
at
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream
serializationStream, HeaderHandler handler, Boolean fCheck, Boolean
isCrossAppDomain, IMethodCallMessage methodCallMessage)
at myCmdLets.test.ProcessRecord()

"RichS" wrote:

> Sorry - misread your post.
>
> If you are creating a cmdlet - you need to put a reference to the assembly
> in your project and a using statement in the code
> --
> Richard Siddaway
> Please note that all scripts are supplied "as is" and with no warranty
> Blog: http://richardsiddaway.spaces.live.com/
> PowerShell User Group: http://www.get-psuguk.org.uk
>
>
> "Andrew" wrote:
>
> > I faced some problem with BinaryFormatter.
> > Deserialize method doesn't work when I run it from PowerShell Cmdlet, while
> > it works normally in test application.
> > I have found only one solution - place dll in GAC, is it correct way?
> >
> > Here is example. It fails on deserialize method telling that it cannot load
> > assembly.
> >
> > [Serializable]
> > public class Test
> > {
> > private int num;
> > public int Num
> > {
> > get { return num; }
> > set { num = value; }
> > }
> > }
> >
> > ProcessRecord method of cmdlet.
> > protected override void ProcessRecord()
> > {
> > BinaryFormatter sr = new BinaryFormatter();
> > MemoryStream st = new MemoryStream();
> > Test t = new Test();
> > t.Num = 100;
> > sr.Serialize(st, t);
> > st.Position = 0;
> > Test t2 = (Test)sr.Deserialize(st);
> > st.Close();
> > this.WriteObject(t2);
> > }