• .NET

    4 Steps to Profile Your Apps

    October 11, 2012 Share
    JustTrace makes profiling your application easy. Just follow these four steps and you will soon be on your way to identifying and removing memory leaks and performance issues. Keep in mind, profiling is best done regularly so you can detect unusual behavior early and avoid problems before they manifest. Follow these four steps to profile your applications with JustTrace: Assess, Acquire, Analyze, and Act.  Step 1: Assess Determine what kind of issue you have. Is your application’s memory continuously growing while running? You have a memory leak. Do some parts of your application take too long to run? You have a performance...
  • .NET

    Bad code exposed! Do you really know when your code smells?

    September 24, 2012 Share
    I’ve seen really bad code in my day. I have seen it in legacy code bases, code reviews on greenfield projects, and worse: I’ve even seen it in my own code. In fact, I can open up just about any open source project and immediately detect the existence of potentially bad code. I am not bragging… it is not as though I am incredibly gifted or that I have superhuman powers. I’ve experienced enough issues from bad code to intuitively pick up on much of it, and the rest of my knowledge comes from reading books on the subject of writing...
  • .NET

    Just* works even better in Visual Studio 2012

    September 20, 2012 Share
    Exciting news never comes alone. The brand-new Visual Studio 2012 is officially released bringing lots of good and handy new features, options and opportunities for all .NET developers. Telerik is never behind, and we’ve released Service Packs for your favorite Telerik tools that make them integrate seamlessly with Visual Studio 2012. The recent Telerik JustCode Service Pack 2 adds dynamic support for the new color themes in VS 2012. This means that if you change the colors and theme of your Visual Studio 2012 instance, JustCode will simply pick them up and use them. And if VS looks good, JustCode will look...
  • .NET

    5 Things You Should Know About Refactoring in C#

    September 10, 2012 Share
    There are many misconceptions among developers and development managers about refactoring. Perhaps a consultant used refactoring as an excuse to spend needless cycles reading blogs, or maybe a “refactoring” was blamed for a large swath of bugs found in a release. Regardless of the source, there are development shops that cower in fear or scream in terror when the word “refactoring” is uttered aloud. The problem is they were frightened by something other than refactoring. I hang out with developers around the globe at conferences, user groups, and sometimes just to grab a bite to eat. I enjoy discussing code and long...
  • .NET

    Top 5 Reasons Why You Should Refactor Your Code

    August 20, 2012 Share
    I am a huge proponent of writing quality code, a view that is shared by many of my colleagues. Unfortunately, I do encounter those who do not share my enthusiasm. Their view is often one of “Get It Done,” whereas I take the position of “Get It Done Right.” When discussing refactoring, the “Get It Done” developer often brushes it aside as a waste of time. I want to address that crowd, and anyone else who eschews refactoring, with my top 5 reasons why you should refactor your code. Enjoy! 5. Your Code Sucks Broken Bridge / jollyUK / CC BY How often do you write an...