In .NET 4.0 there is a new option when adding controls to a page or user control: ClientIDMode. This property offers you four choices: Legacy, Static, Predictable, Inherit. Previously it was almost impossible to find the id of a control in a normal matter such as jQuery. Using
Choosing Legacy will continue to issue an ID in the same manner they were generated in previous version of ASP.NET, by concatenating the ID values of each parent naming container with the ID of the control. Setting the property to Static will use the exact value of the ID property of the server control. Predictable is used for controls that are data-bound controls such as repeater and also makes use of a ClientIDRowSuffix property. Using Inherit makes the control ID property use the setting of its parent control.
In the example below, two lists are created inside the ContentPlaceHolder of a page using the same DataSource. The first is using the default and the second uses the new property with Static set as the value.
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<asp:XmlDataSource ID="LinkData" runat="server" XPath="Colors/Color">
<Color Name="Green" />
<asp:BulletedList ID="uxList" DataSourceID="LinkData" runat="server" DataTextField="Name" />
<asp:BulletedList ID="uxListStatic" ClientIDMode="Static" DataSourceID="LinkData" runat="server" DataTextField="Name" />
Here is the output of the page in HTML
And the corresponding view in the browser
Because of the generated tag on the first list jQuery can’t find the control to append to.
Scott Guthrie has an article up on his website discussing the new auto-start feature of web applications that will be available in IIS7.5 with ASP.NET 4.0. I just learned about this last week at the Southern Fried Road Show.
I am going to try and enlist the 960 Grid System on a website I am working on.
“The 960 Grid System is an effort to streamline web development workflow by providing commonly used dimensions, based on a width of 960 pixels. There are two variants: 12 and 16 columns, which can be used separately or in tandem.”
monoTouch enables applications developed in any .net language to run on the iPhone. Significantly, monoTouch provides .net bindings to native API, allowing application developers will have access to iPhone specific functionality from within their .net applications. monoTouch integrates with both the free MonoDevelop IDE as well as Apple’s XCode toolkit
Interesting article comparing MVC vs. WebForms and a third option known as ZeroForm.
.NET 4.0 and VS 2010 introduce a new feature for the Entity Framework called model first. In addition, you will now be able to have a code only model. Written with POCOs and a simple class derived from ObjectContext and you are on the way…
Yesterday i was attempting to use a stored procedure with the Entity Framework through the “function import” features and couldn’t get the auto-gen feature to expose the function on the Context. The stored procedure was returning a scalar value which at this point doesn’t seem to be supported through auto-gen. Choosing an Entity, however works fine. Further digging this morning led me to this article on the ADO.NET team blog explaining the issues with return types and stored procedures in Entity Framework. The article also links to another great article showing how to return custom types two ways: one way through the entity framework itself, the other through the use of extension methods.
ADO.NET Entity Framework Extensions
T4 code generation has been on my short list of things to look into but keeps getting put off as i navigate down some other endless path. Meanwhile, I found a nice article on using T4 to generate stored procs for CRUD operations for the Entity Framework.
Entity Framework Stored Procedure Generation
Ran into an issue on a website where the Session was timing out yet the forms auth ticket was still valid which was causing errors. Here is one solution:
The GU also mentions some of this in the post and in digging through all the comments.