Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Wes' Puzzling Blog

... trying to solve the puzzles of .NET

  • TinyUrl

    TinyUrl is a service that allows you to turn those huge wrapping urls like this:

  • Completely online email clients

    I'm been trying to find the best completely online email client such as oddPost and fastmail.  I like oddPost's GUI but it doesn't have all the features, I like fastmail's features but it doesn't have a very good GUI.  Does anyone else use a completely browser based email client online that has a nice GUI and has a nice set of feature, especially the ability to check other pop/imap accounts?

  • Over write text in a window's console application

    Today I had a need to display a counter on a Console application and I was trying to think of a way to over write the existing number with the new number in the console window, using C#.  So after thinking about it for a minute it came to me, just write backspace characters.  Well anyways just incase anyone would ever need this here is a simple example: 

  • NiftyPortal

    I stumbled upon this pretty cool online news reader a while ago and I just happened to stumble upon it again and I figured that I would pass it along.  NiftyPortal

  • Using Embedded Images in ASP.Net V2

    Thanks to Yves and Peter for the advise I utilized your advise to create a new version my embedded Image example. I did switch to an ashx file, I didn't even know about this file type until now. I'm no longer passing in the assembly as a parameter but I didn't want to put the assembly in the config file either, so I figured that I would just test for the image by the passed in name in all the assemblies loaded into that AppDomain. There shouldn't be to many right? But you do have to make sure that embedded image has a unique name, that shouldn't be to hard though because you can prefix it by your namespace.

    <% @ webhandler language="C#" class="ImageHandler" %> 
    
    public class ImageHandler : System.Web.IHttpHandler 
    { 
      public void ProcessRequest(System.Web.HttpContext context) 
      { 
        string image = string.Empty;
        System.IO.Stream stream = null;
          
        try
        {
          context.Response.Clear();
    
          // Get Image Name from request
          image = context.Request["img"].Replace("/"".");   
      
          // Find image in loaded assemblies
          foreach(System.Reflection.Assembly asm in System.AppDomain.CurrentDomain.GetAssemblies())
          {
            stream = asm.GetManifestResourceStream(image);
            if(stream != null)
              break;
          }
          
          // Throw exception if image is not found
          if(stream == null)
            throw new System.Exception("Image not found in loaded assemblies");
                
          // Create an Image object from the stream
          System.Drawing.Image img = System.Drawing.Image.FromStream(stream);
          
          // Save the Image stream to the output stream
          img.Save(context.Response.OutputStream, System.Drawing.Imaging.ImageFormat.Gif);
        }
        catch(System.Exception ex)
        {
          context.Response.Write("Exception: <BR>image = " + image + "<BR>" +
            ex.Message + "<BR>" + ex.StackTrace.Replace("\n""<BR>"));  
        }
        finally
        {     
          context.Response.End(); 
        }; 
      } 
       
      public bool IsReusable 
      { 
        get { return true; } 
      } 
    }
    

    So what do you guys think about revision 2?

  • Using Embedded Images in ASP.Net

    This will prevent me from having to copy all the images; all I would need to copy is the Assembly and the image.aspx file.  What do you guys think?  Does anyone see any potential problems with this?