Hi Rafal, is there or will there be a way to configure what issues CODESCAN checks? For example, maybe where I work, we consider it okay to initialize variables using functions in the declaration section (not that we actually do consider this okay, but just using an example from the VS Extension download page). Is there or will there be a way for us to configure / fine-tune what CODESCAN brings up as a compiler warning?
(Great tool by the way. Definitely going to try this out.)