Actually, this pertains to both the ConTrak Systems and FinGame development projects, as both have need and will use this file uploader.

ASP .Net 2 contains a FileUpload web control, which is very nice for uploading files.  However, VS.Net 2005 beta forces me to jump through hoops I am not about to do (no code-behind pages and everything must be in a code directory).  Therefore, I needed some sort of component to upload files correctly.

With the help of a Microsoft Knowledge Base Article, I began work on a file uploader.  The completed custom web control I created will upload a file a specific directory, as specified by my code.  If the file already exists, the user is asked to confirm the overwrite.  I can also restrict the uploader to upload images only or any one file extension I desire.

The web control is still partly in development, as I must rework some aspects of ConTrak Systems to make everything work with many of the images uploaded for the badge printery.  The control itself is complete, unless something in ConTrak forces me to add lines of code to the control (which I will not do willingly).  The crux of this matter is the size and DPI of all images uploaded to the badge printery.  You see, the DPI will change all my "put this text here" calculations and will be a general mess.  The size itself (width and height) may have some issues with badge printing, but I don't know at this point. 

It DOES look like, however, the badges will be printed at 96 DPI.  I want to get it up to 300 DPI, but this both costs disk space and will require a rework on the part of my badge printer.  I will need to have a few separate calculations for various DPI levels, as I have yet to produce successfully a formula that takes into account image size, DPI, and bit depth (I've tried already with my overkill thumbnailer/mass image watermarker).

Anyway, onwards toward a never-setting sun!  ...and perhaps a job?