Performance is awful

4 posts, 0 answers
  1. Joel Reinford
    Joel Reinford avatar
    32 posts
    Member since:
    Sep 2004

    Posted 19 Mar 2010 Link to this post

    I've been a Telerik customer for about 5 years and this is the first product that I would NOT recommend to others. I put it on several different machines with different configurations ranging from mid-level to high end (all dual core or better, 2-8 GB of RAM, Raptor hard drives to OCZ SSD, Windows XP to Vista x64). It is sllloooowww on all of them, caused out of memory exceptions on the 2 and 4 GB machines and refuses to uninstall on two Vista x64 computers.

    In addition, lots of false positives for problems that aren't problems. Users beware, this product isn't quite ready yet. Maybe on the next release.

  2. Chris
    Admin
    Chris avatar
    221 posts

    Posted 22 Mar 2010 Link to this post

    Hi Joel,

    I'm terribly sorry to hear you've had such problems with JustCode. We'll try to do what's possible to fix these problems not only for the next release but even earlier for the first service pack.

    Unfortunately we can't reproduce these problems locally and we test JustCode against a large number of solutions. We test it with all the company's codebase and with some popular large open source projects. Some of these solutions consist of about 20,000 - 30,000 lines of code and some of them exceed 1mil. lines of code. With that I want to say we really pay attention to the quality of our products and we'd really appreciate your assistance on helping us pinpoint the problems you've mentioned.

    We haven't yet received any exception reports or "Good Code Red" reports from your email account and these reports would really help us a lot. When some exception occurs in JustCode you should see a red warning sign in VS' statusbar, just double click it and then click the "Send" button.
    In order to report "Good Code Red" problems (false positives) you could position the cursor in one of these false positive, press Alt + Enter and then select "Report Good Code Red". You could also right click in the JustCode Error List Window and select "Report Good Code Red" from there.
    I hope doing this won't take much of your time.

    If for some reason you're not able to use the above mentioned techniques for reporting problems in JustCode, perhaps a screenshot of the problem(s) could also help us.

    About the false positives - could you tell us whether they're C#, VB.NET, JavaScript, HTML or XAML? Sometimes a single issue could lead to a large number of these errors and fixing it could take us only an hour or a day. It's just a matter of whether someone would report this problem so that we can react in a timely manner. For example currently we have an issue with parsing one of the latest SL 4.0 assemblies and this issue could lead to a large number of false positives if you're using SL 4.0. The fix for this problem will be available in the next internal build of JustCode scheduled for the end of the week.

    Once again, sorry for the inconvenience and thanks in advance for helping reproduce and identify the problems you're having.

    Regards,
    Chris
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  3. DevCraft banner
  4. Ian Morris
    Ian Morris avatar
    1 posts
    Member since:
    Apr 2010

    Posted 21 Apr 2010 Link to this post

    Hello,

    I would second some of the problems reported here. 

    It hammers my PC and I find it running full tilt when I am just editing a bit of Javascript (as part of a larger solution). It's as if it rescans the entire solution on every change.

    As for false positives, every error reported is one that VS apparently missed! The funniest one is where it wanted me to remove the brackets from a function call that had no parameters, something like this:

    String1 = String2 & AClass.AFunction() & String2

    It complained that AFunction was not a member of it's class! Also errors with mixing integer types when doing bitwise operations, using '>' and '<' with strings (I'd agree a warning but an error?) and there some others I don't recall.

    I think this is a useful product, but it shouldn't have been released yet. Also, I found that the default options were not helpful. All my colour syntax formatting changed and ^W^E no longer brings up the error list, though VS says this isstill  the correct key combination. Presumbaly JustCode has remapped some keybindings?

    I've disabled all types from code analysis yet it still seems to scan things, how can I turn it off without uninstalling it?

    Regards,
    Mark Leavesley
  5. Chris
    Admin
    Chris avatar
    221 posts

    Posted 03 May 2010 Link to this post

    Hi Mark,
    Sorry to hear you've had such issues with JustCode. Could you please try the SP1 release of JustCode. We've fixed quite a lot of issues in that build.
    As for the color identifiers, here's how you can disable this option:

    http://blogs.telerik.com/joshuaholt/posts/10-04-26/justcode_ndash_color_identifier_basics.aspx

    or how you could customize the colors:

    http://blogs.telerik.com/joshuaholt/posts/10-04-28/justcode_ndash_color_identifiers_in_depth.aspx

    About the ^W^E key binding, it's quite strange as JustCode doesn't use this key binding. What you can do is to open Tools -> Options -> Keyboard, press the cursor inside the "Press shortcut keys" textbox and then press the shortcut. Then take a look at the "Shortcut currently used by" dropdown, it will display the commands which are using that shortcut.

    Kind regards,
    Chris
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top