add check for obsolete methods/properties/events to Sequence Analyzer

[warren_scott]

I know that I can write my own sequence analyzer tasks, but I think this one should be default out-of-the-box from NI:

Add a sequence analyzer warning task that checks for usage of obsolete methods / properties / events.  This way we can use sequence analyzer to help find them and make our code easier to upgrade with future versions of TS

Otherwise, trying to find all the obsolete "stuff" is REALLY REALLY annoying -- a lot of searching

[AllenP]

Warren,

Would you expect this rule to only search API calls within the Sequence File?  Or also to search code modules?

[warren_scott]

It would be really nice if it could search within code modules, but that is getting too close to having TestStand control code analysis for client code, which is way too complicated.

What I think would be a realistic expectation:

Phase1: implement out-of-the-box analysis rule that searches just within sequence files.

Phase2: (bigger issue, but this would be GREAT if it could happen) is a "toolkit" to install that is a set of custom VI analyzer rules for TestStand modules, and maybe others for other languages as appropriate that would look for things like this.

Phase3: maybe some way of having a TestStand workspace/project Sequence Analyzer task integrate with VI Analyzer.  Would be pretty cool, but it would take a bit of head scratching to figure out how well it would work out.