We want to use .NET Standard for the extensions if possible so that we
could potentially run them in Visual Studio at some point. The reason
the default extension was not .NET Standard is because the try-convert
stuff uses MSBuild directly and was forcing .NET 5+ to be the TFM. This
change moves try-convert to be its own extension which allows the
default extension to be .NET Standard.
We have been using information from a lock file to identify the transitive dependencies for a project. This is problematic for our use cases in a couple of ways:
- Requires that the project file be up-to-date with the packages we want to check which may not be the case
- Requires `dotnet restore` to be run and we end up running it fairly often to ensure things are up-to-date
Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.SwaggerGenerator.MSBuild , Microsoft.DotNet.SignTool , Microsoft.DotNet.Helix.Sdk
From Version 7.0.0-beta.22064.25 -> To Version 7.0.0-beta.22071.6
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
This changes so default extensions are loaded
before custom extensions. This means custom
extensions can override things like default templates
from the default extension
* test fixes
* Addition of Format Provider for analysis support
* Addressing PR comments pertaining to writer provider for htmlview
* Removal of extra line in ConsoleAnalyze
* Test change for sarif
* Separating testing classes for writers
* Looping in the renaming of the AnalyzeResultWriterTest
The transitive dependency analyzer often seems to cause problems with loops. This change moves it so that it occurs after all the analyzers are run by moving it into its own step.
This change enables a user to run conversions to SDK style as a unit of work before continuing on to additional code changes. Currently set behind a feature flag so SOLUTION_WIDE_SDK_CONVERSION must be enabled for the solution wide conversion to be used.
* test fixes
* This pr reflects updates to changelog and readme based on the addition of the format feature flag
* Addition of the pr link in the changelog
* Revert "test fixes (#982)"
This reverts commit 02b49ff0ed.
* Git revert to reduce noise and make log fixes
* reintroduction of file fixes
* Revert formatting changes in README.md
* Revert formatting changes in README.md
* Revert formatting changes in README.md
* Revert formatting changes in README.md
* Revert formatting changes in README.md
* Revert formatting changes in Changelog.md
* Reword format parameters option
* inclusion of html format for readme explanation
* Nit Formatting
* Nit Formatting
* Nit Formatting
* Nit Formatting
* Nit Formatting
* Nit Formatting
* Nit Formatting
Co-authored-by: Sunanda Balasubramanian <subal@microsoft.com>
* Addition of the Htmlview feature
* Fixes to some pr comments
* removal of extra function
* Change to embedded resource for the html template
* Code cleanup in AnalyzeResultWriter
* removal of UpgradeLog
* check fixes
* more check fixes
* Cancellation Token removal
* feature flag fix
* fix for feature function
[main] Update dependencies from dotnet/arcade
- Update SDK version to .NET 6 GA
- Merge remote-tracking branch 'origin/main' into darc-main-670d7585-c802-4fed-8ac9-45adcc587dc4
- Deal with new warnings
- use latest nuget
- Merge remote-tracking branch 'origin/main' into darc-main-670d7585-c802-4fed-8ac9-45adcc587dc4
* Improving SARIF with HelpUri, full description, specific rule name
* Updating all classes, updating tests
* Addressing PR feedback
* Updating tests and class
* Adding comment
* reverting
* Adding specific ruleIds for packageanalysis
* Addressing PR feedback
I found a few Razor source updater issues while investigating #856. This addresses them by making sure that source updates are correctly able to edit parts of the project other than cshtml files if needed and by improving the logic for mapping changed code back to cshtml files.
Fixes#856Fixes#914Fixes#915
* Update README.md for .NET 6 launch
* Updated README.md based on feedback to make it free of a specific .NET version
Using "latest .NET version (current, LTS, preview) to support future version releases, etc.
* Update LTS, Current and Preview to point to .NET6
* Update tests to reflect the change
* Some more test changes
* Reverting the using statements in tests
* Add a ifdef for .NET 6
* Adding a specific version for NuGet.Frameworks to unblock 6.0 tests
* Revving the version to 1.0.x for .NET 6 release
* Add documentation for the workaround and revert version changes from this PR.