Thanks Tim, this course has been invaluable to see your process and I have learnt a great deal so far. Finally caught up and looking forward to the next one!
That is not something I have pursued, nor do I intend to pursue. While I would have a ton of fun working for Microsoft, I prefer to teach and do so on my own so I am not constrained in what I teach.
Wouldn’t you use epics only when there are more abstract layers above you (managers and their managers), so they could use epics to discuss the work, without having to zoom in to all the little details? I agree with you, for a one man project they only add complexity
Hi tim! I have a question, on a web app (front end) you are calling an api (backend, separate solutions). After they log in, with ajax (post to Login method on api), how do you redirect to the main view of the application in the succes () method with the token the api gave you?
Hi Tim I notice at 23:35 we are using prerelease NuGet Packages (3.1.0 preview1 Microsoft packages and 5.0.0-rc4 Swashbuckle packages). Maybe Phase 2 is a good time to upgrade our NuGet Packages to current release packages? Thanks for your videos, I'm really getting a lot out of this course.
Good catch. I just added this as a work item in our DevOps board. It is work item #24 and I added your comment to the description. Thanks for pointing it out.
Hi Tim, when you get to no 6 "Deploy the desktop app..." please mention something about code signing certificate (Authenticode) and how to implement that with ClickOnce in order to avoid the Windows SmartScreen Filter when running the installed WPF app for the first time. Still trying to get my head around that.
@@IAmTimCorey With .NetCore, isn't ClickOnce gone? From what I've read, the answer from Microsoft is to utilize UWP to compile your project into MSIX packages.
It depends on what part you are referring to. Azure DevOps does git hosting. That part is practically identical to GitHub. It also does issue management (Boards), which is a bit different than GitHub but there are similar concepts. Azure DevOps has a CI/CD process that is similar but different to GitHub Actions. I do not believe GitHub does package hosting like Azure DevOps Artifacts. I also don't believe GitHub does test plans. They both have wiki ability. At the end of the day, Microsoft is pulling GitHub closer to Azure DevOps as far as functionality.
