CsprojToVs2017
CsprojToVs2017 copied to clipboard
hvanbakel
Tooling for converting pre 2017 project to the new Visual Studio 2017 format.
Hi, I run the following command : dotnet-migrate-2019 migrate "path/to/mysolution/mysolution.sln" I get the following message : Impossible to load file or assembly ''Microsoft.Extensions.Logging.Abstractions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'". How can I solve...
Siging of an assembly can also be done using assembly attributes in the assemblyinfo.cs [assembly: AssemblyDelaySign(true)] [assembly: AssemblyKeyFile(@"..\..\PublicKey.snk")] With this pull request these attributes get also transformed
A default `AssemblyInfo.cs` has non-empty assembly options `AssemblyTitle`, `AssemblyProduct` and `AssemblyCopyright`. When converting projects, I would like to avoid these options being copied to the new csproj. How about a...
I've seen it in a few projects now and I believe it is something that was put in by VS2010 templates to indicate the Visual Studio version and probably others....
Following construct: `bin\$(Configuration)\.xml` should be changed to `true` It's same but cleaner
So-called _eager_ mode, implement transformations that do unsafe but effective, highly opinionated transforms. A feature, thus not a blocker for next version release. - [x] Migrate to `portable` DebugType -...
I run dotnet-migrate-2017 from the solution root of SDK projects: dotnet-migrate-2017 migrate The tool discovered the projects and start to backup, process the project file and showed many info W011...
Split off from #165 PCL profiles to .NET Standard conversion can be 2.x scheduled. There is about 12 supported PCL profiles (of approximately 80), but they are the most common....
Some projects (like [ConfuserEx](https://github.com/yck1509/ConfuserEx)) specify only conditional `TargetFrameworkVersion`s: ```xml v4.0 v4.5 ``` It works in legacy project system, but fails sanity check in CPS, as `TargetFrameworkIdentifier` doesn't get defined by...