This must have happened with a fairly recent definition update as I did not have it a week ago (I'm not sure when I last opened this software but it couldn't have been more than a week). A piece of software I wrote was flagged as a virus and blocked the second I compiled it to run it. I then went to open an older build of it (I was already in visual studio originally so building and launching was more convenient) it also found that to be a virus.
Like I said I wrote the code myself so I know it is not a virus. It goes on the local network, lists some configuration files to you (XML files with a custom extension), lets you pick one and edit it. Perhaps the weirdest part though is that this program has very little code in and of itself. It works by loading a running a Form in a DLL (a referenced project in Visual Studio that's built to a DLL). Other programs that use this DLL (but start from a form within themselves) do not have an issue. The entire code of the exe can be placed here:
using System;
using System.Collections.Generic;
using System.Windows.Forms;
using ATE.GUI.Dialogs;
using ATE.Configuration;
namespace ATE_Results_Loader
{
static class Program
{
/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main()
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new ATE.GUI.DataViewerForm());
}
}
}
ATE.GUI.DataViewerForm is within the DLL (which does not report as suspicious)
