4 Answer(s)
-
0
Hi,
We dont have an Angular2 version yet but we are planning on it. It will be released in a few (two or three) months.
-
0
Great stuff guys but. Can you recommend us an interim step before we can use Angular 2? Should we go with ng-upgrade? <a class="postlink" href="https://scotch.io/tutorials/seamless-ways-to-upgrade-angular-1-x-to-angular-2">https://scotch.io/tutorials/seamless-wa ... -angular-2</a> <a class="postlink" href="http://blog.rangle.io/upgrade-your-application-to-angular-2-with-ng-upgrade/">http://blog.rangle.io/upgrade-your-appl ... g-upgrade/</a>
Best Regards, Alistair
-
0
Hi Alistar, I would like to give my two cents on Angular2 and aspnetboilerplate. I hope this helps someone who is on the fence about converting from AngularJS that boilerplate comes with. Again this is just my humble opinion.
I started to convert the software over to angular 2 and ran into waaay too many problems. Angular 2 itself is a half baked mess with breaking changes and beta modules from vendors. The compiled components are huge in file size which forces you to lazy load components if the app is going to have any size to it (large solution). This sounded great until I found out WebPack doesn't support Lazy Loading yet. Breaks the build. That was the final straw for me as I kept hitting walls like this over the 10 days I spent on it. 10 days of wrapping my head around Angular2, fixing all the typescript dependencies in Visual Studio, getting my build scripts just right, building components and so on.
Personally I think I will wait until angular 2 gets all the kinks worked out and even then I don't consider it a good fit for ASP.Net MVC or Core unless you are using the fore mentioned as a middle tier and DAL only. It just doesn't make sense. Razor views are no longer useable and it defeats the purpose of MVC in ASP.Net altogether. I did see a post where you could run the template of a component through the controller to use Razor Views, but I couldn't get it to work. WebPack didn't like that either. At this point I wasn't about to convert over to Gulp and have to start all over.
I think Angular 1 is a good fit and makes sense for ASP MVC. as of this writing.
I am certain moving forward the kinks will get worked out and clever developers will come up with usable patterns for MVC and Core, but as of right now, I have chosen to stay with AngularJs
Paul
-
0
Thank you for sharing your experinces and ideas. Angular2 is now is final release but still it's cli is being developed and some other related projects are not finished. I think it will be more mature in 2017.
