Namespaces and visibility.

I'm trying to derive my own class from System.Drawing.Image which represents a bitmap stored in a DirectDraw offscreen surface.

But when I compile it gives me the error
'System.Drawing.Image.Image()' is inaccessible due to its protection level
for every constructor of my class.

Now I would normally guess that this means the constructor is protected, internal or private. But:
It can't be protected, my derived class would have access to it.
It can't be private, else no class could be derived from Image (there's no friend keyword in C#, right?).
It can't be internal, because a) I placed my image class in System.Drawing and b) System.Drawing.Imaging.Metafile is derived from Image and has access.

Why does it deny me the access? How can I solve this problem?

Code:

---

public class DdImage : System.Drawing.Image
{
        //...
        public new int Flags
        {
                get
                {
                        return 0;
                }
        }

        public new Guid[] FrameDimensionsList
        {
                get
                {
                        return null;
                }
        }
        // etc.
}

---

Because System.Drawing.Image is an abstract class.

I know that. I'm deriving from it. I never call any Image constructor explicitly. But the compiler gives me errors!

Ok, as it is I'll assume Image is somehow guarded in it's namespace (still seems strange to me).

Damn, that would have been nice.

You might want to use the Bitmap class instead. I think there is the same functionality and you can create an instance of it.

Code:

---

public new int Flags
        {
                get
                {
                        return 0;
                }
        }

---

what does this do? proprieties aren't in the format of:
<access> <type> <name> ? what does the new do?

this MIGHT help...

http://radio.weblogs.com/0111551/sto...ctClasses.html

Quote:

---

what does this do? proprieties aren't in the format of:
<access> <type> <name> ? what does the new do?

---

The new keyword is there to hide a member with the same name in the base class.

Yep, it won't allow me nothing, it won't allow me override, so I have to use new.

Bitmap does too much of its own. I don't want it allocating memory behind my back.

Quote:

---

Originally posted by kovan
this MIGHT help...

http://radio.weblogs.com/0111551/sto...ctClasses.html

---

Thanks, but it didn't.

Could it be that I have to implement ALL public methods and properties from Image, even when they are derived from another class (MarshallByRefObject or Object)?