The Lazy Techie ...!

The pop-out menus are displayed as white boxes, when Internet Explorer 8.0 (IE8) used to view an ASP.NET Web page that has dynamic menus

2009-07-07T18:43:00.002+05:30

Currently I’m working on a support project which I developed in ASP.Net 2.0. This application has relied on AJAX and ASP menu controls provided by Microsoft.

The recent issue I faced was application compatibility with Internet Explorer 8 (IE8). The total appearance of the site was improper and, asp dynamic menu control had problem. The pop-ups were displayed as white boxes. It would have been tedious job for me to site and change all style sheets to make it IE8 compactable. But following blog helped me in this situation.

http://blogs.msdn.com/giorgio/archive/2009/02/01/asp-net-menu-and-ie8-rendering-white-issue.aspx

I have added following code into the master page master page of application, and my site is back!
<meta equiv="X-UA-Compatible" content="IE=EmulateIE7">
Check out Microsoft KB on this issue, http://support.microsoft.com/kb/962351

DotNetNuke Related Links

2008-06-20T19:01:00.000+05:30

Creating a DotNetNuke® Module - For Absolute Beginners!
http://www.codeproject.com/KB/custom-controls/Creating_A_DNNModule.aspx

Where are my Designer.CS Files ?

2008-05-21T16:08:00.000+05:30

Last month when I was working on a ASP.NET 2.0 Maintanace Project, It required to add some custom attributes to a set of text boxes. The custom attribute class was already available, i wanted to specify the custom attribute to the textbox at design time. As usual i went in search of designer.cs file for the aspx page and found no files with that extension.

After couple of Googling and great help from my old pals, I figure out that I was working on a "Website Project" created with VS2005, rather than a "Web Application Project".

Web Site projects have no project file (this is incredibly, unbelievably annoying in a lot of scenarios) and are solely based on what’s in the filesystem (ditto).

Web Application projects have a physical project file and resemble the “classic” Visual Studio 2003 web project model.

Read More on the Differance at "Coding Mixture's Blog" : http://maordavid.blogspot.com/2007/06/aspnet-20-web-site-vs-web-application.html

Runtime binding & Compile time binding

2008-03-20T14:08:00.000+05:30

Compile time binding to a method signature and run time method
For a method invocation a1.method(list-of-params) :

1) At compile time the DECLARED classes of the variables which serve
as parameters in the method invocation are used to choose the most
specific method signature visible from the DECLARED class of variable
a1 - the choice set includes all visible inherited methods. The
return type is not considered at this stage.

2) At run time an exact match of the compile time descriptor (signature
selected above plus return type) is sought in the Actual class
associated with the object instance held in variable a1, and, if
needed, then is sought in its parent and ancestor classes in order.
The classes of the actual parameters are NOT considered at run time.
An example that might be surprising at first is:

class A {
(0) public void method1(A a1, A a2)...
public void method1(A a1, int i)...
}
class B extends A {
(1) public void method1(A a3, A a4)...
(2) public void method1(B b1, B b2)...
public static void main(String [] args) {
A a6;
B b3, b4, b5;
a6 = b3;
(3) a6.method1(b4, b5); ....
}
}

The method invocation at (3) causes the method at (1) to be invoked at
run time, even tho (2) is a more specific and matching method in the
class of the invoking object instance (object b3).

This happens because compile time analysis selects the method signature
(0) as the only visible applicable signature in the declared class (A)
of variable a6, which is used to invoke the method. At run time, this
signature is used to select (1) since it matches the selected
compile-time descriptor (signature + return type).

Note : This content is copied from another Blog/Site/Tutorial, this is just for informative purpose

SharePoint Portal Server: What is it?

2006-06-19T15:48:00.000+05:30

SharePoint Portal Server is an application built on top of Microsoft Windows SharePoint Services. Windows SharePoint Services is a technology you get in Windows Server 2003. It is an engine for serving up in a very scalable, very available, very self-serviced and extensible way, tens of thousands of Web sites to hundreds of thousands of users. The sites come to you without you doing anything extra out-of-the-box with document collaboration, information sharing, and team productivity tools. Using SharePoint sites for sharing-type applications or collaboration activities, instead of file shares, is sensible and effective.

SharePoint Portal Server 2003 provides multifeatured, collaborative portal pages by unifying and enhancing the features and capabilities of Microsoft Windows SharePoint Services and by adding additional functionality and management controls to SharePoint sites.

For More Info : http://www.intranetjournal.com/articles/200502/ij_02_04_05a.html