It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
In our project, we are having xsd schema files, we are auto generating c# classes for xsd and using them. Each time, if we need to do modification, we are asked to do it in xsd file and which later generated into c# code.
My question is, why we need xsd in first place, why can't we directly have the serializable c# classes created.
I'm assuming the changes to the classes are a result of changes to some XML data structure that the app supports. With that assumption, here are a couple of reasons to keep the XSDs in sync:
If you ever re-generated the class files from the XSDs all changes to the classes would be lost
The XSDs could be used to validate any XML document that could be (de)serialized using those classes.
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
The SerializableAttribute class is explained on this link. In the start it is written:
Indicates that a class can be serialized
Can anybody expalin what this means (the bold part). I am not clear about it.
Serializing an object (an instance of a class) means turning it into something that can be written on a file or broadcasted over the network, such as an XML file (Xml serialization) or a Byte array (binary serialization).
This needs to be a two way operation, so you must be able to "Deserialize" the object.
In order to be serializeble an object must contains just serializable fields/property or fields marked as not serialized. For example a Sql connection is not serialized (it would make no sense deserializing it somewhere else...)
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I'm looking for full C# standard interfaces list. I'm almost sure that such topic was posted somewhere on MSDN, but I can't find it. Does anyone has a reference?
im sorry but such doc does not exist...
See, msdn documentation is organized by "namespaces", so... you can see that such document would not fit anywhere... by the way, why would you want that?!? if you compile the documents of each interface in the basics dll (system, text, system.data, linq, etc...) you would have a quite large document that would cause more confusion than "de-confusion", since in diferent namespaces interfaces may have the same name...
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I'm in my first year studying .Net and came to the chapter, "An Introduction to the System.IO classes"
I'm just curious to know what the .IO stands for. I do understand that this is learning about how to use Directories, Files and paths.
IO itself stands for Input/Output.
This is the entire System.IO namespace: http://msdn.microsoft.com/en-us/library/system.io.aspx
You're probably going to cover directories, files, and streams.
'IO' is the standard acronym for Input/Output. The System.IO namespace contains all the classes that deal with input/outputs like reading/writing files.
IO stands for Input and Output. Basically System.IO contains methods for reading and writing files as well as using Streams like you have said already.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I am facing problem with "Access one xml file from 2 different applications at same time".
But it shows error code is "access denied, because another process using the file".
I applied all lock methods, but no use (same error).
Setting the correct FileShare enumeration value when instantiating the underlying FileStream allows you to control this.
Ref.: http://msdn.microsoft.com/en-us/library/system.io.fileshare.aspx
Even if it would be possible for two applications to write to the same file at the same time, the file would be corrupted. I recommend you to use a database instead.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 12 years ago.
why use of namespace and use keyword and declaration of namespace
Namespaces are used for organizing the types in the code in a logical manner. Imagine the Base Class Library itself, with its many thousands of types, without namespaces. It is simply a tool for making code more structured, much like the ability to create directories in the file system helps you organize your files.
Now, since the full name of a type is the namespace and type name, these may become fairly long. In order to make this easier on you as a developer, you can tell the compiler that you are using types from certain namespaces in a code file with using (or Imports in VB.NET) directives, and then you don't need to use the full name in that file. It simply tells the compiler where to go look for any type that is not entered using the full name in the code.