code-analysis

Are there any static or dynamic code analysis tools that analyze XSLT/XSL code? The resources I have been able to find so far are: 1. Oxygen xml editor 2. http://gandhimukul.tripod.com/xslt/xslquality.html which looks faily basic in its capabilities There are quite a few testing tools and verifiers at Tony Graham's XSLT Testing Tools page. If you haven't looked there, it's a fairly comprehensive list. Using Saxon in schema-aware mode will catch many common errors. You've already discovered Mukul Gandhi's XSL Quality tools, which support user-added extensions. On the xsl-list run by Mulberry

FxCop (tool for static code analysis) gives me an error while checking code behind of .edmx model. How to prevent FxCop from analyzing auto-generated code (or at least Entity Framework generated classes)? I have moved to Visual Studio Code Analysis, as it gives me the same functionality as FxCop. From FxCop blog : "That's correct, they are different products (FxCop and VS Code Analysys), however they do have a common engine. Visual Studio 2008 SP1 already comes with the same fixes and analysis (plus a little bit more), so there is no need to 'update' Visual Studio with the latest FxCop." But

Where can I disable live code analysis in Visual Studio 2017? This pops up every time I start my solution. I do not need this: I've followed this support document from Microsoft but unchecking "Enable full solution analysis" seems to have no effect on live code analysis . Then I found a solution for Visual Studio 2012 but also without any luck. So it seems to me that live code analysis is a complete different thing not managed by full solution analysis . It is running immediately as a background process task after (re)starting the solution. Anyway, how can I get rid of this? It's not possible,

Source code analysis and exploration tools for C and C++ seem to be sorely lacking. Are there any tools which I can use to gather information about C and/or C++ source files? cscope does part of what I would need, Doxygen looks closer. At a minimum list of all function, callers, callees, variable references etc. Perhaps Doxygen's xml output would work. Ideally gcc or llvm could be hooked for this purpose but I have yet to find a convenient way to do so. Any suggestions? There is the clang static analyzer which is part of the clang front end for llvm, but I don't know how well it works for C/C+

Code analysis: ON_NOTIFY(TCN_SELCHANGE, IDC_TAB_HISTORY_TYPE, &CAssignHistoryDlg::OnTcnSelchangeTabHistoryType) Warning C26454: Arithmetic overflow: '-' operation produces a negative unsigned result at compile time (io.5). The definition of TCN_SELCHANGE is: #define TCN_FIRST (0U-550U) #define TCN_SELCHANGE (TCN_FIRST - 1) I can't see what else I can do! You are trying to subtract a larger unsigned value from a smaller unsigned value and it's causing the result to wrap past zero. In your case, I assume TCN_FIRST is defined as 0 so setting TCN_SELCHANGE to one will fix the problem. You should

Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Sometimes one needs to dig into someone else's code, understand it and maybe refactor/fix it. So I'm wondering what tools/practices do you use to do that? It's not about any specific language or platform, rather some advises in general. I myself find it very useful to run the code in question under debugger (if it is possible of course), set breakpoints and step through the code.

I am trying to find private methods that are not called from any other code (CA1811) https://msdn.microsoft.com/en-us/library/ms182264(v=vs.110).aspx , with Visual Studio 2012 Code Analysis buy it doesn't detect it, despite putting the project code analysis rule set in " all rules ". This is possible? In this case, how can I configure my project solution? In case of installing any extension, I will prefer that it was free. Thanks! The rule CA1811: Avoid uncalled private code perfectly works fine to detect the uncalled private methods. To enable the code analysis warnings, you also need to set