StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWebforms: Inline Literals in .ascx preventing compilation
primarykey
Id
4867622
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-01T20:29:43.157
FavoriteCount
0
LastActivityDate
2011-02-02T19:24:01.390
LastEditDate
2011-02-02T14:41:17.313
LastEditorUserId
91642
OwnerUserId
91642
ParentId
0
PostTypeId
1
Score
0
ViewCount
999
LastEditorDisplayName
text
Body
<p>I have the following snippit in my .ascx file:</p> <pre><code><%@ Control Language="C#" Inherits="MyCompany.Modules.Discovery.ViewDiscovery" AutoEventWireup="true" CodeBehind="ViewDiscovery.ascx.cs" %> <div id="ViewDiscovery_<asp:Literal ID="litModuleId" runat="server" />"></div> <script type="text/javascript" src="<asp:Literal ID="litControlPath" runat="server" />carousel-jquery.js"></script> <script type="text/javascript" src="<asp:Literal ID="litControlPath2" runat="server" />discovery-widget.js"></script> <script type="text/javascript"> $(document).ready(function() { var myData = <asp:Literal ID="litContent" runat="server" />; var myDiscovery = discovery('<asp:Literal ID="litControlPath3" runat="server" />'); myDiscovery.json(myData); myDiscovery.init("ViewDiscovery_<asp:Literal ID="litModuleId2" runat="server" />"); }); </script> </code></pre> <p>As you might be able to infer from the syntax highlighting (or rather, how broken it is), if I try to compile my CodeBehind file with this .ascx file, it fails horribly because it doesn't recognize the various literals that I have sprinkled around in the file, and thus my codebehind file fails to compile. I have to remove them from their positions, put them at the end of the file unencumbered by their context in the page, compile, then revert to the original version.</p> <p>Surely there is nicer way of going about putting literals in the page.</p> <p><strong>EDIT:</strong> When I package my module up and install it on another instance of DotNetNuke (it works fine locally as long as I do that rigamarole when I compile it), it throws an error:</p> <pre><code>DotNetNuke.Services.Exceptions.ModuleLoadException: The tag contains duplicate 'ID' attributes </code></pre> <p>Related, or is there some other issue going on here?</p> <p><strong>EDIT</strong>: I have tried to use <code><%=variable %></code> but haven't gotten anywhere. This is a snippit from my codebehind:</p> <pre><code>namespace MyCompany.Modules.Discovery { partial class ViewDiscovery : PortalModuleBase, IActionable { public string strContent = "Insert Content Here!"; protected void Page_Load(object sender, System.EventArgs e) { // Do stuff here! this.strContent = "My content!"; } } } </code></pre> <p>If I then do this in my ascx file:</p> <pre><code><%@ Control Language="C#" Inherits="MyCompany.Modules.Discovery.ViewDiscovery" AutoEventWireup="true" CodeBehind="ViewDiscovery.ascx.cs" %> <%=this.strContent %> </code></pre> <p>...nothing shows up on my page. A peek at the context of 'this' in the .ascx file reveals it to be of type "ASP.viewdiscovery_ascx", not "ViewDiscovery" as I expected.</p>
Tags
<asp.net><webforms><ascx>
Title
Webforms: Inline Literals in .ascx preventing compilation
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAlexMax
UserOwnerUserId
1. USAlexMax
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.