Open knaepel opened 3 years ago
@knaepel our build pipeline expects a .csproj that contains an assemblyinfo.cs. But sure, moving to .net standard would be awesome!
@MEichhoff do you think Helke can extend our script to support the new project style? That would be great.
From my point of view she should be able to do it.
This project references SmartFormat.NET. The package is compatible with .NET Standard 2.0. Why not migrate the project to .NET Standard 2.0 to make it easier to move to .NET Core in the future. Also, the dotnet cli could then be used and the csproj file will be more concise. https://docs.microsoft.com/en-us/dotnet/standard/net-standard