Archive for June, 2004

New Job

I recently changed companies, and am now in the second day of my new job. Today I actually got to write code, fixing bugs in a project that is nearing the end, almost ready to move to QA. It’s quite exciting at a new place with the new people and the positive potential. I’ve even already learned some new things, I expect it will keep going that way.

Posted on:
Posted in None | Comments Off on New Job

Visual Studio Hampers VB.Net Developers

At the Great Lakes Area .Net users Group meeting last night, during his excellent ASP.Net tips and trick presentation, Jason Beres let us in on a dirty little trick that Visual Studio plays on VB.Net developers (not C# developers though). By default, the editor hides “advanced” properties and methods in the Intellisense.

This setting can be found in the Options dialog box. Tools Menu -> Options -> Text Editor -> Basic:


By default, Hide Advanced Members is checked. I guess the designers were trying to keep VB.Net “friendly” by hiding the complexity? How many times have you as a developer used the Intellisense to explore the options on an object? If you have, you were being shorted.

Posted on:
Posted in Visual Studio | Comments Off on Visual Studio Hampers VB.Net Developers

Using XMLHTTP in Javascript

I attended a terrific meeting tonight of GANG, the Great Lakes Area .Net user Group, based in the Detroit-area. The main presenter was Jason Beres who gave an excellent presentation on ASP.Net tricks, many of them utilizing Javascript. One of my favorites came up in discussion and I agreed to post the code snippet here.

I have used this techniqe mainly on classic ASP pages as a way to populate secondary dropdown lists before ASP.Net and control-based postbacks came along. It still works with ASP.Net… BUT…the secondary listbox is not in the Viewstate so it’s value isn’t set properly when accessing the control in server code on the postback where you handle the data. The secondary list’s selected value is still in the Request.Form collection though. It is still a great technique to use to fetch data from the server without reloading the page.

The technique is IE-only as it uses an ActiveX object (XMLHTTP) in the Javascript. It also uses the XML DOM to parse the response from the server. In this example the server is an ASP page, but it could easily be a web service as well with the addition of one a little more code. This code is related to a previous post where I used VBA to enable Excel to be a web service client.

Here is the Javascript function:

/*  Purpose: Fill secondary list boxes with content
    Arguments:  oItem – the primary dropdownlist object
                sFieldName – The name of the field filling the secondary list
                oDestination – the secondary list object
    Returns: None, fills list box using MSXML*/
function fillSecondary(oItem, sFieldName, oDestination)
  var nValue = oItem[oItem.selectedIndex].value;
  var xmlHTTP = new ActiveXObject(“Microsoft.XMLHTTP”);“POST”, “./listboxesXML.asp”, false);
  xmlHTTP.send(‘<‘ + sFieldName + ‘>’ + nValue + ‘    
  var xmlDOM = new ActiveXObject(“Microsoft.XMLDOM”);


  if (xmlDOM.parseError != 0)
   alert(“Error occurred: ” + xmlDOM.parseError.reason);
   return false;

  var oNode = xmlDOM.documentElement.firstChild;
  var n=0;
  if(oNode != null)
   //Clear out the secondary list box, it might already have items
   oDestination.length = 0;
   while (oNode != null)
    oDestination[n] = new Option(oNode.text, oNode.attributes(0).text);
    oNode = oNode.nextSibling;
    oDestination.selectedIndex = 0;

In the HTML on the page, add an OnChange handler to the primary dropdown list to call the Javascript when the user changes the value:

<FORM id=“Form1“>

<SELECT id=“Primary“ onchange=“fillSecondary(this, “Primary“, document.form1.secondary)“><OPTION value=“1“ selected>A list Item</OPTION></SELECT>

<SELECT id=“Secondary“ name=“Secondary“></SELECT>

The classic ASP page (listboxesXML.asp) called by the Javascript looks like this:

Dim xmlDOM   ‘XML DOM object
Dim oRS    ‘Recordset for child records
Dim sXML   ‘XML String returned to browser
Dim oNode   ‘DOM node containing data for searching
Dim sType   ‘The type/name of the unknown child node

set xmlDOM = Server.CreateObject(“MSXML2.DOMDocument”)
xmlDOM.async = false
xmlDOM.Load Request
xmlDOM.setProperty “SelectionLanguage”, “XPath”
if xmlDOM.parseError = 0 then
 ‘Select the request node
    set oParent = xmlDOM.selectSingleNode(“request”)
    ‘Get the child of the request node
    set oNode = oParent.firstChild
    ‘Store the child’s value
    sSearchValue = oNode.Text
    ‘Store the child’s name
    sType = oNode.nodeName

    set oRS = Server.CreateObject(“ADODB.recordset”)

    ‘Fetch the appropriate data into the recordset using sType to tell which
    ‘  secondary list we should be fetching, in this case it is called “secondarytype“

    ‘ADO Code should be here, removed for brevity

 if not oRS.EOF then
  ‘Build a response XML string
  sXML = “
  while not oRS.EOF
   sXML = sXML & “<” & sType & ” id=””” & oRS.Fields(0).Value & “””>”
   sXML = sXML & Server.HTMLEncode(ors.Fields(1).Value) & “   oRS.MoveNext
  sXML = sXML & “

  sXML = “
  sXML = sXML & “<” & sType & ” id=””0″”>”
  sXML = sXML & “None listed  sXML = sXML & “

 end if
 set oRS = nothing
Response.Write sXML
Err.Raise 1, “ParseError”, “There was a parse error in the request.”
end if

This can be very tricky to debug if you have any problems. Try looking at the xmlHTTP.ResponseText in an alert in the Javascript function to see any 500 errors generated by the server.

Posted on:
Posted in ASP.NET, JavaScript/AJAX | Comments Off on Using XMLHTTP in Javascript