There’s a handy little method File.WriteAllLines — no need to open a StreamWriter yourself: In .net 4: File.WriteAllLines(speichern, ausgabeListe); In .net 3.5: File.WriteAllLines(speichern, ausgabeListe.ToArray()); Likewise, you could replace your reading logic with File.ReadAllLines, which returns an array of strings (use ToList() on that if you want a List<string>). So, in fact, your complete code could … Read more
Executive summary MyList.Free is sufficient. Detailed answer The TList<T> generic container owns its contents. When you free the container, the contents are also disposed of. Now, if T is an unmanaged reference, either a pointer or a class, then the list owns the reference. It does not own that which the reference refers to. So … Read more
public interface IPrimitive { } public interface IPrimitive<T> : IPrimitive { T Value { get; } } public class Star : IPrimitive<T> //must declare T here { } Then you should be able to have List<IPrimitive> primitives = new List<IPrimitive>; primitives.Add(new Star()); // Assuming Star implements IPrimitive primitives.Add(new Sun()); // Assuming Sun implements IPrimitive
The following works and as per StaxMan’s advice no longer uses the deprecated static collectionType() method. public class SoApp { /** * @param args * @throws Exception */ public static void main(String[] args) throws Exception { System.out.println(“Hello World!”); String s = “[{\”user\”:\”TestCity\”,\”role\”:\”TestCountry\”},{\”user\”:\”TestCity\”,\”role\”:\”TestCountry\”}]”; StringReader sr = new StringReader(“{\”user\”:\”TestCity\”,\”role\”:\”TestCountry\”}”); //UserRole user = mapper.readValue(sr, UserRole.class); mapJsonToObjectList(s,UserRole.class); } protected … Read more
One big difference is that List<Employee> can be expanded (you can call Add on it) or contracted (you can call Remove on it) whereas Employee[] is fixed in size. Thus, Employee[] is tougher to work with unless the need calls for it.
Queue has a constructor that takes in an ICollection. You can pass your list into the queue to initialize it with the same elements: var queue = new Queue<T>(list); // where ‘T’ is the lists data type.
Adding the Required attribute to a list-style property doesn’t really do what you want. The will complain if the list isn’t created, but won’t complain if the list exists with 0 item in it. However, it should be easy enough to derive your own data annotations attribute and make it check the list for Count … Read more
Yes, generics is a good choice. The key to achieving type-safety (and being identify the type with the Type property is to add an abstraction between the list and Field<T> class. Have Field<T> implement the interface IField. This interface doesn’t need any members. Then declare your list as being List<IField>. That way you constrain the … Read more
It’s because you used Function instead of Sub. Since a Function returns a value, the compiler considers that the equals sign (=) is used as a comparison, not an assignment. If you change Function to Sub, the compiler would correctly consider the equals sign as an assignment: TempList.ForEach(Sub(obj) obj.Deleted = True) If you had a … Read more
After adding an item to a list, you can replace it by writing list[someIndex] = new MyClass(); You can modify an existing item in the list by writing list[someIndex].SomeProperty = someValue; EDIT: You can write var index = list.FindIndex(c => c.Number == someTextBox.Text); list[index] = new SomeClass(…);