Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
I am undergoing training in asp.net and the topics which are being taught there these days are repeater and datalist control. I want to know that whether these things are used frequently in the companies. The other thing i want to know is that what are the topics which i should learn in depth so as to get a job. I don't want to go through out dated topics.
I am not aware of what's most demanding in asp.net job sector. Please guide me through.
yes, they are still in use. However, if you are new to Asp.net you might put more effor into learning ASP.NET MVC instead of Webforms.
MVC is a more modern approach with clean separation of concerns. Also you do not get the viewstate / abstraction that webforms has. Find out more here: http://www.asp.net/mvc
However, a lot of sites are still using the webforms approach and they are doing fine. Invest your time in the controls, in Linq and entity framework,
Data GridView, User Data Validation, and learn some basics as like Binding data, xml parser etc.
yes
talking about Asp.net all the server controls are used and will be used.. however Asp.net in itself isnt very good for learning website making as it abstracts away the underlying beautiful http request/response architecture of the web.
so if you are learning asp.net lay a great stress on ViewState that would also help you ultimately build the basics.
With it caching and update panel for ajax are also important. if possible use jquerys ajax that would tell you a lot about the AJAX thing and also would save your time.(i remember just bumping my head on update panel for hours trying to figure out what is going wrong).
then there are features in the c# language itself like linq which are very helpful with connecting to any sort of database on which you should lay stress
Every control group in asp framework is important.It depends upon the requirement of your application.To become good developer
1.)Clear all basics related with framework.
2.)You must know about all controls.
3.)You must know how you play with data.
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 9 years ago.
Improve this question
why should i use telerik radcontrols over visual studio built-in controls. Basically i want to know the pros and cons of telerik controls.
I am new in telerik. I really get very less time for learn something new.
So is it worthwhile to choose telerik over other new technologies.
We use Telerik a lot, togheter with the standard set of controls.
Pros
Prevents you from reinventing the wheel. For example, RadScheduleView and their charts are powerful, if you need them.
Tons of controls, for almost any need
Look and feel-consistency
The huge library of demos and examples provide a solid base when you want to rapidly do or test something
Extensive documentation
Great support from the staff and community on their forums
Widely used - almost every issue encountered has an answer
Quite good MVVM-support
Cons
Some controls are sub par performance wise, but it has gotten better over the last few years
You probably wont use most controls
Your application tends to get rather large (even with optimizations)
The learning curve for some of the most useful controls can be steep, depending on the experience you have
Customization of some of the controls is cumbersome
Some controls don't offer much above the standard ones
My tip is to find out what you want to do, and check if they have a control that seems to make the cut - and try it!
Advantages:
By using this control our lots of coding is reduced. For ex:- Telrik Grid automatically handled Pagging,Filter,Sorting...etc. So, we can reduced development time.
Using telerik style builder, we can easily create our custom theme to match our site theme.
Any .net developer get good hand on this control in very short time.
We can get easily support from telerik team, telerik mvp and telerik users.
In trail demo all the features is available, so we can implement this controls in our page and check the how it looks and match our requirement.
Demos and documents available in live. If internet is not available in our system then we can also install this demo in our system and we can check it offline.
The number of control is very high so after buying this control we do not need to buy any other control.
In-addition its controls also provide client side events and api.
RadControls is a complete ASP.NET AJAX development toolset .It includes more than 70 versatile and performance-optimized components that help you build high-quality, professional line-of-business projects. RadControls speed up UI development up to 5 times and allow web developers to focus most of their time on implementing business logic.
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 believe that one needs to buy a license(?) to use devexpress. I'm currently implementing a gridview and want the sorting arrows to appear in column headers. I know that devexpress grids have that feature and I believe many more? Could anyone point out any specific reason why someone would pay for using a devexpress grid, or I guess the devexpress suite comes with a lot more than just grids?
Could anyone point out any specific reason why someone would pay for using a devexpress grid, or I guess the devexpress suite comes with a
lot more than just grids?
Here is your reason of paying for the third party controls, In Short features give preference to use these rather than the standard controls.
it’s unlikely for the client to have a specific request about some user interface component that can’t be satisfied with either default controls or 3rd party controls. Many of the convenience aspects like detailed view, sorting, auto completion, filtering, and changing perspective have already been solved by the 3rd party companies over the several versions of the controls.
When in need for some UI functionality, it’s better to search the companies’ websites for something suitable, instead of trying to develop from scratch. It will also certainly be cheaper than going over the document, develop, debug, test, and deploy cycle countless times.
By using 3rd party controls it’s easier to keep focus on the actual business functionality for your project, to spend time developing visible features for the application, than to work on solving the many background technical difficulties associated with developing every functional request.
On the other hand, if you reach the conclusion that the control would require some serious modifications in order to suit your needs, it’s probably better to do the entire development in house, eventually based on the simple default controls that come with the .NET Framework.
For example, I do use devexpress controls, on which project i am
working they specially require a developer with knowledge of
DevExpress control, because that will reduce the development time(
Project completion Time also) rather than using the standard control.
The Specific requirement make them to pay for the controls as those
guys commented in this SO thread.
Check these for feature comparison - Standard GridView vs DevExpress GridView. I like it's client side functionality..
Here's a reason. Because they want sorting arrows in column headers. Also, any of hundreds of other features these products provide that the default grid does not.
The point is, the extra features ARE the specific reason.
Not only does it take care of operations such as sorting and search. It is actually very useful in helping you populate data from your database easily by quickly mapping your fields to IQueryables (If you are using C# and not DevExtreme). If you're using the grid on many pages in your platform, you can easily configure all these grids from one single point (Themes, Functionality, Configuration, etc...). It also provides additional security measures to prevent certain injection attacks. Finally, it is always updated with new features and improvements with constant releases. One really important thing too is that the DevExpress help center and forums are very rich and you will find an answer for almost any question or issue you come across. So using the DevExpress component will bring scalability and increase reliability with time for your platform.
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
My question is simple and straight forward - Is DevExpress fast enough for real world web application. We're using DevExpress in our company to build a CRM for a client and every page has got lots of controls and its damn slow. On my development server it takes 10sec for a page with around 20 controls to load. Is this good or bad? And can you guys point me to a real life DevExpress application except the ones given on the case study section.
I realize that this question is quite old and the original author has probably long since made a decision. However, when I was personally directed by my company to use DevExpress and I was trying to eek out all of the performance that I could, a Google search would always point to this thread and many like it across the internet. There's always a question, a few anecdotal responses, and usually a PR response from somebody that works for DevExpress. I rarely find honest answers from experienced people.
In the past, I've used Telerik, Infragistic, and DevExpress. From a performance and maintenance perspective, DevExpress is the worst. All of their controls have odd properties and accessors that do not align with what somebody that is familiar with ASP.NET or even HTML would expect. Since the properties and accessors of the controls are so convoluted, you will find that you've written about twice as many lines of code that are necessary in a normal .NET application.
DevExpress controls are rendered out as hugely bloated, nested tables. Some controls expose a lightweight rendering mode that is better, but their styling and functionality do not match with the other DevExpress controls, and I found them to be quite buggy in cross-browser testing.
Custom styling requires many, many custom CSS selectors that force you to code DevExpress class names into your CSS, due to the nested and hidden nature of the control properties. This is very bad practice, since DevExpress can and should be able to change their internal CSS class names whenever they see fit.
These controls also make an absurd number of GET requests to their DXR.axd handler that serves up resources.
There's no doubt that their controls work fine in a Demo environment with only 1 control displayed on the screen, but in the real world, these controls are terrible and should be avoided. Implement your own controls or just download Bootstrap and use native ASP.NET controls. I replaced DevExpress with controls that I created that style the native HTML type that gets rendered from .NET and the following chart illustrates some of the differences in resource usage between the two. There were no changes to the page layout, business layer, data layer, or database code for this swap, just a replacement of DevExpress controls that I'd previously optimized and tried to squeeze every bit of performance out of with my own controls.
Chart Comparing DevExpress to Custom Controls
That's bad, but I wouldn't point straight at the DevExpress controls when assigning blame - I'd be running a profiler against my code to work out where the issue really is.
Soham,
As a general rule, when designing for the web, try to keep your pages light so they can run faster. For example, do you absolutely need 20 controls on one page?
And if they do not need any special functionality then you can use the native rendering.
Also, check out my article on the DevExpress web.config settings to improve performance.
Btw, I work for DevExpress. :)
I have no DevExpress experience, but you may also want to check out Improving Asp.net performance. It might help out as well.
2016 - Over the last 5 years I have used Infragistics, Dev Express, Telerik in that order.
Infragistics I won't even get started on because it is a subject unto itself.
My biggest pet peeve with Dev Express is their controls do add some "bloat" to the overall result. However, some controls do have feature sets that are worthy of the bloat. Certainly their Grid and Pivot grid are complex tools that allow the user to do many things, and i have successfully implemented Devexpress packages that worked both quickly with very good results. I have two problems with Dev Express:
Every time I install a new version, it breaks a significant amount of code, that's both WebForms and MVC implementations. That is quite frustrating, but as programmers to be expected I guess.
They really don't look very nice, you have to go through significant effort to get the to look anything close to a bootstrap table etc. Once done though they do allow all the needed bells and whistles. You could of course as the authors above suggest grow your own, that's always an option, but it's not why people buy controls. They are trying to leverage their time so that they can implement faster of course.
Having said all this, Telerik is the current best of breed, in my opinion by far. Easier to implement, grids are fast, have proper desirable functionality and look better.
If you use 20 Controls containing Textboxes with formlayouts, probably the Server takes a hard time to render that page containing alot of hierarchy of long tags in it. DevExpress is bad on having multiple Controls. Redering one ASPxTextbox Control could take KB compared to hundreds of byte on ASP.net Textbox control.
It very common for an entry page to have more than 20 controls. I did use devexpress for years, the speed and performance are acceptable. We use to build ERP solution.
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'm about to create a site that will act as public front site of company that sells furniture, but after user log in, he'll see much more options. Internal news, files to download, customized pricings, newsletters, etc. - stuff for wholesale clients.
I want to make it quickly and maintain/extend it easily. I'm asp.net developer and while I could write it in python, php, whatever else (I know these too), I still prefer asp.net. I was thinking about umbraco, since it gives a real productivity boost and that I familiar with it ( and extending it). I've had a short romance with ASP.NET MVC, so I know what it's all about, but I would still spend some time learning it (but what a fun!). Of course, there's also webforms, but that's my last choice here. Last but not least to mention is the SEO.
The question is, have anyone of you had similiar dilemma and what was your final choice?
EDIT:
Just wanted to notice, that this site will be maintained by me and by the client. And the goal is to set it up asap, but that doesn't end the development process. This product will live on for years.
This is the age old question - bespoke vs off the shelf.
With Umbraco you have the potential for an awful lot more site in a lot less time since the requirement is substantially to produce the content rather than the infrastructure. In terms of UI you can produce you should be pretty close either way - Umbraco gives you a lot of control.
With MVC you get to do anything you want - but one way or another you have to build it and, more importantly in terms of this question, you have to build the tools to maintain the content too.
And this is why there is a dilemma - because with Umbraco (or any packaged CMS) the question is 1) can you do what you need within its constraints and 2) where you can't how easy is it to extend the system to deal with those elements that need to be custom.
Finally there's the question of who is maintaining the content - if its to be the site "owner" (which it should be) how are they going to interact with the system? This is the advantage that Umbraco has in that the whole content maintenance thing is handed to you on a plate.
One last point - remember that you have a duty to your client to choose what is best for them and not to choose a platform because you want to play with new toys. Thankfully a lot of the time the two coincide (-: but its worth bearing in mind. (Oh, and before you write off forms completely, remember that ASP.NET Dynamic Data - forms based - will give you an instant database maintenance site which will go some way toward dealing with the maint problem that you'd have with an MVC site).
So... no absolute answer because there is no single "right" - you're almost always working on a case by case basis.
Comparing MVC and Umbraco is comparing apples and oranges really. Umbraco is a Content Management System and as such provides plenty of out of the box functionality that it seems your client needs, whereas MVC is a web development framework, and as such is at a lower level than Umbraco. Using MVC to implement the features needed by your client is very much the same as using asp.net web forms to implement the very same features. In fact, Umbraco could decide at one point to use MVC to implement it's features.
So I agree with Murph, the choice should be Content Management System versus implementing CMS features yourself using MVC or any other web development framework (and yes, MVC is brilliant).
Since you are familiar with Umbraco, as am I, you know that you will be stuck integrating packages. This may not be a bad thing, but it is a consideration. You will not be able to use that website with any other solution. As you know Umbraco consumes the entire website.
I personally would go with MVC, because I love it. Version 2 was just released today, making it even easy to put an application together in no time.
Just want to tell you that I'm going down the n2 + mvc road.
Thanks for the answers!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
We are building a web application using C# and SQL server. We are thinking about buying the DevExpress ASP.NET controls. Anybody have any opinions about this tool or have any they would recommend?
I've made extensive use of the DevExpress ASPxGridView and many of their other controls.
As mentioned earlier, the DevExpress controls can create a lot of markup, however, they other a ton of functionality and features. They're pretty easy to use. If all you're needing is a really simple grid control, then it's probably overkill. However, if you want to have features like sorting/grouping, drag-drop re-ordering of columns, hiding and adding columns at run-time, AJAX support, etc. then these controls are awesome.
Recent versions (2009.2 and 2009.3) have introduced a number of performance improvements mainly around reducing the volume of traffic and cycle time involved in round-trips to the server. This has made the controls feel even snappier at the end-user side.
One other key benefit of the DevExpress controls is the support. These guys are excellent at getting back to you with meaningful answers to questions in a timely manner. I also enjoy the fact that they have several releases per year which include enhancements and new functionality. You can see their release history by looking at their release history for the ASPxGridView: http://devexpress.com/Products/NET/Controls/ASP/Grid/whatsnew.xml
All in all, I think it's a good value for the money.
By the way, I have no affiliation with DevExpress, I'm just a happy customer.
I can't comment on the DevExpress control, but as you were also asking for alternatives:
I was mainly using Telerik RadControls for ASP.NET Ajax in the past. This is a full suite of controls with many controls (have a look at the demos to get an idea). I think these controls are quite powerful, although you'll need to consult the documentation to take advantage of all the features. In addition, I'd like to point out that telerik offers great support (in my experience).
i think the tool is good, but if you are just starting the building of the application i would recommend using asp.net mvc instead of asp.net webforms
I used the DevExpress grid controls on a project and they were excellent. Easy to skin and customise with some great features out of the box like filtering, sorting and AJAX support.
We have used the Infragistics WebGrid. They have great knowledge base and help available from their website.
The feature I liked and implemented was the client side edit of data simulating excel functionality. You can edit the cell by simply moving the arrow keys and without using mouse.
Take a sample look at http://samples.infragistics.com/2009.2/WebFeatureBrowser/Default.aspx
I've used both and my honest opinion is that they are over-engineered (esp. Telerik) and create a lot of muck in the markup. Also, there is always a learning curve involved in successfully adopting any of these offerings. However, if you really do have to have the eye candy, go for it:-)