4 ms·

Still project.json tho, they said they will remove it in future. Too bad not now.

by romanovcode 10y ago

bad_user 10y ago
And replace it with what? Source?
- quaffapint 10y ago
  This was a discussion on the github issues list. The plan is to put things back in msbuild. The question is what will they still leave in json format - possibly a nuget.json.
- pionar 10y ago
  Going back to .csproj files, but improving those. From [0]: "Question: project.json is going away? Sadface What were the things we liked? It was small, contained NuGet information, and could be edited by hand. Damian does not want to lose any of those benefits, and that is why they are working in several steps to complete this migration. Additionally, the team is building tooling at the command line so that you don’t have to work with the project file directly. Consider a possible npm-like command like “dotnet install json.net –save” to add a NuGet package to your project. There will be first class commands like this available. The new MSBuild will not have a complete list of every file, so that should reduce the size of the build file. It will still be XML, but the team is committed to making that experience better for all .NET projects. This will be an enhanced MSBuild that has all of the best parts of project.json" [0]https://blogs.msdn.microsoft.com/webdev/2016/05/11/notes-from-the-asp-net-community-standup-may-10-2016/ https://blogs.msdn.microsoft.com/webdev/2016/05/11/notes-fro...
  - bad_user 10y ago
    Oh man. It's not like I liked the idea of project.json, because it clearly has problems, like being rigid / not extensible. But I was hoping for a migration towards something like Maven / Gradle / SBT / Leiningen. And extending MSBuild is not a solution towards that. And it's really not about MSBuild being XML. No, this is about MSBuild being too freaking manual, in an Ant/Makefile fashion. Maven is declarative, it depends on established conventions with overridable settings and has plugins. And it takes care of everything, from dependency management, building, deployment, testing, continuous integration, metrics, etc, things for which people normally use Visual Studio or TFS or other third-party and usually incomplete, bloated and expensive solutions. And sure, providing command line tools that modify MSBuild is nice. But you know, the fact that you need a tool to modify MSBuild highlights a big problem. And no, it's not because of the XML.
- vyrotek 10y ago
  Q&A from ASP.NET Live - https://www.youtube.com/watch?v=P9HqMZviaMg&t=2097 https://www.youtube.com/watch?v=P9HqMZviaMg&t=2097
- WorldMaker 10y ago
  The proposal, as I understand it, would be to push NuGet specific stuff to something like a nuget.json file and what (little) remains of the project.json after that into the xproj file and "back" into the MSBuild/XBuild world. (The proposal would not add the individual file contents of the project into the xproj, however.) This was an article highlighting the community discussions on this: https://wildermuth.com/2016/05/12/The-Future-of-project-json-in-ASP-NET-Core https://wildermuth.com/2016/05/12/The-Future-of-project-json...
- anton_gogolev 10y ago
  https://github.com/aspnet/Home/issues/1433 https://github.com/aspnet/Home/issues/1433

Still project.json tho, they said they will remove it in future. Too bad not now.

bad_user 10y ago

And replace it with what? Source?

quaffapint 10y ago
This was a discussion on the github issues list. The plan is to put things back in msbuild. The question is what will they still leave in json format - possibly a nuget.json.
pionar 10y ago
Going back to .csproj files, but improving those. From [0]: "Question: project.json is going away? Sadface What were the things we liked? It was small, contained NuGet information, and could be edited by hand. Damian does not want to lose any of those benefits, and that is why they are working in several steps to complete this migration. Additionally, the team is building tooling at the command line so that you don’t have to work with the project file directly. Consider a possible npm-like command like “dotnet install json.net –save” to add a NuGet package to your project. There will be first class commands like this available. The new MSBuild will not have a complete list of every file, so that should reduce the size of the build file. It will still be XML, but the team is committed to making that experience better for all .NET projects. This will be an enhanced MSBuild that has all of the best parts of project.json" [0]https://blogs.msdn.microsoft.com/webdev/2016/05/11/notes-from-the-asp-net-community-standup-may-10-2016/ https://blogs.msdn.microsoft.com/webdev/2016/05/11/notes-fro...
- bad_user 10y ago
  Oh man. It's not like I liked the idea of project.json, because it clearly has problems, like being rigid / not extensible. But I was hoping for a migration towards something like Maven / Gradle / SBT / Leiningen. And extending MSBuild is not a solution towards that. And it's really not about MSBuild being XML. No, this is about MSBuild being too freaking manual, in an Ant/Makefile fashion. Maven is declarative, it depends on established conventions with overridable settings and has plugins. And it takes care of everything, from dependency management, building, deployment, testing, continuous integration, metrics, etc, things for which people normally use Visual Studio or TFS or other third-party and usually incomplete, bloated and expensive solutions. And sure, providing command line tools that modify MSBuild is nice. But you know, the fact that you need a tool to modify MSBuild highlights a big problem. And no, it's not because of the XML.
vyrotek 10y ago
Q&A from ASP.NET Live - https://www.youtube.com/watch?v=P9HqMZviaMg&t=2097 https://www.youtube.com/watch?v=P9HqMZviaMg&t=2097
WorldMaker 10y ago
The proposal, as I understand it, would be to push NuGet specific stuff to something like a nuget.json file and what (little) remains of the project.json after that into the xproj file and "back" into the MSBuild/XBuild world. (The proposal would not add the individual file contents of the project into the xproj, however.) This was an article highlighting the community discussions on this: https://wildermuth.com/2016/05/12/The-Future-of-project-json-in-ASP-NET-Core https://wildermuth.com/2016/05/12/The-Future-of-project-json...
anton_gogolev 10y ago
https://github.com/aspnet/Home/issues/1433 https://github.com/aspnet/Home/issues/1433