4 ms·

The CLI is new to .NET Core, and .NET Framework/.NET Core are practically different platforms. Despite that, I don't get why I should struggle that much trying

by dvcc 10y ago

The CLI is new to .NET Core, and .NET Framework/.NET Core are practically different platforms. Despite that, I don't get why I should struggle that much trying to get a simple empty project going.

justabystander 10y ago
I don't know if you've noticed this or not, but, while the .NET Core has hit RTM, the tooling is always marked as being a "Preview" for good reason. (https://www.microsoft.com/net/core https://www.microsoft.com/net/core) They've got a solid idea on how to work .NET Core, the desktop .NET framework and .NET Standard as the bridge, but the tooling for .NET Core work is undergoing frequent revisions.
nightski 10y ago
It's really not that complicated. You described pretty much all the trouble in less than a paragraph. It sounded like 10 minutes of fiddling around. For creating a cross platform library that just works it's pretty painless. Have you tried java/maven? Or webpack? Or god forbid cross platform C++? Your problem seems to be focused on the fact that command line interfaces are not discoverable. This is true of all command line interfaces. Linux/Unix has many utilities that are quite foreign at first. But once you learn the interface (and in this case it is quite simple) you can accomplish things with quite a bit of efficiency.
- dvcc 10y ago
  I don't know, I don't think my main problem was with the CLI rather how hard it was to just get something small going. In contrast, node takes all of 5 seconds to setup a small library, install dependencies, clearly list required engine, etc. Is it perfect, no way; however, it isn't very complicated either. I don't think I'm totally alone with that sentiment either. .NET Core was a project that had pretty high expectations from the beginning, a cross-platform, sane and simpler .NET development platform (C#/F# too!).

4 ms·

The CLI is new to .NET Core, and .NET Framework/.NET Core are practically different platforms. Despite that, I don't get why I should struggle that much trying

by dvcc 10y ago

The CLI is new to .NET Core, and .NET Framework/.NET Core are practically different platforms. Despite that, I don't get why I should struggle that much trying to get a simple empty project going.

justabystander 10y ago
I don't know if you've noticed this or not, but, while the .NET Core has hit RTM, the tooling is always marked as being a "Preview" for good reason. (https://www.microsoft.com/net/core https://www.microsoft.com/net/core) They've got a solid idea on how to work .NET Core, the desktop .NET framework and .NET Standard as the bridge, but the tooling for .NET Core work is undergoing frequent revisions.
nightski 10y ago
It's really not that complicated. You described pretty much all the trouble in less than a paragraph. It sounded like 10 minutes of fiddling around. For creating a cross platform library that just works it's pretty painless. Have you tried java/maven? Or webpack? Or god forbid cross platform C++? Your problem seems to be focused on the fact that command line interfaces are not discoverable. This is true of all command line interfaces. Linux/Unix has many utilities that are quite foreign at first. But once you learn the interface (and in this case it is quite simple) you can accomplish things with quite a bit of efficiency.
- dvcc 10y ago
  I don't know, I don't think my main problem was with the CLI rather how hard it was to just get something small going. In contrast, node takes all of 5 seconds to setup a small library, install dependencies, clearly list required engine, etc. Is it perfect, no way; however, it isn't very complicated either. I don't think I'm totally alone with that sentiment either. .NET Core was a project that had pretty high expectations from the beginning, a cross-platform, sane and simpler .NET development platform (C#/F# too!).