Archives

Archives / 2003 / August
  • Databinding Server Controls - Learned Something New

    I was running into an issue databinding an ImageButton's ImageUrl property to a string comprised partly of literal text and partly of a string I was pulling from my ConfigurationSettings.AppSettings collection.  I was using the standard <%# ... %> syntax for the databinding, but the result kept showing my databinding syntax in the button's URL, rather than the actual value.  It seems that while you can do the databinding to the control property, it's all or nothing.  So if you want the string to be:
    <asp:ImageButton ... ImageUrl=”/folder/<%# MyConfigVariable %>/Add.gif” ... />

  • "unexpected error creating debug information"

    I keep running into this issue in my multi-project VS.NET solutions.  For some reason, something is locking the dll(s) in the /obj/ folder of library components.  The fix that I have at the moment is as follows:

  • Caching Best Practices Article on MSDN website

    My first MSDN online article was published this week: ASP.NET Caching: Techniques and Best Practices.  The first half is pretty much well-known info about caching in ASP.NET (at least, it should be well-known to anybody writing ASP.NET applications).  The tips and the best practice pattern are the real valuable parts here for everyone who already knows the caching capabilities of ASP.NET, since these tell you why you should use caching and how to do it the most efficient way possible, which aren't necessarily apparent from the docs.

  • InfoPath Tidbit

    InfoPath forms can only be viewed and filled out by folks who have InfoPath installed... or can they?  As it turns out, InfoPath .xdr files are really just CAB files.  This means you can use the 'expand' utility (in Windows 2000 and later, I believe) to pull out the pieces of the XDR file, one of which contains a definition of the form (actually, one .xsl file per form).  With a little search-and-replace or perhaps another XSL transform, it would not be too terribly hard to convert the input controls used by InfoPath into, say, web controls, allowing the forms to be displayed via ASP.NET.