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.
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
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 6 years ago.
Improve this question
I am a bachelor's undergraduate. For my third year computer project I am hoping to develop a e-commerce website using angularJs and asp.net web API as I have a basic understanding of it. But I have some of questions with my choice.
1) For a E-commerce web app is it a bad decision to develop using above technologies?
2) Will i be able to handle images and other datatypes combined together with text?
3) Would i be able to handle large amounts of Data?
Thank you very much in advance.
1) Yes. Just as much as you could do any other major stack. Depends on how you implement it. E-commerce is a very generic term. There can be e-commerce web apps with 4 pages or 400 pages. These things really determine your tech stack.
2) Yes. Just as much as you could do any other major stack.
3) Yes, but that depends on what DB you use as well.
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.
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
what is the significance of asp.net webpart controls in today applications?
Where in we have AJAX,JQuery, MVC Controls are being used in today application.Does Webpart Controls still being used? Need to now know more detail in this regard.
Webparts are still quite significant in the Sharepoint/intranet world. However outside of sharepoint I've not seen a lot of development take place around this particular piece of ASP.net.
Non-sharepoint/intranet applications, especially those applications that are public facing would do much better using AJAX/jquery and more open and widely used technologies. This is of course my opinion. But webparts are a little "heavy" for sites/applications that have to keep the general public in mind.
One significance of WebParts is, that it isn't implemented in mono, meaning you can't port your code to non-windows platforms if you use them. Apart from that, now that ASP.NET finally has a MVC framework, I wouldn't use anything with a postback architecture.
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 8 years ago.
Improve this question
I have never programmed web sites. I know that I can create web sites using ASP.
So is it possible to create full web site with Silverlight? Or does Silverlight only support web forms?
Yes I suppose you could.
However, would it be the right choice for your target market?
Silverlight market share : 65%
Flash market share : 95%
Javscript - pretty much everyone
HTML - everyone
If you're tarketing the whole world, personally I wouldn't use silverlight for the whole site, just for features that required it (and even then, I'd write a HTML only backup version for people who don't have silverlight).
However, if you're writing it for a company that you know has silverlight installed and you're familiar with silverlight then go for it!
theoretically it's possible, but I don't think it's really recommended when some environments stop supporting plug-ins as java/flash/silverlight...
I suppose Html5 is the best choice for web development.
Here is a flow chart to help you in your decision
Pick your platform