Category: ASP.NET

I’ve been fight with creating Custom Server Controls (Custom Controls).  I have create one Custom Control that inherits from CompositeControl.  And create another control that inherits from the previous created custom control.  Let’s just say the process of create a custom control is not very intuitive.  Let’s not even talk about creating a customer control that inherits from another customer control.  Holly !@#$.

 

I will probably create custom controls again and when I do hopefully the following resources will be helpful.

 

Writing Good ASP.NET Server Controls
http://blog.tatham.oddie.com.au/2007/11/02/writing-good-aspnet-server-controls/

 

ASP.NET Custom Controls: Part 2 – ViewState
http://dotnetslackers.com/articles/aspnet/ASPNETCustomControlsPart2.aspx

 

ViewState Management
http://www.coatta.ca/Main/Technology/DotNet/ViewState.html

 

Composite controls that do their own databinding
http://weblogs.asp.net/asmith/archive/2004/08/29/222442.aspx

 

Control Building and ViewState Lesson for the Day
http://scottonwriting.net/sowBlog/archive/10062004.aspx

 

A Crash Course on ASP.NET Control Development: Building Composite Controls
http://msdn.microsoft.com/en-us/library/aa479016.aspx

My environment: Visual Studio 2008 (VS.NET), Vista, IIS7, ASP.NET. 

I have a situation when I’m debugging ASP.NET and after about 90 seconds of stepping through code the debugger suddenly stops and detaches.

 

Based on info from others, it seems that the underling problem is Vista and Internet Information Server 7 (IIS7).  There are two setting in IIS7 for Application Pools that can create this problem: Ping Enabled and Ping Maximum Response Time.  The default for Ping Maximum Response Time is 90 sec.  By changing these values should resolve the problem.  The references below probably provides a better overview of the problem.

 

Reference:

 

My web application times out when debugging in IIS7

I have the situation where I need to load a JavaScript dynamically.  All the JS files are in the ClientScript directory (http://www.somewebsite.com/ClientScripts/Validation.js).  The ASPX page that references the client scripts could be anywhere, multiple folders (directories) down in the site or in the application root.  I would like a simple way of referencing the the application root.  The magic to this is the ~ (Tidle). The ~ resolves to the root of the current application. 

 

The following line allows me to reference the application root

this.ClientScript.RegisterClientScriptInclude("Validation.js", Page.ResolveUrl("~/ClientScripts/Validation.js"));

 

And here is the results in the HTML file.

<script src="/ClientScripts/Validation.js" type="text/javascript"></script>