WASI preview2 introduces sockets, random, cli. A new analyzer detects if your Wasm module calls wasi:http/outgoing-handler (requires a Wasm runtime like wasmtime) vs. wasi:clocks (universal). It prevents deploying a Wasm module to a “pure compute” edge runtime that lacks HTTP proxy support.
CLI example:
portability-analyzer new scan ./src \
--target-platforms linux,windows,macos \
--output report.html \
--fix-suggestions detailed
Integrate into CI (GitHub Actions):
- name: Run Portability Analyzer
uses: portability-analyzer/new-action@v3
with:
source_path: './src'
fail_on: 'critical'
target_os: 'ubuntu-latest, windows-latest'
Old analyzers checked for __NR_open. New analyzers understand that openat2 (Linux 5.6) isn’t just a different number—it’s a different contract. Modern portability analyzers maintain a matrix of syscall availability per kernel version and architecture.
Example: If your Rust code uses io_uring (via tokio-uring), a new analyzer will flag: “Not portable to FreeBSD 13.x; io_uring is Linux 5.1+ only.”
If you want, I can generate:
.NET Portability Analyzer (ApiPort) is a tool designed to evaluate how portable your existing .NET code is across different .NET platforms, such as Microsoft Learn Important: Current Status As of recent updates, the .NET Portability Analyzer (ApiPort) has been deprecated . Microsoft now recommends using the .NET Upgrade Assistant for modern migrations. Microsoft Learn portability analyzer new
Because the backend service for ApiPort has been shut down, you must use it if you still choose to run it. Microsoft Learn How to Use the (Legacy) Portability Analyzer
If you still need to use the analyzer for a quick audit, you can access it via two main methods: Visual Studio Extension Download it from the Visual Studio Marketplace Tools > Extensions and Updates in Visual Studio. Configure your target platforms in Analyze > Portability Analyzer Settings Right-click your project in Solution Explorer and select Analyze Assembly Portability Console Application A standalone tool available on that analyzes assemblies (.dll or .exe files) directly. Microsoft Learn What the Reports Provide Portability Summary
: A percentage-based score showing how compatible your code is with your selected target platform. Detailed Breakdown : A list of every API used that is not available in the target platform. Recommended Changes
: In many cases, the tool suggests alternative APIs or NuGet packages to replace unsupported calls. www.michael-whelan.net Modern Alternative: .NET Upgrade Assistant For new projects, the .NET Upgrade Assistant
is the superior choice. It does more than just analyze; it can:
Automatically update project files (csproj) to the new SDK style. Update NuGet package dependencies to compatible versions. WASI preview2 introduces sockets , random , cli
Perform code transformations to fix common breaking changes between .NET Framework .NET 6/7/8 ApiDocs.co .NET Upgrade Assistant
Porting a .Net Framework Library to .Net Core - Michael Whelan
The traditional .NET Portability Analyzer (often called ) is currently being deprecated and replaced by newer modernization tools.
Here is a draft piece summarizing the transition to the "new" recommended workflow:
From Analyzer to Assistant: Modernizing Your Portability Workflow
If you are looking for the latest way to assess your application's flexibility across platforms, the landscape has shifted. While the .NET Portability Analyzer Integrate into CI (GitHub Actions): - name: Run
served as the go-to tool for identifying missing APIs when moving from .NET Framework to .NET Core, Microsoft is now pointing developers toward the .NET Upgrade Assistant as its successor. Why the Change?
The original Portability Analyzer relied on a backend service that has been shut down, meaning the tool must now be used in a restricted offline mode . More importantly, it is not supported in Visual Studio 2022
or later. To keep up with modern environments like .NET 6, 7, and 8, you must pivot to newer alternatives. The New Recommended Tools: .NET Upgrade Assistant
: This is the primary replacement. It doesn't just analyze; it can automate many of the changes required for an upgrade, including project file conversions and NuGet package updates. Platform Compatibility Analyzer
: Included in the .NET SDK, this Roslyn-based tool identifies APIs at compile-time that might throw a PlatformNotSupportedException on specific operating systems. Binary Analysis (Upgrade Assistant Preview)
: For those who need to check third-party dependencies without source code, the Upgrade Assistant now includes binary analysis features similar to the old ApiPort. Quick Comparison: ApiPort.exe to generate an Excel or HTML report of missing APIs. Upgrade Assistant extension
directly within Visual Studio 2022 to "Analyze" or "Upgrade" your project step-by-step. While the "alpha" version of the API Portability Analyzer
received a minor maintenance update as recently as May 2024 to support legacy environments, the path forward for new development is clear: the Upgrade Assistant is the new standard for portability analysis. on how to run the new Upgrade Assistant's analysis command for your specific project type? The .NET Portability Analyzer - Microsoft Learn