We should be able to optionally exclude encrypted Objects from Analyze Project or at least list them in it’s own section of the Report.
Because we use Analyze Project to move our Projects from API 1 to API 2 and 3rd Party Controls, Classes and so on, which can’t be fixed by our selfs, clutter the report.
That’s a good point. And most encrypted classes won’t be updated because we need to support older versions. On the other hand, I’m not sure this can be implemented because analyze needs to look at the whole project. Take out the class, and the project doesn’t compile.
They’d probably need to simply drop the results from the final report.
[quote=457201:@Sascha S]We should be able to optionally exclude encrypted Objects from Analyze Project or at least list them in it’s own section of the Report.
It would be nice to be able to set analyze project to ignore API 1.0 deprecations for projects you want to maintain backward compatibility on.
Failing that (which I suspect they won’t do because they want us to change and that makes it too easy not to) let us be able to set an attribute so that Analyze project ignores API 1.0 deprecations for modules, classes or methods, even if not encrypted, for items using API 1.0 code you don’t intend to change and know works.
I thought encrypted classes were not scanned by Analyze project, but 2019R2 finds deprecations about Timer/Action that should now be “Run” in the demo, encrypted classes.
Apart from that, nothing. Looks like a fluke.