Why?

• how reference .net standard libs in .net framework project?
• dotnet issue

Migration

  1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32:   net462 DD.Database DD.Database DD.Database Library Properties false Properties\GlobalAssemblyInfo.cs Properties\VersionInfo.cs

pros

  1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32:   net462 DD.Database DD.Database DD.Database Library Properties false Properties\GlobalAssemblyInfo.cs Properties\VersionInfo.cs

ability to specify not concrete version

 1: 2: 3:   

package information in one place

 1: 2: 3:   

we don't have to specify all files included

 1: 2: 3: 4: 5: 6: 7: 8:   Properties\GlobalAssemblyInfo.cs Properties\VersionInfo.cs 

easy migrate to .net core

 1: 2: 3:   net462;netstandard2.0 

generate nuget package throw visual studio

 1: 2: 3:   true 

packages in one place

• all packages are located in .nuget folder

automatic generation of assembly info

 1: 2: 3:   false 

specifing not concrete version of package

• what with package doesn't respect semantic versioning?
• System.Data.SqlLite.x64 ver 1.0.106 vs 1.0.76

teamcity and hardcoded paths to bin folder

• buildsteps sometimes contains path to dlls
• after migration dlls goes not to the /bin folder but /bin/{targetFramework}

you have to update visual studio

• minimum version to support all msbuild magic is 15.2
• update of all agents

what with web projects

 1: 2: 3:   PackageReference 
 1: 2: 3: 4:   0.0.5