Here[^] it is. Serialization may take some getting-used-to, but it's more versatile than dumping memory.
I'd recommend building it in two separate steps; First, create a small console-app to serialize a random object. Once that works, you should be able to switch between Xml-serialization and binary with ease.
Second part would be to store that "information" in a database. That will work the same way for any information; if you get stuck once you're there, simply come back and we'll look at it again
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
Okay so go ahead and do that. Did you maybe have some sort of a question that you wanted to ask?
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
Hi All Developers I have A Problem :
How I can Change Opacity Of a Control IN Windows Application C#.net .. I Know How I can Change Form Opacity But How we can Change Control Opacity Like A button.
Problem:First C# 2008 app did not find the location of where the executable was located for the second program.
When my company deployed my C# 2008 and 2010 applications to a test server, one of the applications did not use the configuation set for where the executable was suppose to be at? Our network administrator found where the first program thinks the second executable was at.
Thus I am trying to determine why one of the programs did not take the setting it was given.
The location the first program was looking at was at:
c:/server name/share directory name/test/app1.exe.
The only way I can think this location was picked since on a few tries, the location of the executable as was at:
//server name/share directory name/test/app1.exe
Is this accidently? Should I have the network administrator reboot the test server to see if the c:/server name/share directory name/test/app1.exe. location request goes away?