A nice article that's worth reading by Dino Esposito about ASP.Net 2.0 and webpart development.
"If you’re a SharePoint consultant, or invested a lot in the current version of SharePoint, is the advent of ASP.NET WebParts a good or bad news? And vice versa, if you have significant ASP.NET skills (especially in control development), does the future open up a whole new world of job opportunities in the SharePoint’s land?
Although this article has been written before the release of the Whidbey’s Beta 2—the build announced as feature-complete—I believe that a few quick considerations can be made regarding the future of ASP.NET WebParts and SharePoint products.
- It is rumored that the next version of SharePoint products (both Windows SharePoint Services and SharePoint Portal Server) will entirely be built on the ASP.NET WebParts framework;
- Today’s SharePoint 2.0 WebParts will continue work in the next version of SharePoint, thus preserving your today’s investments;
- ASP.NET WebParts will work in the next version of SharePoint;
- The next availability of an update to SharePoint 2.0 to support ASP.NET 2.0 WebParts seems not to be a far-fetched idea either;
The core code of SharePoint WebParts can be easily ported to ASP.NET WebParts. It goes without saying that the more platform-specific features you use, the more work is required to adapt controls. However, conceptually speaking SharePoint and ASP.NET WebParts support a nearly identical set of features so that mapping one to the other doesn’t pose insurmountable problems."
Read the full article