It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I am a Asp.net developer and due to new advancements I am confused between MVC and Entity Framework.I would like to know which is the best option to study first EF or MVC
The two are completely different and have different purposes.
MVC (Model View Controller) is a programmatical pattern used for building applications. Microsoft have a a framework called ASP.Net MVC which is their implementation of it for building MVC websites.
Entity Framework (EF) is an ORM (Object Relational Mapping) tool. This is used primarily for simplifying the data access layer of an application. This can be used in conjunction with ASP.Net MVC.
Personally, I would read about ASP.Net MVC first. This is because you can then use any one of several ORMs with it, including NHibernate and Linq2SQL, the latter being very lightweight and a perfect place to start.
I think they "must" works toghether to get the best. Entity framework, you can think of it as a way to access the database (in an object-oriented fashion). While Asp .NET MVC (which let you choose how to handle the model part, so you can easily use EF) is a framework to create a web application; you can think of it as something that will help you create html pages. As I've stated before, you can easily use entity framework as the M part of mvc if you need to interact with a database.
I suggest you to study MVC first because will give more results (they are something that you can see), then EF. However this is a totally subjective thing.
The most "student" approach is to study EF first and then mvc, but in this case you won't see any real result 'till you studied a bit of MVC.
Hope this helps in any way.
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I need to know the technical difference of those files. Which one is the best option?
When and why should we use it?
I need a human answer, not the MSDN links.
.ashx files are used for handling HttpRequests and modifying HttpResponses; you can pretty much make them do whatever you want. I have seen them used for things like serving PDFs and doing server-side processing and then redirecting. See here for more info.
.svc files (which were not mentioned in your question) are part of MS's new Windows Communication Foundation which is for SOA development. WCF supports SOAP, REST and a lot of other cool stuff.
.asmx files are an older means to host SOAP services. They are often accompanied by asmx.cs files (or .vb) which contain the actual methods behind the service. See here for more info. This is a legacy technology and I would recommend using WCF instead in new development.
[WebMethod] attribute is used to denote the methods surfaced in a SOAP service hosted by an asmx. See here for more info.
The .axd extension is used by generated web services used for many different things. (E.g. MVC3 uses axd web services to serve MS specific javascript) I don't think you would ever create an axd file, but I could be wrong... at least I never have. See here for more info.
Which one is the best option?
They are different tools used to solve different problems. When and why you should use each one depends on the job you are trying to accomplish. Lower level handling of your web application's behaviours can be achieved with ashx files. If you want to provide more standardized services, I would recommend using WCF and svc files. Please provide us with more information about the task you are doing so we can help you pick one.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
as the title says, I want to develop a browser multiplayer game with HTML5.
The game will be something like "risk", the turn-based strategy game. I decided to develop with HTML5 and the new canvas.
But the problem is on the server side. When I google, I only get answers, where people use "System.io", "node.js" etc. for that.
So my question is:
Is ASP.NET - especially MVC 4 - a bad choice for my purpose? I would like to do that with asp.net, but of course not when there is an easier/more suited option.
Some people say asp.net is not suited for that, it's too complicated and so on.
But I ask you pros out there :D
Would you consider developing a game like that with asp.net mvc 4 or better stick to other solutions with system.io and node.js and other frameworks? (php?)
I hope you can help my out, that stresses me for weeks now :(
Thanks in Advance!
Greetings from Munich
Tornister
Asp.net, especially MVC is well suited to develop an html5 based game.
A turn based game, is not very different from a web based chat. Where you send messages between members via the server.
To design a scalable solution, you got to use the right methods though.
You have various options to communicate between users.
Libraries like SignalR would help. If you do want to do it yourself, the most efficient method is to use a IHttpAsyncHandler and ajax requests. In MVC the equivalend it AsyncController.
Frameworks like node.js are designed to be async, and thus well suited. Php out of the box is not a good choice for such applications as it doesn't support async requests.
To sum it up, asp.net is not a bad choice, but you need to know how to use it. If you are more comfortable with another framework like node.js, then you should choose that one. Familiarity reduces a lot of development time.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I'm developing an ASP Web API project and using KnockoutJS as the client side technology. To the best of my knowledge there are no examples projects or any kind of sources available in internet for these two technologies yet. If someone has used these two technologies for their development, it is great if you can provide some links here (If there are online sources). I am posing this not as a question but to get some online sources about these technologies to one place (Because as I know there are no online sources yet). If someone know any sources about the projects which have used these two technologies in there architecture, it will be a great help for me (Since there are no online sources).
Thank you.
You should checkout upshot.js, Steve Sanderson's library for interfacing with WebAPI REST services. It is designed to complement knockout.js when building single page applications, facilitating communication between the view model (knockout) and the back end (WebAPI).
Here's a relevant SO post:
Where can I find Upshot.js examples and documentation?
I don't really have any links to share, but on the server side WebAPI outputs JSON by default and client/KnockoutJS side you are just consuming JSON. I use jQuery's .getJson() method and update my KO view model with the return data.
Check out John Petersen's blog for some good Web API samples.
Technically, Knockout.js doesn't help with accessing a REST API specifically Knockout with JSON. So, yea it works fine and I've used to with the Web API no problem. There is the Mapping plugin that helps with mapping the data to your view models which may be useful to you: http://knockoutjs.com/documentation/plugins-mapping.html
Backbone.js is meant to work with REST APIs (like Web API) and there is a project that makes Knockout work with Backbone (https://groups.google.com/forum/?fromgroups#!topic/knockoutjs/SAESwAqjfK4). I haven't used it so I don't know if it works well or not.
I am trying to make sense of the complete cycle from the point when a user issues a request from the browser to the point response is rendered for both ASP.NET Web Forms and ASP.NET MVC.
UPDATE:
Specifically, the concept of Page LifeCycle does not exist in ASP.NET MVC.
If the answer compares both these technologies from that view point it would be great.
That's an awful lot to ask for a simple question on a Q & A Forum site. It is pretty close to the definition of "not a real question" per the guidelines of the site:
It's difficult to tell what is being asked here. This question is
ambiguous, vague, incomplete, overly broad, or rhetorical and cannot
be reasonably answered in its current form
It is a real question in most senses, and a good one, but it is overly broad for a simple answer.
However, in the spirit of trying to be helpful, here are a few links that might be helpful:
How ASP.NET works
ASP.NET Page Lifecycle
How ASP.NET MVC Works
How web servers work
Personally, I like the explanation that came out in the older books from when ASP.NET and .NET in general were "the new thing". Every one of them did a good job of explaining the difference between static HTML and "dynamic" technologies like CGI, classic ASP, JSP, and then went into how ASP.NET works. Beginning ASP.NET 1.0 with C# from Wrox was the first book I read on the subject.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
Back in 2006 I've created a web site using asp.net 2.0. At that time, I had used Web Forms and classic ADO.NET SQL queries to connect to the underlying database. I've also used a fair amount of XSLT.
Today, the site still stands (it has gone through various upgrades but it is still based on Web Forms and simple SQL queries) but I believe it really needs to be upgraded as far as its technological infrastructure is concerned.
What is the next step I should take to move forward? A bit of ajax? JQuery maybe? Rewrite it in asp.net mvc? Replace SQL with typed datasets or even ling to sql? And what is the best way to embrace APIs such as twitter's?
So, can an old dog learn new tricks?
So why do you believe the site's infrastructure needs to be upgraded? If the site is running and performing well after 6 years of load and data, then what factors are causing you to think you need to upgrade it?
Are there features that you want to implement (or users are asking for) that you can't implement with the current infrastructure?
Is maintenance difficult and brittle, and every time you upgrade, you spend weeks fixing bugs introduced?
Are there integrations that you'd like users to be able to do so that they can extend your application's functionality and/or data to their own applications?
Those reasons above could be reasons to upgrade, but I can't really tell you.
But as far as some of your questions about what to upgrade:
a bit of AJAX? It depends on what your current infrastructure looks like, but it's not too hard to introduce and you can isolate it
pretty well with a service layer.
jQuery? Again, it depends on
how your pages are structured. If you have a lot of master page
re-written IDs and very few classes on your DOM elements, using
jQuery right off the bat may be tough as you'll have to figure out
how to get your selectors in line.
Replace SQL with Typed
DataSets? Please don't do that. Honestly, if you go with
Linq-to-SQL or EF, you'll probably take a slight performance hit
compared to using ADO.NET with DataReaders (if that's what you're
using).
Can an old dog learn new tricks? Always. The learning
never stops.
I would just advise not to upgrade just to upgrade. Make sure you have legitimate business reasons for doing so.
Hope this helps. Good luck!
Step 1) figure out what would add value for your users
Step 2) investigate technical solutions to solving those problems
Step 3) learn and build
You could create a persistence layer and learn about entities. This is an extremely useful skill to have. You could do this by using NHibernate. I would also throw in some LINQ to get a great combo. After this i would probably go to the GUI and do some needed features with jQuery