does not implement interface member

This error is in this c# code that I don't normally see.

    public class admin_systems_and_versions_aspx : global::Admin, System.Web.IHttpHandler {
        private static bool @__initialized;

Error      3      'ASP.admin_systems_and_versions_aspx' does not implement interface member
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
teststatus2production\7e352623\d1efa770\App_Web_xslh3hfa.0.cs      157      

I tried removing the temporary files and that did not work.
Who is Participating?
Carl TawnConnect With a Mentor Systems and Integration DeveloperCommented:
You need to implement the method defined by the interface. But first you need to check if you have a class called "Admin_Systems_and_Versions" and that it does indeed implement the IHttpHandler interface. If its not your code itself throwing the error then it will be some problem with one of the frameworks base classes.
Steve BinkCommented:
Did you implement the IsReusable property for your class?
drlewickiAuthor Commented:
How? In what page?
The new generation of project management tools

With’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Carl TawnSystems and Integration DeveloperCommented:
The error message would suggest that you have a page called "Admin_Systems_and_Versions.aspx" that is marked as implementing the IHttpHandler interface, but doesn't implement the IsReusable method of the interface.
drlewickiAuthor Commented:
what is the solution?
It appears that you have defined a class like this:

public class admin_systems_and_versions_aspx :  global::Admin,  System.Web.IHttpHandler

this indicates that your class is implementing the interface

and in order to implement that Interface, you MUST implement a method:

public void ProcessRequest(HttpContext context) {


and a property:

public bool IsReusable {
    get {
        return false;

Steve BinkCommented:
An interface is only a contract between the ASP.NET engine and the developer.  The engine agrees to provide specific functionality to your application through this interface, and you agree to give it the specifics of how you want it to work.  Every interface is going to have some property or method you need to implement in your application's code.  In this case, there are only the two items referenced at the link I provided and demonstrated by Arthur_Wood.

... here, when they say "implement", they are meaning:
    "define", "create", "write", "include", "specify"

... not what the English verb "implement" generally means:
    "perform", "put into effect", "carry out", "execute"

You don't ever have to execute the method, but in order to fulfill the Interface's contract, you must define the method to your class that implements an interface.

Steve BinkCommented:
>>> ... here, when they say "implement"

Another great lesson in basic assumptions.  I've been using the language so long, I had not even thought that someone could misconstrue that concept.

In programming, the best definition I have seen for "implement" is "providing a practical means for accomplishing something".  An interface is merely a skeleton.  It does not actually include code to *do* anything, but instead provides the overall structure that must be followed in order to do a particular thing.  When you define a class as inheriting an interface, it is inheriting that general structure.  Still, there is no need to provide the code for it.  Providing that code is referred to as "implementing", or an "implementation" of, the interface.

Think of it in the context of a car.  The car interface says you must have a steering wheel, an engine, and brakes.  The interface does not actually create those items - it only mandates their existence.  Each car manufacturer can choose to implement this interface in a variety of ways, but every car *must* have those properties.
All Courses

From novice to tech pro — start learning today.