So been coding .net since 2013. I have built a lot of cools apps. Honestly I find mvc awesome. But I have always used razor.
Of recent I been going for interviews and all I am hearing is ooh you dont know angular, getting to feel like Razor is a wrong thing to use for front end.
By the way if I have a project that already used razor has front end. Can I add up new views using angular (I mean can I still install angular on an existing project with template)
By the way if I have a project that already used razor has front end. Can I add up new views using angular (I mean can I still install angular on an existing project with template)
This question has been answered in your previous threads.
I have cursory experience with Angular and only built proof of concepts when trying to decide on a client UI framework. My investigation indicated Angular is better build from scratch. I could be wrong but went with React after building a few Angular and
React demos.
I recommend visiting an Angular support site if you have specific question about Angular. I also recommend that you go through a few Angular tutorials to get a better understanding.
there are a class of application that mvc / razor makes sense for. But the closer the web application is to a desktop application replacement, the less its a match. If the web application will require a lot of javascript to implement the UI elements, and
effects, the more complex it is to write with a combination of server render logic and client render logic.
also there is a current trend to move to progressive apps, which you need to code in javascript. Once you start code the web application is client code you want a framework, for there are three popular frameworks, react, angular and vue.
all three have similar concepts, client routing, view/component engine, and a store. all three use the node build chain, and have a node cli for creating, testing and developing projects. while angular requires typescript (which is optional for the other
two), you will need to know modern javascript, with arrow functions, promises, async/await, functional programming, etc.
if you plan on a long career in web application development, you will need to follow the trends. you should at least learn one of the frameworks.
Member
66 Points
237 Posts
Is wrong to use razor for front end
Nov 21, 2019 03:42 PM|InspiredJide|LINK
Hello Guys,
So been coding .net since 2013. I have built a lot of cools apps. Honestly I find mvc awesome. But I have always used razor.
Of recent I been going for interviews and all I am hearing is ooh you dont know angular, getting to feel like Razor is a wrong thing to use for front end.
By the way if I have a project that already used razor has front end. Can I add up new views using angular (I mean can I still install angular on an existing project with template)
Models - COntrollers and Razor views.
Thanks alot.
All-Star
45061 Points
19454 Posts
Re: Is wrong to use razor for front end
Nov 21, 2019 03:53 PM|mgebhard|LINK
This question has been answered in your previous threads.
https://forums.asp.net/p/2161675/6285514.aspx?Re+vuejs+vs+angular+which+do+I+learn
I recommend React if for integrating client side UI rendering.
https://reactjs.org/docs/add-react-to-a-website.html
I have cursory experience with Angular and only built proof of concepts when trying to decide on a client UI framework. My investigation indicated Angular is better build from scratch. I could be wrong but went with React after building a few Angular and React demos.
I recommend visiting an Angular support site if you have specific question about Angular. I also recommend that you go through a few Angular tutorials to get a better understanding.
All-Star
54284 Points
13661 Posts
Re: Is wrong to use razor for front end
Nov 21, 2019 04:44 PM|bruce (sqlwork.com)|LINK
there are a class of application that mvc / razor makes sense for. But the closer the web application is to a desktop application replacement, the less its a match. If the web application will require a lot of javascript to implement the UI elements, and effects, the more complex it is to write with a combination of server render logic and client render logic.
also there is a current trend to move to progressive apps, which you need to code in javascript. Once you start code the web application is client code you want a framework, for there are three popular frameworks, react, angular and vue.
all three have similar concepts, client routing, view/component engine, and a store. all three use the node build chain, and have a node cli for creating, testing and developing projects. while angular requires typescript (which is optional for the other two), you will need to know modern javascript, with arrow functions, promises, async/await, functional programming, etc.
if you plan on a long career in web application development, you will need to follow the trends. you should at least learn one of the frameworks.