Update Add-D365WindowsDefenderRules to a new VS2022 version about d365fo.tools HOT 6 CLOSED

I started work on this, see #783
Seems that the paths for the Dynamics related executables got outdated at some point, I updated them as well.

I still have to look at the following executables and other exclusions from mfp:
AosDeploy.exe
axsetup.exe
robocopy.exe
git.exe
vstestconsole.exe
qtagent32.exe
qtagent32_40.exe
Extensions: *.md, *.man, *.xml, *.xpp, *.netmodule

from d365fo.tools.

I ended up not including AosDeploy.exe and axsetup.exe from mfp's exclusions, because I couldn't find them on environments I have access to. Also did not include robocopy.exe because it is already listed in the exclusions, as is qtagent32.exe. The rest was added.

from d365fo.tools.

Good suggestion, I will look into that.

Also very nice report on your experience with a highend machine for x++ development!

Put a breakpoint to SalesTable.init and attach to process: almost instant (2-3 seconds)

🤤

from d365fo.tools.

Maybe AosDeploy.exe and axsetup.exe are from the package installation, so normally they don't present.

from d365fo.tools.

@TrudAX I had the same idea, but couldn't find those executables in a service update package contents. Internet search says that axsetup.exe is an AX 2012 thing, no mention of it for D365FO. And no mention of AosDeploy.exe at all.

from d365fo.tools.

@TrudAX Just stumbled upon the following comment in the web.config file:
<!--These are the default onebox values. These will be overwriten by values in oneboxconfig.xml in AosDeploy.exe-->
Seems like AosDeploy.exe is used in creating one box environments.

from d365fo.tools.