<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Visual Studio Spoiled Me, and Web Parts Framework Made Me Learn</title><link>http://blogs.technet.com/aqa/archive/2008/07/27/visual-studio-spoiled-me-and-web-parts-framework-made-me-learn.aspx</link><description>It took me sometime until I figured out some facts about Web Parts lifecycle. The following are some findings I believe will make you rethink what methods and events to override to develop a Web Part: CreateChildControls() is - from what it is - used</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>