I've run into this before. You are correct in that the compiler is looking in Foobar.System.Windows.Forms because you named your namespace 'System'. The local namespace 'System' overrides the global namespace 'System'. I do not know how to get around this. In my case I chose not to name my namespace 'System' but instead named it 'Foundation'. I just wanted to let everyone know that therei s nothing messed up with your project.
User 2183100
Posts
-
Namespaces, aliases and Visual Studio Forms Designer -
what is the maximum sizePlease don't read a 2gb file all at once. Thats just insane. Read it a little bit at a time, say, 1 mb or 10 mb, or whatever. Like the other guy said, check out StreamReader.
-
componentI'm sorry, english must not be your primary language but please, describe exactly what you want, what you expect it to do, how you expect it to do it, what it is for, and please use more than one sentance to explain all of this.
-
Too many generics in code.How about:
public class MyComplexList: NodeHeap<Node<SimplePathFinder<TTileMap, TTile, TData>, TTileMap, TTile, TData>,
SimplePathFinder<TTileMap, TTile, TData>, TTileMap, TTile, TData>
{
};MyComplexList openList = new MyComplexList();
-
Wasted spaceI suspose you also believe lambda expressions shouldn't be used either? They are even harder to read but shorten the amount of written code by huge degrees. I wrote my first one today. Granted it's quite simple but its effective. return ModifiedKeys.First(kvp => kvp.Value == id).Key; Just to help you out, ModifiedKeys is a Dictionary. This line returns the first key in my dictionary who's value matches id.