I use a variety of IDE's (Programing Environments) such as Visual Studio. However, the problem I have relates to Dark BASIC Professional (DB).
When DB compiles the Code into an executable, SONAR pounces on it and zaps it to quarantine. Normally, you can tell NIS to restore the file and ignore it from future zapping. However, as DB produces a new executable every time you re-compile the Code, SONAR pounces on it again. Even if you tell NIS to ignore the file from future zapping, I guess it just thinks that it is a new file (it would have a different signature (size, date/time, etc), even if it has the same name and in the same Folder.
Any suggestions on how I can get around this without turing SONAR off (which I don't want to do, and have to do when I use the Dark BASIC Development Environment)?
I have scanned through the settings (NIS), but can't seem to find anything that can help me deal with this.
Thanks,
Chris.
p.s. the sub plot to this post: Why is SONAR doing this? It is obviously something to do with the Dark BASIC System. As I wrote the Code for my programs, I know that they are not malware!, but Dark BASIC has built in functions to help with a variety of things (such as writing to the display) which must be included in the compiled program. Possibly some of these the heuristic engine of NIS traps as being 'suspect'. I wonder if anyone as Norton can take this up with 'The Game Creators' (who make/release Dark BASIC). www.thegamecreators.com.