StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1362546
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-09-01T13:39:15.237
FavoriteCount
0
LastActivityDate
2009-09-01T13:39:15.237
LastEditDate
LastEditorUserId
0
OwnerUserId
161852
ParentId
1325101
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I developed a solution that solves my problem in VS 2008: <ol> <li>Create Main Site Solution: Create a MVC 1 Website solution in VS 2008 </li> <li>Create Model Class Library: Add a Class Library for the Model Code</li> <li>Create View Code: Add an "Empty Website" to hold the .ascx pages, and add a reference the model library</li> <li>Create Deployment Site: Add a deployment project that compiles the "Empty Website" goto the "properties page" and Check: "Merge All outputs into a single assembly" and "Treat as library component" and be sure to UnCheck: "Allow this precompiled site to be updatable"</li> <li>Reference Deployment Output: In the main project add a reference to the output of the Deployment site. </li> <li>ASP. - Compiled Controls: Controls show up under the ASP. namespace and are named in two ways A. if the .ascx / aspx page did not declare a "ClassName" then they are named using their folder and file name with underscores ex. <%@ Control Language="C#" ClassName="Admin_Index" %> B. if they did declare a class name then that is their name</li> <li>List item</li> </ol> Usage: Example code is below Here is an example usage <pre><code>public ActionResult Index() { var ctl = new ASP.Directory_FirmProfile(); //create an instance ctl.Setup(new MyDataModel); //assign data //string test = CompiledControl.Render(ctl); //output to string return new HtmlCtl.StrongView(ctl); //output to response } public class CompiledControl { public static string Render(Control c) { Page pageHolder = new Page(); pageHolder.Controls.Add(c); StringWriter output = new StringWriter(); HttpContext.Current.Server.Execute(pageHolder, output, false); return output.ToString(); } public static void Render(Control c, StringWriter output) { Page pageHolder = new Page(); pageHolder.Controls.Add(c); HttpContext.Current.Server.Execute(pageHolder, output, false); } public static void Render(Control c, HttpResponseBase r) { Page pageHolder = new Page(); pageHolder.Controls.Add(c); HttpContext.Current.Server.Execute(pageHolder, r.Output, false); } } public class StrongView : ActionResult { private Control ctl; public StrongView(Control ctl) { this.ctl = ctl; } public string VirtualPath{get;set;} public override void ExecuteResult(ControllerContext context) { if (context == null) throw new ArgumentNullException("context"); HtmlCtl.CompiledControl.Render(ctl, context.HttpContext.Response); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreate Instance Aspx Page of Ascx Control In a Back End Class without Loading FilePath
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGlenn
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. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COAfter using my solution for a few weeks I would recommend against it. The extra compile steps and occasional bugs greatly out weigh the small benefits of this method.
 singulars
 PostPostId
 PO
 UserUserId
 USGlenn

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.