Welcome
This blog starts at the technical coal face, but I'm also going to let loose on:
So let's dive in with a nice quick and easy one.
When Two Worlds Collide
I was integrating existing user controls into sharepoint, and wanted to replace xml data bindings with lists (but no other changes - I'm lazy like that).
But blow me if there wasn't much info beyond webparts and GUID references!
So this is the simplest solution I could come up with - no CAML or nesting yet, but I'll revisit that...
<%@ Register Tagprefix="SPwebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<asp:DropDownList ID="selCountry" runat="server" DataSourceID="dataSourceCountries" DataTextField="Title" DataValueField="CountryCode2Digit"></asp:DropDownList>
<SPwebControls:SPDataSource id="dataSourceCountries" runat="server" UseInternalName="True" DataSourceMode="List" SelectCommand="<View></View>" >
<SelectParameters>
<asp:Parameter Name="WebUrl" DefaultValue="{sitecollectionroot}"/>
<asp:Parameter Name="ListName" DefaultValue="Countries"/>
<%-- <asp:Parameter Name="WebUrl" DefaultValue="someSubWeb"/> --%>
</SelectParameters>
</SPwebControls:SPDataSource>
I hope this helps someone else - let me know if you improve this or test out dynamic filtering.
NB: For the non.netters, note that <%-- --%> can be used to prevent instantiation and rendering to the page.