In Lewis Carroll's Through the Looking Glass, Humpty Dumpty redefined the meaning of the word "glory" to mean "a nice knock-down argument". When Alice, to whom he was speaking, protested that that was not the correct meaning of the word, Humpty Dumpty replied:
"When I use a word," Humpty Dumpty said in a rather scornful tone, "it means just what I choose it to mean -- neither more nor less."
In the same way, when web hosts use the word "unlimited" to say that you get "unlimited disk space" or "unlimited bandwidth" (or its equivalent "unlimited data transfer"), the word "unlimited" usually gets redefined to some other meaning, at the web host's discretion. The exact meaning varies from host to host, in the spirit of Humpty Dumpty, but it invariably means the opposite of the "unlimited" found in the English language."
(Thanks to http://www.thesitewizard.com/webhosting/unlimited-space-bandwidth.shtml)If you are interested in some of the Patterns (e.g. Dtos and how they should be populated by Transfer Object Assemblers), mentioned above, see (Gasp! It's not from Microsoft!) the Java J2EE patterns site at http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObjectAssembler.html.
<%--
Name: GenerateUIFromDtoViaReflection_Draft0-1
Author: David Klein
Description: Using Reflection to Generate UI from Dto Assembly when has correct Mapping Attributes
Note: Make sure that referenced assemblies are in the GAC or in the CodeSmith /bin directory so they can be
resolved correctly.
--%>
<%@ CodeTemplate Language="C#" TargetLanguage="Text" Src="" Inherits="" Debug="True"
Description="Template description here." %>
<%@ Property Name="AssemblyPath"
Type="System.String" Default="c:\temp\MyDtoAssembly.dll" Optional="false"
Category="Strings" Description="The path to your dto."
Editor="System.Windows.Forms.Design.FileNameEditor" %>
<%@ Property Name="TypeName"
Type="System.String" Optional="false" Category="Strings"
Description="Fully qualified name for your Dto" %>
<%@ Assembly Name="System.Data" %>
<%@ Assembly Name="Oakton.Sample.Common.Dto" %>
<%@ Assembly Name="Oakton.Framework.Common" %>
<%@ Assembly Name="Oakton.Sample.Common" %>
<%@ Import Namespace="System.Reflection" %>
<%@ Import Namespace="Oakton.Sample.Common.Dto" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="Oakton.Framework.Common" %>
<%@ Import Namespace="System" %>
<%@ Import Namespace="System.Windows.Forms" %>
<%
//Debugger.Break();
MessageBox.Show(TypeName);
Assembly assembly = System.Reflection.Assembly.LoadFile(AssemblyPath);
Type objectType = assembly.GetType(TypeName);
//System.Type objectType = System.Type.GetType(TypeName);
//System.Windows.Forms.MessageBox.Show("Is null {0}", (objectType == null).ToString());
PropertyInfo[] properties = objectType.GetProperties();
foreach(PropertyInfo property in properties)
{
//Add Property of Dto to UI
string fieldName = property.Name;
%>
<div class="row">
<label>
<asp:Literal ID="<% =fieldName %>Literal" runat="server" Text='<%%$ Resources:CommonResources, CustomerDetail_<% =fieldName %> %%>' />
</label>
<span class="input">
<asp:TextBox runat="server" ID="<%=fieldName%>TextBox" Text='<%%# Bind("<% =fieldName %>")%%>'
SkinID="short" />
</span>
</div>
<%
}
%>
///
/// Territory name - incorporates property from related entity Territory (name) to allow server-side queries
///
public string TerritoryName
{
get
{
return Sales_SalesTerritory == null ? string.Empty : Sales_SalesTerritory.Name;
}
}
Here is a sample of how to do option number 5 using this shorthand projection technique. NOTE: This sample uses System.Linq.Dynamic from 101 LINQ Code Samples which (if you have Visual Studio 2008) can be found in %ProgramFiles%\Microsoft Visual Studio 9.0\Samples\1033. System.Linq.Dynamic allows you to pass non-typed values (ie just strings) for your sort expressions.
See when using Server-side sorting with System.Linq.Dynamic, you can also put the correct full-qualified sort expressions in your templated control (e.g. GridView) for nested entities in your projection. Note the sort expression in the code below which is consumed by System.Linq.Dynamic to generate the correct Sql:
/// <summary>
/// Project -> Sort -> Extract to avoid the need for a separate projection entity.
/// </summary>
/// </pre><param name="criteria">
/// <param name="totalCount">
/// <returns></returns>
public List<sales_customer> SearchCustomer(CustomerSearchCriteriaDto criteria ,out int totalCount)
{
var query =
from customers in _context.Sales_Customer
join territories in _context.Sales_SalesTerritory on customers.Sales_SalesTerritory equals territories
join customerType in _context.LookupValue on customers.LookupValue equals customerType
select new {Customer = customers, TerritoryName = territories.Name, CustomerTypeName = customerType.Value};
if (criteria.AccountNumber.Length > 0)
{
// Account Number
query = from customer in query
where customer.Customer.AccountNumber.Contains(criteria.AccountNumber)
select customer;
}
if (criteria.TerritoryId.HasValue)
{
// Territory
query = from customer in query
where customer.Customer.TerritoryId == criteria.TerritoryId
select customer;
}
if (criteria.CustomerTypeLookupId.HasValue)
{
// Customer Type
query = from customer in query
where customer.Customer.CustomerTypeLookupId == criteria.CustomerTypeLookupId
select customer;
}
totalCount = query.ToList().Count();
//Run server side query to get correct 10 records to display to user based on paging and sorting
//criteria.SortExpression is just a string.
return query.OrderBy(criteria.SortExpression).Skip(criteria.StartRowIndex)
.Take(criteria.MaximumRows).Select(newCustomer => newCustomer.Customer).ToList();
}
