ParseProject doesn't support new csproj-format
See original GitHub issueParseProject doesn’t support new csproj
-format. One essential thing missing is support for multiple target frameworks.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:28 (17 by maintainers)
Top Results From Across the Web
c# - How to parse in a dotnet sdk csproj project file?
I'm trying to load a csproj file using Project from Microsoft. ... BuildEngine is still unhappy about the new csproj format, though in...
Read more >Upgrading an existing .NET project files to the lean new ...
In Visual Studio 2017 and .NET Core 2 (and beyond) the csproj format is MUCH MUCH leaner. There's a lot of smart defaults,...
Read more >Old csproj to new csproj: Visual Studio 2017 upgrade guide
NET Core went from the project.json to csproj file format, and the new csproj format is leaner, easier to read, and adds new...
Read more >Converting projects to new csproj - Niche Software
After some intensive research, I discovered that the classic .csproj file format automatically restores NuGet packages as a part of the build.
Read more >Moving to SDK-Style projects and package references in ...
The new SDK style csproj only supports the new packagereference style package formats, which is very good, but we need to have these ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@wexman Parsing MSBuild project files is actually very complicated. Also note that project files are more a function of MSBuild than the C# language. Between the different types of projects, different SDKs and project file formats, and different MSBuild tasks and targets, there’s a lot to them under the hood. There’s also a difference between “parsing” the files to determine the structure of the file (as Cake does) and “evaluating” them to figure out how MSBuild will interpret them (as @matkoch suggests).
Can we please leave the attitude out of this, especially without understanding all the facets of the problem. We’re all volunteers here.
So now with version 0.26.0 of cake, the incubator addin (1.7.2) doesn’t work anymore (because it was built against cake.core 0.22.0). How am I supposed to get the version info I need now? Can you please stop breaking things between every 2nd release?