Upon starting the project, I knew I wanted to use Angular2, but wasn’t so sure about TypeScript. I’d heard a lot about the tool, but didn’t really see any practical reason to use it over regular plain old JavaScript. I wanted to try the new ASP.NET, which combines MVC and Web API.Īlso, I develop on a MacBook Pro in Parallels and because ASP.NET Core is cross platform, the idea of native development in OS X without having to spin up a Windows VM was enticing. In this Angular2 tutorial, I’ll reveal the problems faced and lessons learned along the way so you are better positioned to have success with this exciting new technology. There is always risk associated with using new technologies on a project – lack of up-to-date documentation, project configuration problems, and unforeseen bugs. Recently, I started a new project and had the opportunity to test out the Angular2 framework. I’ve been wanting to test out a number of new technologies ASP.NET 5 ( now ASP.NET Core 1.0), Angular2, TypeScript, and JSPM, to name a few. This fast-paced change has created gaps in documentation, making it difficult for busy developers to stay up-to-date with the latest version of the framework. Much of the information has quickly become outdated as the API continues to evolve and mature. A lot has been written about Angular2 over the past year.
0 kommentar(er)
