Source: http://compositec1.codeplex.com/discussions/472364#post1133363
Also registered in HQ TFS as Issue # 4574
Repro:
1. Install the package (attached: Test.ShowQueryString.zip) with 2 user control functions
2. Insert the Test.ShowFunc function on a page.
3. Open the page in a browser appending '?activity=Some' to its URL
4. Check the output on the page.
Expected:
Some
Parameter: Some
Actual:
Some
Parameter:
NOTE. The first line shows the result of :
```
<f:function runat="server" name="Composite.Web.Request.QueryStringValue">
<f:param name="ParameterName" value="activity" />
</f:function>
```
The second line shows the result of:
```
<f:function runat="server" name="Test.ShowParam">
<f:param name="Name">
<f:function runat="server" name="Composite.Web.Request.QueryStringValue">
<f:param name="ParameterName" value="activity" />
</f:function>
</f:param>
</f:function>
```
Comments: ** Comment from web user: burningice **
Also registered in HQ TFS as Issue # 4574
Repro:
1. Install the package (attached: Test.ShowQueryString.zip) with 2 user control functions
2. Insert the Test.ShowFunc function on a page.
3. Open the page in a browser appending '?activity=Some' to its URL
4. Check the output on the page.
Expected:
Some
Parameter: Some
Actual:
Some
Parameter:
NOTE. The first line shows the result of :
```
<f:function runat="server" name="Composite.Web.Request.QueryStringValue">
<f:param name="ParameterName" value="activity" />
</f:function>
```
The second line shows the result of:
```
<f:function runat="server" name="Test.ShowParam">
<f:param name="Name">
<f:function runat="server" name="Composite.Web.Request.QueryStringValue">
<f:param name="ParameterName" value="activity" />
</f:function>
</f:param>
</f:function>
```
Comments: ** Comment from web user: burningice **
Looks more to me that you're overabusing the C1 functions system.
Why not just do
<f:function runat="server" name="Test.ShowParam">
<f:param name="Name">
<%# Request.QueryString["activity"] %>
</f:param>
</f:function>