Don't be ridiculous. In general, storing images in a DB isn't best practice, but there are certain situations where it is extremely useful (for example, versioning of artwork etc).
On Sun, Jan 31, 2010 at 8:10 AM, Gunawan Hadikusumo < [email protected]> wrote: > It is a worst practice to keep images on Database.......... better put in > seperate folder name and name that folder using GUID. > > > On Sun, Jan 31, 2010 at 9:25 AM, Derek <[email protected]> wrote: > >> I'm an old-school ASP developer trying to wrap my head around .Net >> development. I can probably figure out a way to do the following, but >> I'm wondering about the BEST way to do it. Here's the issue; >> >> I have a site where users can upload images in various areas, and to >> keep things clean I am saving the images in image columns in a SQL >> Server 2005 db. I am using the Telerik tools, including the >> RadBinaryImage, and that part is working properly. >> >> When the image is uploaded, I'd like to; >> >> - create an appropriate-sized thumbnail and save that in a thumbnail >> image field >> - with the full-size image again, resize the image within specified >> bounds, add a transparent image as a watermark, and save that image >> back to the db >> >> I have access to Persits ASPJpeg, but from my reading I also believe >> that the .net imaging library can do the resizing and combining for >> me. My questions are; >> >> - where is the best place to do this? >> - can I do it with a general class function that could be called for >> different tables? (there are several tables where images may be saved, >> but the image column names are the same in each) >> - would it be better to do it with the .net image library, or would >> you recommend using a third-party object library like ASPJpeg? >> - any code examples that would explain the process for any/all these >> steps? >> >> Thanks in advance, and any and all assistance is greatly appreciated. >> >> >
