3 ms·
More importantly, if the default is to depend heavily on conventions, MS should have had a big glaring button / warning / notification in the Introduction page,
by kumarvvr 5y ago
More importantly, if the default is to depend heavily on conventions, MS should have had a big glaring button / warning / notification in the Introduction page, which summarizes all the conventions used. Would have saved many beginners a lot of time.
I am an experienced programmer and was very frustrated having to search for all the conventions used in the framework.
- andix 5y agoThat always drove me nuts. You need to learn all those conventions from the examples. And then you always got the strangest surprises and still needed to use attribute based routing.
- Rapzid 5y agoSomething that drives me crazy about the current ASP.NET Core documentation is that it is overly example based. I wish there were more comprehensive coverage of the subsystems.
- andix 5y agoTotally. Most of the time I don’t even check the docs, I go straight away to the source code on GitHub.
- oaiey 5y agoTrue story. We developers are an interesting species. Documentation is for us never sufficient because we want to know how the sausage is done down to the if statement. And for good reasons.
- SketchySeaBeast 5y agoAbsolutely. I've wasted hours doing things that, if I'd been shown the way Microsoft wanted me to do them, I'd solve in 10 minutes, but instead I need to spend a ton of time trying to figure out why the new variable on my model isn't binding correctly because I didn't realize they need to be properties.
- deleted 5y ago[deleted]