Help with ASP.Net Resource

Question

OK, I'm struggling to begin converting some of our web customizations to ASP.Net. As part of the process of building our new 9.1 instance, I need to be able to add a column to the "Current Percent Utilization of each Interface" resource that displays the value of a custom interface property for each interface, and this resource has now been switched to ASP.Net. Here's what I have so far... Added the following lines to InterfaceUtilization.ascx: TAG <%# Eval("IF_Tag") %> Added the following line to InterfaceUtilization.ascx.cs: formattedTable.Columns.Add("IF_Tag", typeof(string)); The piece I'm struggling with is the "formattedRow" command in the InterfaceUtilization.ascx.cs file. Here's my best guess at what I need to add, noting the piece that I think I'm missing: formattedRow["IF_Tag"] = String.Format(WhatGoesHere, interfaceID, row["IF_Tag"], paramString); This is a very simple one, but we have some extensive customizations that work quite well coded in classic ASP that will need to be converted to ASP.Net, but I must admit I'm having a hard time following or deciphering the trail of coding needed to make them work with the newer releases of Orion. With ASP, it's fairly simple, as everything you need is in a single file (or includes obvious references to other files), and easy to interpret, but with the new .net arrangement, one has to touch multiple files to implement a simple modification, and I have yet to figure out where everything is and how it all works. I understand the benefits of making the switch, but it makes my hair hurt... :) If any of you .net folks out there can help me out with this instance, I would greatly appreciate it... :)

vhcato · Answer

Thanks, Tim. I was afraid that would be the case. For now, I've resorted to using an ASP resource, but will see if I can build a new ASP.NET resource from scratch that will do what I want. I'm pretty sure I can do it, but the piece thaty concerns me is getting the util bars to display. I'll play around with it when I have some time. :)

vc

tdanner · Answer

I'm afraid this approach isn't going to work. The query used to build this resource (compiled into OrionWeb.dll - not editable in the field) does not include custom properties. The row["IF_Tag"] expression will fail when it tries to render the page.