Advice for further learning of .Net Core

Question

User1390052142 posted

Hello! I am still fairly new to using ASP.NET Core and have really only worked on one project with it. My first project was an internal company website that we used .Net Core to create as well as implementing a CMS in there too. This was not only my first project as a developer in the work world, but also my first web project ever, so it was certainly a learning experience. Prior to working on it I had 0 experience with .Net Core or MVC in any way. As I begin work on my second project (another web project, but much more robust and complex than my previous project) I want to make sure that I improve upon my previous work. My main concern is that I feel as though I wrote too much hard coded HTML and didn't fully utilize .Net Core's power. My question is, in general, about how much HTML should I actually be writing? On my previous project, I did the entire layout page, and then several of the other pages as well, only utilizing the .Net Core when I needed something to be loaded from the CMS. So for example, on my homepage, I had used HTML/CSS to layout the image and paragraph locations, but used .Net Core to reach out to the CMS to load whatever images or text should be displayed at the time. Does that sound like what I should be doing, or should everything be generated using .Net Core? I know this is a pretty broad question and I'm hoping I don't catch a lot of flack on this. I'm just hoping to find some people who have some solid experience who can point me in the right direction, maybe let me know what I'm doing right and wrong, and where to improve from here. Thanks!

Answer 1

User283571144 posted

Hi ethancodes,

In my opinion,  I suggest you could write enough html and css code to display the page well.

Since the net core will also pass the data to the page before the page has already return to the client side, you generate all the html in the server-side is as same as you write the view's html code.

Besides,as far as I know, it is normally decoupled Front End From Back End.

This means the Back End is used for generate the data and the Front End is used to display the data or image to user.

So we all use jquery, angular js to send the request to the server-side to get the result and fill the data in the html.

The advantage of this:

• completely interact in the front-end with the user and only load data as needed from the server. So better responsiveness and user experience;
• depending on the application, some processing done on the client means you spare the server of those computations.
• have a better flexibility in evolving the back-end and front-end (you can do it separately);
• if your back-end is essentially an API, you can have other clients in front of it like native Android/iPhone applications;
• the separation might make is easier for front-end developers to do CSS/HTML without needing to have a server application running on their machine.

Best Regards,

Brando