Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I Have a question regarding those 2 techniques, if I'm going to use both techniques in my project doesn't they clash?
for example, they both use the MVC model. So if I use the angular routing isn't the ASP.net MVC routing unnecesarry than?
Is it a smart move to only use ASP.net to create the WEB API and the other backend processing, and angularJS to implement MVC and talk to the API
any suggestions?
You shouldn't have to worry about them clashing if done correctly. Your bigger concern should be the additional and redundant work it may cause. For the large majority of situations, having Angular interact directly with WEB API is favorable because it eliminates a layer and makes your UI completely portable between technology stacks.
There are merits to the hybird approach though that are concisely expalined here: https://softwareengineering.stackexchange.com/questions/209735/mixing-angular-and-asp-net-mvc-web-api
The two can complement each other. MVC routing only kicks in when you make a server request. So long as no HTTP request to the server is made, then MVC routing doesn't kick in. I use the server for returning "dynamic content" that depends on some server resident information. You can fetch modals from the server as Partials. Using the Server for mostly API work is however advisable.
There is a project called TwitterBootStrapMVC (https://www.twitterbootstrapmvc.com/) That enables you to render pure bootstrap markup on the server and deliver it to angular after some "post processing". It is handy and works well with Angular.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have just started out doing web development projects for clients and I have done two so far using NextJS, NuxtJS along with headless WordPress for the CMS. As I also have a full time job these projects take a fair amount of time and I end up working constantly.
I have recently come across Webflow and have messed around with it to see how it works. It seems like if I used Webflow and the CMS is provides I could get through projects much quicker than I would currently.
Do you think that for freelancing using a tool like Webflow is a better idea than what I am currently doing?
I currently use Webflow for client projects and I use Next.js at work. I would highly recommend using Webflow for the following reasons on most web dev client projects.
Speed of customization (You can create components in Webflow and copy and past them into new projects, which allows you to reuse standard parts in seconds)
CMS already integrated.
Ability to easily give clients access to edit their own content if they need
Easily edit SEO settings
Easily connect other tools like Zapier and Memberstack if you need
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
We are currently in a tough spot in our university project group. This semester is about object oriented programming. We are to build a web application using ASP.NET. Months ago we decided to use webforms instead of MVC. At the moment we are having some doubts as to if webforms are object oriented. All the content pages have a class but this is the only classes that we have. So my question basically is: Is webforms object oriented and why?
On Microsofts website, 'The ASP.NET page framework presents an object model that enables you to think of your forms as a unit, not as separate client and server pieces. In this model, you can program the page in a more intuitive way than in traditional Web applications, including the ability to set properties for page elements and respond to events.'
So yes, ASP.NET now implements object oriented programming, I believe that in the beginning, not all web application models implementing, but at least now they do, so mvc or webforms will have object oriented features to it. The models are objects themselves, it is possible that mvc would have more features that are oop, but webforms implements models also.
On a Microsoft tutorial they also state that to learn webforms an understanding of object-oriented programming, web-development(html, css, javascript), relational databases, and n-tier architecture are necessary to begin. Here is a link and at the bottom it compares asp.net mvc to webforms https://learn.microsoft.com/en-us/aspnet/web-forms/what-is-web-forms
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
From a developer's perspective (and not from an architectural one) I don't seem much of a difference developing between Asp.net MVC and Server-side Blazor apps.
In fact, the server-side Blazor feels almost identical to MVC excluding some of the convenient data-bindings you can do in the blazor views/pages.
Is there a major difference that I may not be aware of? Again, purely
from a developer's perspective, not from the underlying technology
perspective.
The biggest advantage to server-side Blazor over MVC is that you will be getting the behavior of a single page application (SPA), i.e. rich feeling app with no full page postbacks.
Also in Blazor you are developing components and not Views. Now depending on how you structure you code this may not be of interest, but usually components lead to smaller reusable chunks of UI as opposed to views which tend to be whole pages.
There are potentially more things but they are very opinion based so I'm omitting them here. I hope this helps.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am looking at using Go for my web server:
https://golang.org/doc/articles/wiki/
I was actually going for:
https://spring.io/
since it comes with tons of modules for a web server, like security, data, etc.
Would it make sense to use Go as the Web Server for handling traffic/request and have Spring behind for the actual building of the back-end/MVC?
Or would you typically needs to make a decision between either Go or Spring?
Would it make sense to use Go as the Web Server for handling traffic/request and have Spring behind for the actual building of the back-end/MVC?
No, I don't think so. It's better to take nginx and have Tomcat server with Spring application behind it.
Or would you typically needs to make a decision between either Go or Spring?
Yes, choose what's better for your current task. You can use Spring for the entire web application, Go for some parts, etc.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm porting three of my WP7 apps, that use my WCF SOAP Services to Android (so I can make some money for a change). They don't like SOAP over there so I need to make a duplicate version of my WCF service methods to Restful services.
I created a simple working test service some months ago using the WCF REST Service Template 40(CS) template so that's one choice. However I see a lot on the web about ASP.NET Web API using MVC 4.
My question is: Is this fully cooked and going to grow and prosper or is Microsoft going to get me all involved in this and then drop it like a hot potato after I've got a year in it.
I would choose whatever got the job done that was supportable while being the least effort to implement. If I was on a level playing field I would run with the WebAPI mainly because it is very, very smooth. I would also version my API using versioned urls or content negotiation to insulate myself.
I can't speak for Microsoft, but in general they stand behind anything they have released as a fully supported product for quite some time. I'd expect the WebAPI to be supported at least as long as the platform. I don't see Microsoft dropping .NET support anytime soon and I would expect to see .NET 4.0 supported for the foreseeable future.