can i convert System.Web.UI.WebControls.Image to bytes

Question

4.00/5 (1 vote)

See more:

, +

Hi All,

Can i convert System.Web.UI.WebControls.Image to bytes so that i can save it to database.

Actually I am getting my image as a response of an aspx page (getimage.aspx), see below.

// send the image data down to the client
Response.Clear();
Response.AddHeader( "Content-Disposition", "attachment; filename=m-View_Image.jpg" );
Response.ContentType = "image/jpeg";
Response.TransmitFile( fileName );

// Writes the specified file directly to an HTTP response output stream
// without us having to buffer it in memory.
HttpContext.Current.ApplicationInstance.CompleteRequest();

I want to read that image and save it in database
I can display the image like below:

string url = "http://..../getimage.aspx"

Image img = new Image();
img.ImageUrl = url;
img.DataBind();

But how to convert the image coming as aspx response in to bytes ?

Please help me.

Thanks in Advance.

Posted 8-Jun-11 19:32pm

saxenaabhi6

Updated 8-Jun-11 20:19pm

Ramalinga Koushik

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-06-08T19:48:00

Everything is possible. However, I strongly recommend not to serialize UI controls.

UI can be a temporary item of a software project. If you serialize UI, you won't be able to upgrade it in a backup-compatible manner. It's very likely that later on you will need to migrate to a different UI library or a whole platform. You database, busyness logic and other application specific code will survive… in you refrain from creation of hard coupling of UI with data model.

What you need is loose coupling, see http://en.wikipedia.org/wiki/Loose_coupling[^].

Instead of serializing the UI, create a logical data model of you UI. It will be tightly bound to your functionality and not to UI elements. The model should be composed of pure data classes/structures. The relationship between data model and UI will be reduced to two operations: data to UI (population) and UI to data (acquisition). Yes, this is extra work, but it will pay very well of in near future.

Serialization of such model won't be a problem. I suggest you don't do it manually. My best advice is using Data Contract, see http://msdn.microsoft.com/en-us/library/ms733127.aspx[^].

This method of serialization is the most non-intrusive. You don't have to modify any of your types to make them serializable with System.Runtime.Serialization.DataContractSerializer or System.Runtime.Serialization.Json.DataContractJsonSerializer; instead, you only add attribute to your types and members.

As your thinking about UI serialization shows pretty good confusion about application architecture, I would advice to familiarize yourself with the architectural patterns I listed in my past solution:
how to control Controlls of a user interface form through Functions (methods)[^].

Here is the explanation of architectural patterns in general: http://en.wikipedia.org/wiki/Architectural_pattern_(computer_science)[^].

You don't have to learn them, but you really need to get a good idea on how robust application architecture should be build.

—SA