The AVG Antivirus tool sets out the T391918 example to quarantine

Don Boitnott

created 6 years ago (modified 6 years ago)

[DevExpress Support Team: CLONED FROM T706251: System Tray WPF application]
Using the example provided at that link (How to: Use NotifyIconService), the runtime menu gets the attention of my AVG virus scanner, which immediately sets out to quarantine the app as a bad actor. What gives?

Answers approved by DevExpress Support

Andrew Ser (DevExpress Support)

created 6 years ago

Hi Don,
I installed AVG Free on my side to check the example but the antiviral tool doesn't detect any issues with it - see the attached video. Please make sure that your AVG version is up to date.
Could you also clarify what reasons/messages your antiviral tool shows when it sets the sample to quarantine? What files are under suspect? Also, you can check them using any online antivirus service.
I recommend you contact AVG as their client and send your files so that they can research them and check if this is not a false alarm. I've found the following page on their website: https://www.avg.com/en-us/false-positive-file-form.

I look forward to your reply.

AVG_check.mp4

Show previous comments (2)

Don Boitnott 6 years ago

This appears to be a bad interplay between Visual Studio 2017's XAML processor and your NotifyIconService. First of all, I've implemented the Behavior as follows:

XAML
<dxmvvm:Interaction.Behaviors>  
    <dx:NotifyIconService LeftClickCommand="{Binding ActivateMainWindowCommand}"  
                          Icon="Antero.ico">  
        <dx:NotifyIconService.ContextMenu>  
            <dxb:PopupMenu>  
                <dxb:BarItemMenuHeader Content="Antero OPC/DDE Interface">  
                    <dxb:BarItemMenuHeader.ContentTemplate>  
                        <DataTemplate>  
                            <TextBlock Text="{Binding}"  
                                       FontSize="10" />  
                        </DataTemplate>  
                    </dxb:BarItemMenuHeader.ContentTemplate>  
                    <dxb:BarButtonItem Content="Open"  
                                       ItemClick="SystemTrayOpen_ItemClick" />  
                    <dxb:BarItemSeparator />  
                    <dxb:BarButtonItem Content="Exit"  
                                       Glyph="{StaticResource Symbols23_3DrawingImage}"  
                                       ItemClick="SystemTrayExit_ItemClick"/>  
                </dxb:BarItemMenuHeader>  
            </dxb:PopupMenu>  
        </dx:NotifyIconService.ContextMenu>  
    </dx:NotifyIconService>  
</dxmvvm:Interaction.Behaviors>

If I have that XAML page open in Visual Studio, I will immediately see a non-descript tray icon (see attached image). It is only when the debugger is attached that I get the AVG intrusion detection. If I close the XAML page, the icon goes away.

capture.PNG

Don Boitnott 6 years ago

Note: in the attached image, the image to the left of the non-descript one is my app. I get both when the XAML is open in VS and my app is running. The non-descript one does not provide the context menu, so it's not related to my app, but it does appear to be caused by the NotifyIconService XAML code in some way.

Andrey Marten (DevExpress Support) 6 years ago

Hello Don,

NotifyIconServce only adds an icon to the System Tray and such an antivirus warning seems to be a false alarm. I assume that you see a tray icon because Visual Studio executes this service's logic at design time. However, when I test the same steps on my machine, I do not see this issue (see the attached screencast).

Perhaps, this behavior is specific to your certain VS version or its settings. In my tests I used our controls v18.2.7 and VS2017 Version 15.9.8 on a machine with Windows 10 Version 1809. Could you please share your settings?

I've also discussed this scenario with our developers and we decided to add extra checks in NotifyIconService so that it does not add an icon to the System Tray if it detects that its logic is executed at design time. We will do this in the context of this thread: T729555 - NotifyIconService's logic can be executed at design time. Add it to your favorites to be informed about our progress.

Please note, I cannot guarantee that these changes will fix this behavior, because I did not manage to reproduce this issue on our side.

Thanks,
Andrey

T729143.mp4

Don Boitnott 6 years ago

Windows 10: 1809 (build 17763.379)
Visual Studio 2017 15.9.11
DevExpress 18.2.7 controls

Andrey Marten (DevExpress Support) 6 years ago

Thank you for the update. Our developers have added corresponding changes to this service. Once we publish the hotfix in the context of the T729555 thread, please test it in your application and let me know if it helps.
Andrey

Created: April 1, 2019 9:00 PM

Modified: April 4, 2019 11:48 AM

Platform: WPF

Product: MVVM Framework

Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

The AVG Antivirus tool sets out the T391918 example to quarantine

Answers approved by DevExpress Support

Recently viewed tickets