Anyone have an minimal example of ASP.NET MVC and dotnetcharting.com control lying around?
Thanks,
rodchar
New asp.net charting controls - will they work with MVC (eventually)?
You can download ASP.NET samples of the .NET Charting control here. It gives a wide range of examples and provides code snippets to go with.
You can use the Microsoft ASP.NET chart control that James mentions with the MVC Framework. The control was designed for use with WebForms, but it will work from an MVC View as long as you don't need to handle postback events. If you do, you may want to consider developing a hybrid solution with WebForms pages where charting is required and MVC for the rest of the site.
Related
I have worked with ASP.NET MVC 5.0 and that is the only ASP* technology I have ever seen or worked with. I even searched on Goolge and got more confused.
For example in this book, what are they teaching? When they say ASP.NET, does it mean ASP.NET Web Forms?
Mainly my question is this: When I see ASP.NET , does it mean ASP.NET WebForms? ( Unless it is ASP.NET core or MVC, those two I know ) but I get confused between ASP.NET and ASP.NET WebForms?
Many years ago one time I dragged dropped some buttons and text boxes on a ASP.NET page, it was VS2003 :) I think, so was that ASP.NET WebForms and this book above is still the continuation of that one? Or we can use some sort of ASP.NET that is not WebForms or MVC or Core too?
ASP.NET is a technology which is developed by Microsoft. You use it 2 different ways which are ASP.NET Web Forms and ASP.NET MVC. These are pattern and they have changable usage for the user. They have many layer.
For easy example: https://www.tutorialspoint.com/asp.net/asp.net_introduction.htm That's All :))
ASP.NET is a framework for creating server side web applications so it's set of tools , API , libraries ...etc , web forms is just part from this framework , other parts include ASP.NET MVC, ASP.NET Web Pages, and ASP.NET Single Page Applications.
check this :
https://www.asp.net/web-forms/what-is-web-forms
If we turned back the time, ASP.NET was of course WebForms initially in 2001, so we don't even need to explicitly call it WebForms.
The meaning of ASP.NET only changed when Microsoft published ASP.NET MVC (and later Web API/SignalR/Web Pages), some time around 2010. From then on ASP.NET is the umbrella term to cover them all, as well as WebForms.
Recently ASP.NET Core was created as a brand new platform, different from all previous frameworks. Thus, IMHO ASP.NET Core != ASP.NET.
Back to the book cover, it should mean all things under ASP.NET 4.5, which includes WebForms/MVC/Web API/SignalR/Web Pages.
I actually have that textbook and the author presents the material using ASP.NET WebForms. I believe he covers MVC but in short detail; I can't remember offhand.
As for the other answers, yes, ASP.NET is Microsoft's web programming framework. There are basically three primary technologies that you can leverage: ASP.NET MVC, ASP.NET Web API (actually an extension of ASP.NET MVC), and ASP.NET WebForms. You can of course create other types of apps as well, such as SPAs, but these are definitely the primary technologies available to you. The nice thing about these is that you aren't necessarily tied to one technology - you can mix and match different technologies in one solution.
If you are completely new to ASP.NET, I would suggest you look at Microsoft's tutorials on building ASP.NET Core applications so you can leverage the cross-platform technologies Microsoft is heading towards. You mentioned that you've worked with ASP.NET MVC and .NET Core, so I'm assuming you're also aware that you can leverage ASP.NET Web API there as well.
https://learn.microsoft.com/en-us/aspnet/core/data/ef-mvc/intro
Hope that helps.
I know S#arp architecture is built for ASP.NET MVC. But I'm wondering if it can be used in classic ASP.NET (WebForms) or even desktop applications like WinForms or WPF.
Thnkas a lot.
Iain,
You most definitely could use S#arp Architecture in an application other than ASP.NET MVC. I use it to power several console applications and we have a few windows services running it as well.
You would want to look at the S#arp Architecture Contrib project to use it in a non MVC or Web Form app. To use it in web forms, you would use spin it up as you would a MVC application, but using it in your web forms would be slightly different. In this case, look for an MVVM or MVP solution and replace as you need.
As far as I understood from your question, you should have a look at the MVP pattern. You can create your own Models and Views by yourself with asp.net forms.
I'm not sure about WebForms or WPF but if you want to use it for WinForms, check this out:
wiki.sharparchitecture.net/ContribNonWebHowTo.ashx
I have found it to be very workable.
this is my first question Here ,
I am a beginner in asp.net , and i want to make a CMS project using it
After Some readings I found that the MVC structure is very suitable for Me
Just want to know :
how much the asp.net MVC depend on the normal asp.net??
as a beginner i don't know the level of knowledge for Normal asp.net to start working using asp.net MVC
Please tell me where to start in the normal asp.net(3.5) and when to switch to learn the asp.net MVC ??
Detailed information is very welcome
Thanks For your Time
It is built on normal ASP.NET minus postbacks, viewstate, and event wiring. The underlying System.Web stuff is the same, but with some new wrappers to access it, and of course a bunch of new featuers that make up the MVC portion. Just get a book on ASP.NET MVC, and don't worry about classic ASP.NET.
'normal' (also known as WebForms) asp.net and 'mvc' asp.net are somewhat different from each other in how things are put together and how things work with each other. There is no need to learn one before learning the other.
If you read through this article you can see at a glance what the differences are between 'normal' or WebForms and 'mvc'.
Here is a pretty good tutorial for learning about MVC from Scott Guthrie if this is the way that you're leaning.
Good luck and have fun!
It depends on what you mean by "ASP.NET". ASP.NET MVC does depend on standard ASP.NET request processing pipeline (IHttpModules, IHttpHandlers and all other internal workings), but it does not depend on WebForms infrastructure.
I've recently jumped on the ASP.NET MVC bandwagon and I found the introduction tutorials on the official http://asp.net/mvc site very useful.
ASP.NET WebForms tried to mimic WinForms desktop apps in that you have controls and event-driven interaction, which is not particularly well suited to the stateless HTTP
ASP.NET MVC gives you full control over the HTML that is generated and sent back to the browser, but more importantly, it makes it easier to write testable code.
Also, ASP.NET MVC does not depend on ASP.NET WebForms, they are built on the same foundation. In fact, in principle, you can mix and use both in the same app if you really wanted to :)
When MVC was released, what used to be simply ASP.NET was renamed ASP.NET Webforms and MVC because ASP.NET MVC. Not sure if that answers your question but it does clear up some terminology.
Why not start with Asp.Net MVC ?
Asp.Net is split now into 2 parts. Webforms and MVC.
I'd advise looking at the following -
http://bloggingabout.net/blogs/mischa/archive/2008/02/04/asp-net-mvc-vs-asp-net-webforms-vs-ruby-on-rails.aspx
http://nerddinner.codeplex.com/
I'm currently present with the following situation.
We have a huge enterprise application written with WebForms. Refactoring it or completely rewriting it is out of the question. So I'm not talking about migration WebForms -> MVC.
However, I understand one can technically add MVC functionality to coexist with the rest of the project. I was asked to present MVC concepts for a team so that we can consider how it could become (or not) of use to us.
After careful thinking I do not see any ways or reasons to add MVC elements to a WebForms project since it will become a strange breed then.
Maybe there are certain not exactly obvious possibilities to add value to a WebForms project with MVC framework? Has anybody thought about it?
Sharing a master between MVC and WebForms - dealing with the
Mixing ASP.NET Webforms and ASP.NET MVC
ASP.NET MVC WebForms Hybrid application
Combining MVC and WebForms from Pro ASP.NET MVC Framework (also available here)
I would also look at this article from Scott Hanselman. He seems to have the mojo on mixing these technologies.
Plug in Hybrids...Mixing ASP.NET and ...
My company has developed (and still continues to develope) a large ASP.NET business application. Our platform is ASP.NET 2.0 using some ASP.NET Ajax. We're extensively using third-party components, like webgrids, comboboxes, treeviews, calendar and scheduling controls etc.
Now, I don't know a lot of ASP.NET MVC and I'd like to know if there is a way to use these third-party-controls in the ASP.NET MVC model. Or do vendors have to rewrite their products in order to make them suitable for ASP.NET MVC?
If they use the ASP.NET Control Model (That will be about 99,9% of controls written by ASP.NET Control vendors), they have to rewrite their controls. How much work there is in that, is very different depending of there arhitecture of their controls - the more ajax they already use, the more posible it is that they easily can change it to MVC.
ASP.NET AJAX Control toolkit for exsample can work with MVC. You can see how to do this in a video on WWW.ASP.NET: http://www.asp.net/learn/mvc-videos/video-373.aspx
Much of the controls will need rewriting, as most of them need the postback model in class ic webforms. And there is no postback in asp.net mvc.
so: postback required for the component? -> won't work in asp.net mvc
For the record. I received the Telerik email newsletter with some interesting news:
"One of our most exciting product novelties is that RadControls for ASP.NET AJAX are able to work in the new Microsoft ASP.NET MVC framework." [...]
Link: Telerik RadControls in Microsoft ASP.NET MVC
The ISV market definitely has smoe catching up to do with MVC, but that makes sense - it isn't RTM yet (although the last preview at least had an explicit "go live" licence). Regular Webforms controls will pretty-much need re-writing.
I don't imagine it will take long for the major players to catch up, but if you are using something from a smaller company it could be hard getting it to prioritise MVC. One (really hacky) option might be using an IFRAME or AJAX to treat a portion of the page as a separate aspx page... really, really nasty.
You gotta question how interested the 3rd party market is in creating mvc controls when it has such a low market share. They seem to want to just focus on webforms and silverlight/wpf controls.
I am reviewing syncfusion tools for mvc (just downloaded it). It's worth a look-see. Seems to be actually designed to work for MVC.