> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/supported-languages/supported-languages-list/.net/troubleshooting-snyk-for-.net.md). # Troubleshooting Snyk for .NET How to resolve common Snyk problems for .NET, including static dependency resolution for legacy Project files and Legacy Broker setups ## .NET SDK resolution limitations Snyk uses static analysis instead of the .NET SDK to resolve dependencies in the following scenarios: * Legacy Project files: Projects use legacy non-SDK style Project files. * Legacy Broker: Organizations use the Legacy Broker instead of the Universal Broker to connect to brokered private package repositories and SCMs. To improve accuracy, migrate to the Universal Broker. ## Static analysis limitations Static analysis does not support the following: * Private dependencies: Snyk cannot access private dependencies, brokered or non-brokered. Snyk does not resolve transitive dependencies. * Build configuration: Snyk ignores `Directory.Build.props`, `Directory.Build.targets`, and `global.json` files. * Runtime precision: Snyk cannot reliably identify the specific runtime, which can increase false positives. ## Handle runtime false positives Static analysis can flag vulnerabilities that are already patched in your environment, because it cannot always detect your specific runtime patch version. ### Vulnerabilities in SCM If your application runs on a system updated with the latest Microsoft patches, a flagged vulnerability can be irrelevant. You can ignore these vulnerabilities in the Snyk Web UI. ### Vulnerabilities in CLI If your production environment pulls the latest patches or you deploy a self-contained application, use the following configurations in your project file to improve accuracy: * Latest SDK patch: If your application always runs on the latest SDK patch version in production, set `TargetLatestRuntimePatch` to `true` in the project file. Ensure you upgrade all environments to the latest runtime version. * Self-contained applications: If you publish a self-contained app that includes the runtime, set `RuntimeFrameworkVersion` to the specific patch version in the project file. You can ignore vulnerabilities that are no longer relevant. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snyk.io/supported-languages/supported-languages-list/.net/troubleshooting-snyk-for-.net.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.