How to define a property as an Image data type?

[Robert W.]

I have a data model that has dozens of properties of most every data type. I
now want to declare a few of these properties as Images but can't seem to do
it.

The approach I thought would work was this one:

private Image _picture;
public Image Picture
{
get
{
return _picture;
}
set
{
_picture = value;
}
}

where I've declared "using System.Drawing" at the top of the file. But it
won't accept it. In fact, Intellisense doesn't even recognize
"System.Drawing ".

Is it not possible to declare a property as an Image type?

----------------------
Robert W.
Vancouver, BC
www.mwtech.com

[Sean Hederman]

It is, but you need to reference the System.Drawing assembly in your
project. By default DLL project don't reference this. Just right-click on
your project in the IDE, and select Add References, choose System.Drawing
from the list in the first tab, and away you go.

"Robert W." <Ro*****@discus sions.microsoft .com> wrote in message
news:60******** *************** ***********@mic rosoft.com...

I have a data model that has dozens of properties of most every data type.
I
now want to declare a few of these properties as Images but can't seem to
do
it.

The approach I thought would work was this one:

private Image _picture;
public Image Picture
{
get
{
return _picture;
}
set
{
_picture = value;
}
}

where I've declared "using System.Drawing" at the top of the file. But it
won't accept it. In fact, Intellisense doesn't even recognize
"System.Drawing ".

Is it not possible to declare a property as an Image type?

----------------------
Robert W.
Vancouver, BC
www.mwtech.com

[Robert W.]

Sean,

Unbelievable, thank you! I would have never known to do this. Why
Microsoft couldn't have included some "smarts" into the Visual Studio UI to
account for it is beyond me.

If I'm ever on "Who Wants To Be A Millionaire" and there's a dotNet question
I don't know, I hope I can use you as my lifeline!!!

Thanks again,

Robert


"Sean Hederman" wrote:

It is, but you need to reference the System.Drawing assembly in your
project. By default DLL project don't reference this. Just right-click on
your project in the IDE, and select Add References, choose System.Drawing
from the list in the first tab, and away you go.

"Robert W." <Ro*****@discus sions.microsoft .com> wrote in message
news:60******** *************** ***********@mic rosoft.com...

I have a data model that has dozens of properties of most every data type.
I
now want to declare a few of these properties as Images but can't seem to
do
it.

The approach I thought would work was this one:

private Image _picture;
public Image Picture
{
get
{
return _picture;
}
set
{
_picture = value;
}
}

where I've declared "using System.Drawing" at the top of the file. But it
won't accept it. In fact, Intellisense doesn't even recognize
"System.Drawing ".

Is it not possible to declare a property as an Image type?

----------------------
Robert W.
Vancouver, BC
www.mwtech.com

[Jon Skeet [C# MVP]]

Robert W. <Ro*****@discus sions.microsoft .com> wrote:

Unbelievable, thank you! I would have never known to do this. Why
Microsoft couldn't have included some "smarts" into the Visual Studio UI to
account for it is beyond me.

Well, to be fair to them, the error message you should have received is
pretty clear:

"The type or namespace name 'Drawing' does not exist in the class or
namespace 'System' (are you missing an assembly reference?)"

It says what the problem is *and* a possible cause.

Note that a namespace may be contributed to by several assemblies, and
you may also want to use an assembly that VS.NET doesn't know about. I
agree that VS.NET could be better here, but I don't think it's being
particularly bad.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Sean Hederman]

"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******** *************** *@msnews.micros oft.com...

Robert W. <Ro*****@discus sions.microsoft .com> wrote:

Unbelievable, thank you! I would have never known to do this. Why
Microsoft couldn't have included some "smarts" into the Visual Studio UI
to
account for it is beyond me.

Well, to be fair to them, the error message you should have received is
pretty clear:

I didn't want to say anything, he said such nice things about me :-)