Read: 2825 times    -     Avarage Rate: 5

2010 13 Aug

Software development process should take into account many considerations. In general, we can divide them into two categories: functional which correspond to the main functionality of the software, and non-functional as security, persistence, maintenance, etc. This paradigm of separation leads to improve the modularity of software. Aspect Oriented Programming (AOP) is a new programming paradigm dealing with this concept. An aspect is a software entity
Read: 1900 times    -     Avarage Rate: 4

2010 29 Mar

Let’s face it; we all d/o bad things while coding one time or another. Let’s avoid them as best as we can because we may read the code one year later, and we'll not be able to easiely understand it. In addition to the points that we handeled in the series of software coding standards, let’s pass by some points, which enhance our coding skills: Avoid putting using statements ins
Read: 2018 times    -     Avarage Rate: 5

2010 26 Mar

In my series of software coding standards I'll talk today about the second principle, which is casing in naming . While I was looking to how to name a function that needs two or three words to explain its job, I noticed that there are more than one casing concept, accordingly to official Microsoft speackers, C# standards dictate that you use a certain pattern of Pascal Cas
Read: 1799 times    -     Avarage Rate: 3

2010 25 Mar

“The beginning of wisdom is to call things by their right names” – Chinese Proverb “Meaningful” is the keyword in naming. By meaningful names, I mean concise names that accurately describe the variable, method or object. In this article of my series software coding standards we'll see how this would be in C#:
Read: 2079 times    -     Avarage Rate: 4.2

2010 23 Mar

Introduction When I was looking for a standard convention for generics, I came across a 50-page manual for coding standards for C#. I am sure that, apart from the author, there are few who actually go through and read all of them. So, I thought of coming up with this article. I have tried to comprehend the essential facts which we developers sometimes neglect in C#. I will also discuss some common pitfalls. Small, sweet and simple. That’s how I describe it. I
Read: 1753 times    -     Avarage Rate: 4.2

2010 19 Mar

Software applications are based on layers and the communication between them, so the main task in the design of an application architecture will be the identification and creation of layers and then to specify a communication language and set the rules and guidelines of the interaction between these layers. To start the design of an application architecture, the architect should keep in mind the following points: Separation of concerns Clearness in the communication r
Read: 1919 times    -     Avarage Rate: 3.5

2010 19 Mar

Hello, All developers who use SilverLight 3, can feel the limitations in the production of many critical issues and functionalities, especially when you try to create printable reports, or to show and manipulate Right-to-Left languages data, SilverLight 3 don't allow the use of right click menu context, in addition to a good number of other limitations that Microsoft took into consideration in the beta version of SilverLight 4. In fact, SilverLight 4 enhances and introduces ne
Read: 3428 times    -     Avarage Rate: 4.5

2010 18 Mar

Software Developers phobia is code optimization, how to write faster codes? How to make programs runs faster at the same hardware? How to make your client happy? Heaving read a few million lines of C# code, I came up with these optimization benchmarks that help to significantly improve code performance through simple changes. 1. Boxing and unboxing static private void TestBoxingAndUnboxing() { int i = 123; object o = i; // Impl
Read: 1909 times    -     Avarage Rate: 3.7

2010 15 Mar

I've been programming since I was 15 and I've loved technology and programming every since, during that period I’ve learned some lessons that i would like to share. Here are my most memorable 15 lessons so far. Set a time expectation of every task- don’t sit in from of the monitor trying to solve a problem for 8 hours. Set a time table for yourself of