The nested generic syntax is very powerful, but ugly (but I think there is no rational way around that problem) so errors are often difficult to spot, especially if you haven't used them very much. The problem in the code snippet is List<float,float> you can only have one generic type in a list (e.g. List<float> If you want to store two floats this way, you need to create a class with two float properties (Like the example I posted yesterday) e.g.
public class Foo
{
public float Value1 { get; set; }
public float Value2 { get; set; }
}
public class Program
{
public void Main()
{
Dictionary<string, List<Foo>> Bar = new Dictionary<string, List<Foo>>();
}
}
I suggest you research both generics, and the various common collection types (e.g. List, Collection, Dictionary, Linked List, Hashtable, Set etc.). The .Net framework doesn't have all these (e.g. I've had to implement a Set type), but a grounding in each will let you know when to use it and will stand you in good sted in your career.
CCC solved so far: 2 (including a Hard One!)
