Are ASP.NET Web Parts a viable technology for implementing portal architecture

Web parts appear to be widely used in development related to Sharepoint, but there are few examples of their use in asp.net web application applications. I am implementing a portal infrastructure for specific domains and, for example, "widget-like" functionality in iGoogle or pages, and would like to receive such a function in my application. From my point of view, the real troubling problem is that the drag and drop features of web parts do not work in browsers other than IE unless you are using the latest ASP.NET AJAX fantasy library. It seems to me that Microsoft implied that this would be a fundamental technology, now they would transfer these functions to the main product.

Are Web Parts a Dead End Technology? If so, are there any alternatives?

+5
source share
3 answers

I think they are (dead), at least for the development of user interface types that modern web browsers are looking for. My recommendation ... ASP.NET MVC and a good .js library. It works out of the gate more, but with proper planning and implementation, it will serve you much better in the long run.

+2
source

I found a really great site about some tips for implementing behavior similar to WebParts: http://blogs.msdn.com/b/nunos/archive/2010/02/16/quick-tips-about-asp-net-mvc-webpart -framework.aspx

+1
source

- .NET . , - J2EE.

0
source

All Articles