-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hi
I think even if we will not need interoperability between applications, and even we do not communicate with web services, it is easier to serialize using SoapFormatter than XmlSerializer because SOAP will serialize the private members by default, while XmlSerializer will work on public properties…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hello.
I am working on a distributed application which has two components. One is written in standard C++ (not managed C++) and the other one is written in C#. Both are communicating via a message bus.
I have a situation in which I need to pass objects from C++ to C# application and for this I need…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
My application is written in C# and I am a newbie to C#. I am facing with a problem during serialization. The problem is as follows.
There are many classes in my project and when serialization is called on one of the main class object it serializes itself and during this process many of the member…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I have a problem when serializing a Dictionary<string,Person> to IsolatedStorageSettings. I'm doing the following:
public Dictionary<string, Person> Names = new Dictionary<string, Person>();
if (!IsolatedStorageSettings.ApplicationSettings.Contains("Names"))
{
…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hi All,
Consider this piece of code:
private Queue Date=new Queue();
//other declarations
public DateTime _Date {
get { return (DateTime)Date.Peek();}
set { Date.Enqueue(value); }
}
//other properties and stuff....
public void UpdatePosition(...)
{
//other code
…
>>> More
