Geek Answers Handbook

What is your experience using ASP.NET 2.0 web pages?

I would like to know your experience with ASP.NET web pages as a reusable component on your website.

How useful is it? Are you having serious problems? Would you recommend using it in any asp.net project?

Any recommendations or tips that you would like to emphasize regarding this.

Would you recommend using web pages as part of the asp.net portal design, or our center of your design around our old old UserControl as a basis.

This input will help me make a decision for the asp.net application that I am developing.

If you need more clarification, please leave comments.

+4
source share
5 answers

Benefits of WebParts over UserControls:

  • Support for custom editable properties and personalization built into
  • Custom Editor Parts
  • Customizable WebPart Standard Menus
  • Drag'n'Drop WebParts between WebPartZones
  • Connection support between WebParts, useful for viewing basic / detailed data, filters, etc.
  • You can download UserControls

Disadvantages:

  • Use of higher resources.
  • Visual Studio does not currently have designer support for WebParts

As mentioned in ocdecio, ASP.NET MVC is probably the best choice these days, at least outside the SharePoint world, where WebParts are very important.

EDIT:

For an overview of ASP.NET 2.0 WebParts, you can see:

Use WebParts in ASP.Net 2.0 and Personalize Your Portal with User Controls and Custom Web Parts

+2
source

I personally would not recommend WebParts for your application if you are not going to explode completely in the paradigm of the website portal. I played with them sparingly, and he just doesn’t feel that it will be as effective as developing your own works.

+2
source

In my experience, web parts are useful for creating content for SharePoint. But now with ASP.NET MVC, I'm not sure that they will be a good choice for a standard ASP.NET application.

+1
source

I agree with TheTXI ... like many ASP.NET technologies, you won’t get much benefit from the web parts unless you purchase a 100% model.

But besides this, we had some technical problems, mainly related to cross browser issues. Perhaps this has been fixed in recent releases, I do not know: we have finished our own decision.

+1
source

ASP.NET MVC gets so much effort. It literally blows everything else out of the water. I would recommend studying this first. Sharepoint is likely to include MVC soon.

0
source

More articles:


All Articles