Originally Posted by Kevin M
My apologies if anything I wrote seemed hostile! Definitely not intended. If I had to guess at what was making Avast suspicious I'd say it's the reflection combined with PackageManager calls but this is hardly unique to NoMapTips. Does it give you a reason or some kind of reference number? Thanks for reporting.
No worries, my friend!
I just took it as maybe MY wording was harsh or something. I felt bad that I came across that way. Funny now, huh? <lol>
No, I don't recall Avast giving me any type of number.
I uninstalled it and am going to try installing it again. Maybe something got corrupted, or it was a fluke. It happens.
If it helps any, it was only after this most recent update that this happened. Before that, it never sent up any flares.
I really did not think it was an actual virus. I just figured there was something in the updated code that was causing Avasf to react and so I'd let you know so it could be nipped in the bud before a bunch of people started bugging you about it, that's all.
If it does it again, I do believe you and I'll just set Avast to "Ignore" it.
Thanks again for the quick response, my friend!