Last post Jul 25, 2017 02:29 AM by Jean Sun
Jul 24, 2017 10:26 AM|SW2014|LINK
Hi, I'm more of a Windows Infrastructure guy with 20 years in the field. However, I've done some pretty respectable things with C# .NET (Winforms and few basic Webforms projects) over the last 10 years. Anyway, have this idea for a website and thought I'd
get the project kickstarted by paying some freelancer.com developers to churn out a basic outline using ASP.NET MVC. The idea was to take it over from them and begin learning/improving it. What they've given me so far looks brilliant from the outside but inside,
it's not what I was expecting. The entire thing looks completely alien to me as a semi-pro C# developer.
Jul 24, 2017 11:57 AM|PatriceSc|LINK
Jul 24, 2017 12:05 PM|DA924|LINK
being done from the browser as much as possible and not using C# server side code as much as possible from a UI standpoint.
That's not a good thing, and the presentation layer should be coming to the backend for DB activities and business rules to be applied by manes of server side code using C# in a n-tier solution.
a server side technology using C#.
Jul 24, 2017 08:27 PM|bruce (sqlwork.com)|LINK
1) a template approach (angular / Vue / ember). the controls are defined via template engine, with binding parameters. this is similar to asp.net and razor views.
2) a component approach (react.js). this is most like winforms, where you create a component for each control.
load preformance (see spa services for mvc calling node.js to do this.)
Jul 25, 2017 02:29 AM|Jean Sun|LINK
important part in the web development and I think every web developer need to learn them.
If you want to focus on the server side development of the web application, you don't need to spend 3 years to learn JS/Ajax and other technologies, you can just take some time to learn the basic of