unable to create a Direct3D10.BlendState from a BlendStateDescription

[GoogleCodeExporter]

When I try to create a BlendState with settings from a 
BlendStateDescription variable, the new BlendState's description does not 
reflect the description I have provided. None of the settings of the 
BlendStateDescription flow through to the BlendState.Description

I'm currently on June 2008 release, I am unable to update to the latest 
SDK at present, because I am using binary serialization for my project and 
I get the "SlimDX.Vector4 cannot be converted to SlimDX.Vector4" when 
serializing in my objects from file. I do not want to update to the latest 
SDK if I can help it.

Is the BlendState issue I have encountered a fixed issue?

Original issue reported on code.google.com by moviekni...@gmail.com on 23 Dec 2008 at 5:26

[GoogleCodeExporter]

Yes. But the vector serialization issue is new to me. Can you open a new ticket 
for that bug with a more precise 
repro case?

Original comment by josh.petrie on 24 Dec 2008 at 12:45

• Changed state: Invalid

[GoogleCodeExporter]

The Vector serialization issue is (I've since found out) a known bug in .Net's 
binary 
serialization, which by the sounds of it has been there since Day 1. There is 
an 
AssemblyFormat flag that supposedly disables the binary compatibility checks 
but it 
simply doesn't work. Here is how one is supposedly meant to use it:

        Dim fs As New System.IO.FileStream(filename, IO.FileMode.Open)
        Dim b As BinaryFormatter = New BinaryFormatter
        b.AssemblyFormat = FormatterAssemblyStyle.Simple
        o = CType(b.Deserialize(fs), t) ' deserialize object to variable o

I think I'll have to move away from binary serializing for storing my objects 
and 
have my own internal file format that I can control (and fix if necessary), 
then I 
can update to the latest version and get the fix for the BlendState issue.

Thanks, and Merry Christmas!

Original comment by moviekni...@gmail.com on 24 Dec 2008 at 10:16