The identity provider works with ArangoDB but only in .NET Framework, not .NET Core. We ended up abandoning ArangoDB about 1/3 into the project due to some limitations of the platform that I believe may have been resolved by now, but at the time we just couldn't wait. Regarding IdentityServer4, I just setup an authentication end point that services desktop, mobile (cordova and native) and MVC + Angular using IdentityServer4. It took a while and there a lot of gotchas that aren't documented. If you're pressed for time, I'd almost say it might be more worth it to stick with IdentityServer3. We barreled through and got version 4 running, but it's not as clean a solution as I'd like; but I'm -really- picky so it could just be me. Our identity server implementation uses AspNet Identity 3 over .NET Framework. At the time, .NET Core just wasn't an option with the state it was in and I built a conversion for AspNet Identity 3 for Framework since the default one is for Core. Works great! You should be able to use the ArangoDB AspNet Identity provider with some minor upgrades. You can find it here https://github.com/actias/ArangoDB.AspNet.Identity . At some point I want to upgrade everything, but my time is sucked up right now by client projects :(

Personally, I'm not a fan of any of them as is. What I ended up doing was taking the design patterns from Material Design and creating my own version of Bootstrap. It runs great, is compatible with the huge amount of controls out there but has all of the slickness of Material Design. The really nice thing is that it's super easy to customize and tailor to different projects and clients with just a few variable changes.

Denny has the absolute right answer. I also wanted to add, however, don't use $scope if you don't need. It adds overhead to your app that you don't need. Try the following: var self = this; self .settings = { }; self .post_social = function () { var ref = new Firebase(path); ref.update({ twitter: self .settings.twitter || '' , facebook: self .settings.facebook || '' , google: self .settings.google || '' }); toaster.pop( 'success' , "System" , "Settings saved!" ); }; Also, I highly recommend putting your toaster popups in a service. It lets you swap alert services in and out easily. It doesn't seem like a big thing, but we had a customer want a different style of messages and we were able to swap out the plugin and change the alertService and not affect any other areas of our code.

You have to remember that Angular 2 is bleeding edge at the moment. Most places that use C# and Java are going to be mid-enterprise scale businesses that can't risk using anything that new. Also, in my case, the business didn't know there was anything better. I spent the last year converting our tech stack to WebApi and Angular. Sometimes you have to be the driver for change.

I tend to include bootstrap for components and then skin the heck out of it. I'm not a huge fan of their stylings but if offers a really nice starting point.

In my area (LA), I've seen a few postings like that, however, they usually don't pay well and are few and far between. Most job postings I see what some sort of full-stack experience and/or knowledge of HTML/CSS.

How are your fundamentals overall? That's what really matters. A lot of times people get caught up developing via Frameworks and Libraries without going back to the core of what they're developing; instead relying on the Frameworks to obfuscate that for them. It was a huge problem with JQuery and I'm starting to see history repeat itself as more and more Frameworks are released. Before you delve into another Framework, make sure that you're core basics are rock solid. Look at the core fundamentals of JS, HTML and CSS. Develop a solid understanding of programming principles in general: proper code and project structures, creating simple readable code for reuse, etc. Once you've got that down, focus on the core technologies in your stack that are LEAST likely to change. Node, Express, etc are a good place to start. You may even want to look into other server-side languages such as C#, PHP and Java. This will be with you a much longer time than say React, Angular, Ember, and on. These provide the foundation for what you're building and a strong knowledge of the server platform will serve you regardless of your front-end technology. After that, then focus on your front-end stack. Front-end stacks rotate a lot and they're constantly iterating, however, if you've gone through and made sure you're rock solid everywhere else, bouncing between them becomes much easier and intuitive.

So. The 3 project types are thus: Web Application - This is the classic .NET 4.6.1 template. It's been around for a while but you can't use NPM very easily with this project type. ASP.NET Core (.NET Framework) - This is still .NET 4.6.1, but it uses the new ASP.NET 5 setup. A nice intermediary bridge between .NET Framework and .NET Core. ASP.NET Core (.NET Core) - This is the same as the previous project, but with everything initially setup for .NET Core. Out of the 3, I'd choose the first or second; probably the second. .NET Core is still really new and there isn't a tonne of documentation. The second option is a little more flexible and lets you use NPM, Bower, etc. within VS easily. So when you get to the project template selection, that's all they are, templates. They are just projects with certain pages, controllers, etc created for you. At their core they're all the same; just showing off different aspects of the platform. I usually role with the empty project, but I've been doing this for years. Also, you'll be given the option to host in Azure. This is up to you. Everything of my generally ends up there at some point, but you don't have to use it. When your project loads and you click the debug button (or press F5), VS will launch a mini version of IIS called IIS Express to run your website. It runs locally and within its own memory space. When you stop debugging, it stops IIS Express as well; though you can changes this in the options. Creating your own folder structure is done through the GUI for the most part UNLESS you use the ASP.NET Core project types. These project types will pick up folder and file changes made outside of the IDE, so feel free to BASH/PowerShell/Console it up. Nuget packages are generally for .NET libraries only; like NPM is for JavaScript, etc. You should use them, but you don't need to use them for any of your client side stuff. If it's .NET use Nuget; if it's client-side/javascript stuff, go NPM. You can use whatever database you like. There are drivers for just about every major database out there. SQL is generally included by default via EntityFramework. If you want to use MongoDB type: "Install-Package MongoDB.Driver" in your package manager console.

Ahh. Right. No PM. Feel free to private message me on Twitter at @HousePandas. I'll try and work up a lengthier answer when I get back to my PC. I'm mobile at the moment. 😁

C#, .NET, etc. are my native languages and I literally build ASP.NET services and solutions everyday as part of my career. Hopefully, I can provide some insight. First, C#, .NET and ASP.NET while related are not all the same thing: C# is a programming language that's generally associated with .NET but can be used elsewhere. That's all. It's just the language .NET is a Framework . It's a set of API's, classes, etc. that all come together to make programming easier. In general, you write C# code (or VB, F#, etc.) utilizing the .NET Framework and that all gets compiled during build or run time for execution by the .NET compiler. With the latest release of .NET (Core) you can either use the default compiler Roselyn, use a third party compiler or roll your own. There's a lot more to it than that, but I could write pages on just the compilation stuff alone and you really don't need it to get started. ASP.NET is a subset of the .NET Framework specifically geared towards web development. Initially it consisted of what Microsoft called WebForms which were Microsoft's way of pulling traditional application developers over to web development. I personally don't work with WebForms anymore as they are too reliant on session and ViewState and for the most part, most people are moving on to MVC. MVC and WebApi are the kids on the block and with .NET Core, they have been merged. MVC tacked rending Html views as well as returning data, whereas WebApi was geared specifically to returning data via REST generally via XML or JSON although you have full access to the HttpContext so you could theoretically can return whatever you want. Ok, so. With that wall of text out of the way, what you're looking to do is actually pretty simple. Crack open Visual Studio (preferably 2015 with Update 2 or 3 installed) and create a new ASP.NET Web Application or ASP.NET Core Web Application. I'd personally say go with the first for the time being even though ASP.NET Core is the new hotness because Core was literally just released and there isn't a ton of documentation on it. StackOverflow, on the other hand, is full of questions about ASP.NET. Once you've selected your project type, go ahead and select the WebApi template. This will create a project template with everything you need to get started with WebApi. There will be a controllers folder where you'll put your data controllers, a models folder for your models, etc. These controllers are going to be your server side code. By default, they'll all be prefixed by '/API' when you call them. Now, to add a client, you have one of two options: You can dump your files into the same project and have everything there. You can create a new empty web project and put your files there Regardless of where you put our client code, you'll need to make a note of the port number that the web api project runs under (usually http://localhost:SomePortNumber ) and have your Angular project point to that for data. That's a REALLY high level overview of how to get started and I'm sure you have more questions but a Hashnode post is a very limited area for a tutorial :) Check out this tutorial: http://www.asp.net/web-api/overview/getting-started-with-aspnet-web-api/build-a-single-page-application-spa-with-aspnet-web-api-and-angularjs Also, feel free to hit me up if you need help or a starter project to get going with as an example. I'm more than happy to help. I love C#. It's super powerful, really elegant and the .NET Framework has a lot to offer, but I can understand how difficult it can be coming from another language. Once you get past the initial hurdles, it's all pretty much downhill for a while.