Showing posts from January 9, 2011

How To Write Good Code - Diagram

How To Write Good Code Funny Stuff... source . Hope you're having a good time, Elad Shalom, CTO at

IronRuby and Visual Studio 2010 - Integration

IronRuby and Visual Studio 2010. The IronRuby represents another one of Microsoft's attempts to have it all under one development environment. C / C++ VB.Net / C# / F# J# Their latest integration with jQuery IronPhyton And now - IronRuby. This addition is brand new and a very cool one.  The add-on for Visual Studio 2010 is exactly for those who like Ruby and wish it to be implemented in their .Net environment when needed. This IronRuby release (1.1.1) with Visual Studio 2010 integration includes: Ruby colorized and syntax checker. Interactive loop window. Directory based projects. Templates for common Ruby applications (including Ruby on Rails 3 , Sinatra , Gems and Silverlight based browser scripting app)    Source by Christopher Bennage. Thanks, Elad Shalom, CTO at

Multiple Solutions with the Same Structure - Visual Studio 2010 How To

Duplicating Solutions in Visual Studio 2010. As you probably know, I work in a company that provides sports betting solutions for many companies.  Each company has its own GUI and sometimes different flows inside the site. This is basically not hard to manage as long as you create a proper Skeleton Solution. A Skeleton Solution is a solution contains only the most relevant files and folders.  The same classes and JavaScript files that exist in every other solution. A Skeleton Solution will contain, in most of the times, several projects. I believe you've read my article about File Sharing in VS 2010 . This article is in some way an extension of the one I just mentioned. How to Create a Skeleton Solution from an Existing Solution: It's even easier then you think. Create a folder named: "Base Solution" or "Skeleton Solution". Copy the content of your existing solution's folder. Paste the content inside your Skeleton Solution's folder.

Refactoring - Manage Your Code and Layers

Refactory - Design Improvement of the Existing Code. When I say Code Management most people tell me "I know exactly what I wrote... I know exactly where everything lays". Well.. This sentence usually takes me back to when I was 6 or 7 years old.  My mother used to tell me to clean and organize my room  and that's exactly what I told her...: "But mom...  I love it when my soldiers are under the carpet, my school books are in the closet, my clothes are on my library and my shoes are where my action figures were. I'm pretty sure most of you are nodding and agreeing with me. But this is wrong. Back to development then... There are several file types that should be in a unique folder (for each) in every project:    1. JavaScript    2. HTML    3. CSS JavaScript should not be inside "script" tag. CSS should not be inside "style" tag nor inside the element it's affecting. And HTML... Well... HTML should be on his own. Now I w