[rails]

Old, and/or outdated documentation is my top struggle. With all these different versions of .net framework/core, asp.net with and without core, entity framework and all the other stuff in the ecosystem you always have to check if the documentation fits the .net (framework/core) version you are currently using.

On the first look it seems like there didn't change a lot between the old net framework and net core 1,2,3 and now .net 5 but once you get into the details each time it is a changed world.

[kirillzubovsky]

Oh yeah, I can relate. There is a ton of change between version and very often new plugins don't support old versions at all. Would sticking to one, say most progressive implementation (Net 5 at this point) help you feel more confident that the job can be done?

Although at this point Net 5 isn't going to be documented because it's so new, and next year they will release Net 6, which will be the actual long-term support version.... this is how their mess with docs happens in the first place.