I'm looking for best solution to migrate FASM projects to VisualStudio.

Overclick wrote:

I'm looking for best solution to migrate FASM projects to VisualStudio.

Visual Studio doesn't have assembly language support.

What exactly I have to convert or replace on it?

But virtual probably isn't a MASM thing.

If a custom build script is what passes for "support"

@echo off
setlocal

:: Usage
if "%~1"=="" (
    echo Usage: sign.cmd [debug^|release] path_to_binary
    exit /b 1
)

set MODE=%~1
set FILEPATH=%~2

:: Path to signtool.exe, adjust as necessary
set SIGNTOOL="C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\signtool.exe"

:: Check if signtool exists
if not exist %SIGNTOOL% (
    echo signtool.exe not found.
    exit /b 1
)

:: Proceed based on mode
if /I "%MODE%"=="debug" (
    echo Debug mode: Signing with self-signed certificate...
    :: Ensure you have created a self-signed certificate named MySelfSignedCert.pfx
    %SIGNTOOL% sign /f MySelfSignedCert.pfx /p password /fd SHA256 /td SHA256 /tr http://timestamp.digicert.com /v %FILEPATH%
) else if /I "%MODE%"=="release" (
    echo Release mode: Signing with CA certificate...
    :: Assuming you have a CA certificate named MyCACert.pfx
    %SIGNTOOL% sign /f MyCACert.pfx /p password /fd SHA256 /td SHA256 /tr http://timestamp.digicert.com /v %FILEPATH%
) else (
    echo Invalid mode. Use 'debug' or 'release'.
    exit /b 1
)

echo Signing completed.
endlocal    

makecert -n "CN=MyTestCertificate" -r -sv MyTestCertificate.pvk MyTestCertificate.cer
pvk2pfx -pvk MyTestCertificate.pvk -spc MyTestCertificate.cer -pfx MyTestCertificate.pfx -po YourPFXPassword    

Requirenments says I need VS