Wednesday, September 20, 2006
Ok, I am finnaly done creating the Server end of my Client/Server application. Or at least I am done for now, until I find some more features to incorporate into it. Migrating the code over to VS2005 was a bit of an annoyance. Even though the initial migration done by Visual Studio claimed that there was no error in the conversion, when I went to run the application, there were over 150 code "warnings" which stopped compilation. Which in-it-of-itself was strange, I am used to warning not actually preventing compilation...but apparently it does in most cases in VS2005. I would consider those errors...not warnings. So it took me roughly about 3 weeks to clear out all the errors and warning, and then to cleanup and revamp a lot of the code to work cleaner in VS2005, mostly in Multi-Threading.
Now I move over to the Client side application which I expect to be easier because there is not as much code in the Client application that there was in the Server application. Once I am done, the Client will have a ton more code then the Server, but right now, it's a work in progress.
Monday, September 18, 2006
For anyone who wants to inflict a migrane in a relatively short amount of time...consider programming Multi-Threaded applications. I found that while designing, implementing and debugging Multi-Threaded applications, you have to have the ability to think multi-dimensionally. I found that when speaking to many programmers in the field, that not many of them actually have a grasp on multi-dimensional thought and Multi-Threading in a programming environment. Although I will admit that there are many who claim to know, and just end up running around in circles chasing their own tail when attempting to explain or help someone debug such applications. I myself will not say that I am an expert in the field of Multi-Threading programming, but I think that I have a good grasp on it.
I don't know if there are any other programmers that have opinions on how Multi-Threading is applied in VB.Net but I have a few. I do like, for the most part, how Multi-Threading is handled in the .Net environment, but I have to admit, sometimes it's kinda convoluted. I have come across some relatively simple ideas, but when it came time to convert those ideas into .Net I have found that the coding ended up being way more complicated then the original idea.
On a side note...working with Multi-Threading, I realized how much I missed the ability to state:
objMyForm.Modal = True
Name: Tekk Guy