Building Web APIs Part1

[@KennyomarGarcia]

That Scaffold command is such a beautiful thing. Thanks Chris! 😀👍

[@mmontelaegre]

Maybe you could put the text from the notepad to install the packages and create the model in the video description section above

[@alberthoekstra]

Can’t wait for the more advanced ones! Great video

[@alberthoekstra]

Yea, I know what you're saying. Like in this video, 'just to make things easier' he disabled HTTPS, while HTTPS is almost mandatory these days...

[@Thisdudemakesshorts]

So this was really cool thanks.. But how do you trigger a stored procedure if a simple CRUD operation wont cut it? (If you needed a join for example)

[@you0neville0tube]

those model validation if statements are implicit in 2.1

[@suyulmaz4]

great intro, hope to see more advanced staff soon

[@robl4836]

That line getting the connection string out of the config file does not work. Hard-coding the connection string in the UseSqlServer("myconnectionstring") works

[@nidavelliir]

Check if the connection string format is the correct one

[@liorocker1]

I need more of this :)

[@SoyUnEmilio]

It would be great an explample of a reactive web api

[@rahulhadgal]

Chris, Robert, use your Chinook Database and AutoAPI from github.com/proinfocus/AutoAPI. It will take just a setting up of project and connection string to accomplish the exact same thing you have done in this video. Please try out and let me know your opinion and suggestions.

[@niclorenzen3371]

26:13 Bad Request is a 400 and 404 is not found. Great video nonetheless!

[@ChrisWoodruff]

Nice catch... I made a few blunders during the talk.

[@dromar853]

Hey, you didn't put a link for the sample database in :(

[@joeruder]

Links are in the third episode: channel9.msdn.com/Shows/Visual-Studio-Toolbox/Building-Web-APIs-Part-3

[@2Fast4Mellow]

90 degrees at the end of November? Are you guys recording in Hawaii?

[@ChrisWoodruff]

Recorded back in August actually during the forest fires in WA and CA.

[@Zapanath]

i use Insomnia instead of Postman now. Insomnia has a much simpler UI

[@precogtyrant]

its good, especially with graphql support but is buggy as hell. Randomly stops working and once it crashes, it won't open again unlesss I reinstall.

[@RonaldZaZ]

It looks like Robert has a total lack of interest. Very passive.

[@vatansoni6439]

Packages to Install: 9:45

[@AhmedMagdy-AuthorizationDenied]

where is the rest of the episodes ??

[@ChrisWoodruff]

Here is the second episode. kzbin.info/www/bejne/hWSkp4Foh9dkq6s

[@Mahamad1231]

just search for part 2 and 3

[@root317]

I get a solution with 0 projects.. pls help!

[@ChrisWoodruff]

Did you create a new ASP.NET Core 2.1 project with the Web API option? What version of VS are you using?

[@joeruder]

@@ChrisWoodruff -- I hate it when a author replies to a 'pls help' question only to be ignored. Thanks for the great video and for responding to questions Chris.

[@stevenkjames]

cool

[@zurvey]

I'm just amazed at how Microsoft seems absolutely oblivious of the growing functional programming trend, especially for new projects. And the irony is Microsoft currently has the smartest functional language on the planet, F#, with a substantial head start on everything else. Again and again these videos don't even mention F# much less make a token effort at using this "first class language." At the moment, F# is literally the *only* FP that can build native apps, APIs, web apps, etc. By the time Microsoft wakes up to its functional programming advantage, it will have squandered its lead and something like Facebook's ReasonML will be the industry standard.

[@you0neville0tube]

F# is being developed as well... i have also seen f# videos

[@ShawnShaddock]

Chris Woodruff you are wrong about putting business logic in your Repository. Business logic belongs in your services. Repositories are obsolete if your using NoSQL, but if you must make a Repository, it's isolated responsibility is to get and persist data, not enforce business rules.

[@niclorenzen3371]

Shawn Shaddock I’ve learned through DDD business logic should reside in the domain entities aka models. Services are just for orchestration between models/entities and application services

[@ChrisWoodruff]

Shawn -- I totally agree and stay tuned for the third episode in the series. I break out my domain and data logic into their own projects.

[@ShawnShaddock]

@@niclorenzen3371 I've tried both approaches extensively over my last 12 years of .NET development. I've found that the teams I've worked with work better with a clean separation of data and logic. This is especially true in the current environment where logic does not travel with the data. You are sending an object over the wire as JSON, but that domain logic does not go with it.