0

NetTiers works fantastic out of the box using querystrings. Eg:

<data:AspnetUsersDataSource ID="AspnetUsersDataSource" runat="server" SelectMethod="GetByUserId">
    <Parameters>
        <asp:QueryStringParameter Name="UserId" QueryStringField="UserId" Type="String" />
    </Parameters>
</data:AspnetUsersDataSource>

However, if I try to change the parameter to instead be:

<asp:RouteParameter Name="UserId" RouteKey="id" Type="String" />

It just see empty textboxes when navigating to my AspnetUsersEdit.aspx page via the routed url:

user/edit/id

My hunch is this isn't a url routing problem but is instead something I'm missing with how NetTiers fundamentally works. If anyone has successfully used url routing within NetTiers, I'd greatly appreciate any input!

Shaun3180
  • 191
  • 2
  • 9
  • Btw, I am using the 4.0 Framework/IIS 7 in Visual Studio 2010. Point of clarification, I can get routing parameters to work fine using a formview w/ a datasource on the same page, but not with multiformview/user controls (ie, the default website admin installation that is automatically created by netTiers). – Shaun3180 Jul 16 '10 at 16:13

1 Answers1

0

I was able to solve my problem by using FormViews (a slight pain, but good enough for me). One important note that took me some time to solve - NetTiers generated the solution such that periods were contained in the virtual path of the project. Unfortunately this caused havoc with routing when testing locally. Altering the virtual path so as to not contain periods fixed things for me.

Shaun3180
  • 191
  • 2
  • 9