4 ms·
I just took a brief look at the tutorial and it would still get me caught up on the same issues. The class library created by `dotnet new -t lib` had a differen
by dvcc 10y ago
I just took a brief look at the tutorial and it would still get me caught up on the same issues. The class library created by `dotnet new -t lib` had a different target framework than most tutorials, and short of just copying and pasting in a whole new project.json file (which changes the target framework and imports two more) I am out of luck. It's pretty confusing and tiring!
- jongalloway2 10y agoIn Visual Studio 2017 RC it's "File / New / xUnit Test Project" and you're all set. I think some of the docs and presentations have gone a little far to the everything-commandline direction. If you're an experienced .NET dev, you're probably going to be a lot more comfortable with Visual Studio at least to get started. Much easier to start with some working code and break it / play with it than to start at the command line and a project file... again, if you're an experienced .NET dev who's used to Visual Studio. I will agree with your main point that it is confusing and that it should be easier. Those are actually some of the top things listed on the roadmap.
- dvcc 10y agoAdmittedly, I would be much better off using VS to create the project/install packages/etc but I thought I no longer needed to, hell they were providing yeoman generators for .NET Core (but they weren't always updated at the same time as a new release)!