Giulia Stocco

@fabi that is the implementation in .net core 3.1 which is why we are not using it currently. In the issue linked this is addressed in .NET 5 `Can run...

I understand now the distinction you are drawing. It sounds like it may still need to extract native binaries. Thanks for the extra info!

Hi Thomas, To help me understand better. What is your use case that requires .msi? Gabe -------- Original Message -------- On Jan 9, 2020, 11:04 AM, Thomas Garrity wrote: >...

How do you envision accessing ASA after it is installed? Do you want it added to the PATH?

I'm trying to get at what the msix itself will give you as a user. ASA must be run from the command line so it's not actually made simpler for...

> ok I guess I'm not following you when you are talking about "adding to the PATH". ASA should be run from a command prompt. Adding it to the path...

Correct. My recommendation is to launch the binary (Asa.exe) directly in powershell. If you want to follow the directions in the Wiki those work too, but launching directly shouldn't trigger...

We now have a one line installer if you have .NET Core already installed on your system. `dotnet tool install Microsoft.CST.AttackSurfaceAnalyzer.CLI --version ` Right now that is `dotnet tool install...

@poortom1004 Attack Surface Analyzer 2.2 is now out with a one line install/uninstall using .NET Core. First install [.NET Core SDK](https://dotnet.microsoft.com/download). Then run `dotnet tool install -g Microsoft.CST.AttackSurfaceAnalyzer.CLI` This will...

It looks like the argument is AnalysesFile for the collect commands but filename for the verify command. This is definitely incongruous, but the "filename" parameter there is specifying the analysis...