Getting started is a nightmare for new users.

[replete]

(This may not be the right place for this post, but I have no idea where else to put it)

I really feel like the wider vnext project needs someone to own a global 'Getting started with RC1' manual - perhaps on [docs.aspnet.org], that is directed to from all current documentation areas/packages.

I know a lot is going on with the move to dotnet, but I have literally spent hours and hours and hours trying to make sense of everything. From what I've seen of the milestones, RC2 is months away and therefore this would probably be worthwhile.

It took me hours to realize (as a brand new vnext user as of a week ago):

• RC1-final is best to work with right now
  • because of huge (good) changes across the board undergoing in RC2
  • because RC2 seems months away (which is fine)
• It's easiest to stick with dnx451 or dnx46 native frameworks right now
• AspNetCore.* dependencies use a new namespace for RC2+, and I should be using AspNet.* packages instead
• Packages are managed most easily in Visual Studio via the context menu 'Manage packages'
• Adding the non-standard URL to the package manager in VS was required to get RC2 packages
• Look at code samples in master branches are probably for RC2, better to refer to release* or RC1-* branches
• RC2 packages need a custom package provider setting up
• dotnet replaces dnx, dnvm etc
• dotnet is essential for RC2+
• dotnet is not essential for RC1, can use dnx etc at the time (not clear from package repos)
• dnx46,dnx451 are .NET Native frameworks
• dnxcore50 is RC1* name for .NET Core
• project.json schemas documented had slight differences between RC1, RC2
• The official documentation website shows 'vnext' as the default, which seems to be RC2 related.
• Using dnxcore50 as a framework doesn't seem to work easily because it needs ".NET Native" libraries - how do I make it use these?

I could go on. Instead of making stuff, I've been running around in circles. I know vNext is new, but RC1 should be easier to get going with.

What would clear this up:

• Explain how and why RC1 is what most people should use right now
• Getting started with RC1
• Explain who should use RC2
• Getting started with RC2

If RC2 was ready tomorrow, I wouldn't bother with this post, but it seems months away. Which is fine because the changes are great and clarify so much with this project.

[runxc1]

With RC1 and RC2 being so different what needs to happen is to have a beta between RC1 and RC2 so that people can start using the RC2 bits in an easier fashion and not learn all the dnx commands that will be gone and forgotten in a month. I started using vnext back in the beta1 days and have seen more changes between RC1 and RC2 than between some of the earlier betas...

[replete]

I don't mind the switch of tooling - the huge problem is that what's expected practice in RC1 (latest stable channel) is not obvious due to dev channel RC2 practices, requirements, examples being all over the place.

Most of the problem posts I'm coming across, are people trying to do RC1-like things in RC2 and vice versa. It is hellish.

[svick]

Do you think this still needs improvement? Especially have a look at Migrating from DNX to .NET Core CLI in .Net Core docs and Migrating from ASP.NET 5 RC1 to ASP.NET Core in ASP.NET Core docs.

If you think something still needs an improvement, you should open an issue at the dotnet/core-docs repo or the aspnet/Docs repo.