dotnet / try-convert

Helping .NET developers port their projects to .NET Core!

dotnet/try-convert Issues

try-convert 0.9.4.32202 crashes with: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Could not find or load a specific file. (0x80131621)
Updated 2 months ago7
Why does the program not warn that .net 5 is needed when starting?
Updated 6 months ago
What is correct input of Multiple installs of MSBuild detected please select one
Updated 9 months ago6
Can't use the tool with Supported .NET versions
Updated 9 months ago
Release .NET 6 version to NuGet
Updated a year ago
try-convert crashes with 'Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=6.0.0.0
Updated a year ago2
try-convert crashes with "Could not load file or assembly 'System.Runtime"
Updated a year ago8
try-convert can be smart, add condition when encountering a dll with a different name
Updated a year ago
Crash with System.Runtime not found
Updated a year ago3
Support source control systems with read-only files (Perforce, SVN)
Closed 2 years ago
"Multiple installs of MSBuild detected please select one"
Closed 2 years ago1
try-convert fails when "Multiple installs of MSBuild"
Updated 2 years ago7
Try convert: displays multiple instances , without being able to pick one
Updated 2 years ago6
can not seem to be able to fix this error
Updated 2 years ago4
still trying to find netcore 5 not 6 issue
Closed 2 years ago
Upgrade removes custom Import statements
Updated 2 years ago
Documentation should point out that --ignore-failed-sources could be required
Updated 2 years ago1
Unsupported Project Type (Regression of Issue#156?)
Updated 2 years ago2
Immediate crash on startup (System.Threading.Tasks.Dataflow, Version=6.0.0.0)
Updated 2 years ago3
Not Recognizing UWP as Supported Output Type
Updated 2 years ago
Conversion to net6.0: The target platform must be set to Windows (usually by including '-windows' in the TargetFramework property) when using Windows Forms or WPF
Updated 2 years ago
There appear to be some build issues on recent sdks
Updated 2 years ago
Updating System.ComponentModel.DataAnnotations with NuGet package fails when NuGet unavilable
Closed 2 years ago
try-convert is broken on vs 2022
Updated 2 years ago3
try-convert converting .net 4.7.2 to netstandard2.0 target framework when selecting .NET Core SDK as option
Updated 3 years ago
Error - Sequence contains more than one matching element
Updated 3 years ago
Provide informational messaging when a package used content files or install.ps1
Updated 3 years ago
try-convert error - No OutputType found in the project file
Updated 3 years ago1
ASP.Net project cannot be build with VS2022 after conversion
Updated 3 years ago
"System.UnauthorizedAccessException: Access to the path 'Path"
Updated 3 years ago
``--maui-conversion`` switch should also include an option to try to convert winforms and wpf .NET Framework apps to MAUI.
Updated 3 years ago
Error BC30002 Global.Microsoft.VisualBasic.ApplicationServices .. is not defined after convertion in MYWpfExtension.vb file.
Updated 3 years ago
Set csproj property Deterministic to false if AssemblyVersion in AssemblyInfo.cs has wildcard
Updated 3 years ago1
Remove Skip Attribute on Tests + update CI
Closed 3 years ago
Question about package references while using --keep-current-tfms
Updated 3 years ago
Feature request: convert extensions to vs2022
Updated 3 years ago
add --update argument
Closed 3 years ago1
Try-convert shouldn't edit projects that are already converted
Updated 3 years ago
Try-convert breaks if the --msbuild-path ends with a trailing backslash
Closed 3 years ago1
Error when more than one VS install is present
Closed 3 years ago
Seeing duplicate analyzers after running try-convert
Updated 3 years ago
VB Class Library: Compile errors due to "My." namespace
Closed 3 years ago
Add support for Visual Basic WPF and Visual Basic Unit Test projects
Closed 3 years ago2
Exception converting project 'Sequence contains more than one element'
Closed 3 years ago1
Bring more prominence to messages that can help developers cost/plan for significant code changes
Updated 3 years ago1
i ... should get output from failed conversions... right?
Updated 3 years ago
Allow enabling support for custom imports
Closed 3 years ago2
ProjectStyle misidentified for some older desktop apps
Closed 3 years ago
ApplicationDefinition is missing when migrating from WPF project
Updated 3 years ago
dotnet tool install -g try-convert
Closed 3 years ago1