I am a self-taught programmer. I have been coding in VB for probably 6 years now, but have been devoted 100% for the last year. As the applications I am writing get larger and more complex, I am always trying to keep them as efficient as possible, but still always end up with a lot of spaghetti code.
What I am having a hard time with is the architecture of my windows forms applications. I have tried to find resources related to the 'best practices' but cannot find much that really helps me understand. I am trying to stick to the Logical N-Tier approach but I still have a lot to learn. The application I am currently working on is pretty complex and interfaces with multiple web services and MySQL databases. With this, I am finding it difficult to keep all my code in order.
I have two questions for anyone who will listen: First, how do you know what code to put on the form and what to seperate out into another class or module? How much seperation is too much?
Secondly, does anyone have any good references they have used to help understand proper application architecture?
This post has been edited by AdamSpeight2008: 16 November 2011 - 03:22 PM