Sunday, November 25, 2018
This past week I got an Angular/.NET Core 2 test app to deploy to Azure via Visual Studio 2017. I used the built-in SPA template and felt dirty doing it, but it looked like that's exactly what I needed. Previously, I split up the app into two projects. One for Angular and one for the Web API, but it looks like I don't necessarily need to do this just yet. There won't be a time where I'm going to publish both separately, so it's easier for me to deploy from Visual Studio to Azure without much configuration using the SPA template. Working with Angular and .NET Core 2 for personal projects is new territory for me, so I'm trying to keep things as simple as possible and on a need-to-know basis.
I'm hosting my source code there. They have a decent free plan for private repositories and they include some extra stuff to play around with. Azure DevOps is essentially TFS rebranded for the web (at least that's what I've heard). You get source code hosting, CI/CD, kanban boards, and probably a bunch of other stuff I'll never use. It felt like using Github, but easier, though using Github isn't exactly difficult. Anyways, my code is there and I started trying to set up what they call a Pipeline, which is a continuous intetgration pipeline. I tried and then stopped when it didn't work easily. I need to do more research on it, so I'm going to avoid it for now. It's not a must have, it's a nice to have.
Well, now that I have my code set up and know that I can easily deploy it to Azure, I just need to set up my local and production configurations for my development environment as I go. I'm currently reading up on ASP.NET Identity and trying to set it up to work with MongoDB. It's definitely possible and I'll probably have to do it myself, because there doesn't seem to be a solid NuGet package for that.
I got my basic workflow ready, now I'm just setting up the rest of the infrastructure. In this case, I'm trying to set up my user membership system.