Using NameSpace members In another namespace

[yllanger]

Hi guys, I have come yet again to ask another question. :D

The scenario is like this.

Using Parser;
namespace Crawler
{
   public void Main()
{
     MyUri uri = new MyUri();
     Parser p = new Parser();
     p.GetPage(uri);
}
 
}
 

And I have another namespace which is the parser

namespace Parser
{
 
class FormParser
{
     public void GetPage(url)
     {
    //whatever coding here...
      }
 
}
}
 

And I would like to be able to use uri in Parser. However when I try that, I get this error message: Member "'Parser.FormParser.GetPage(Crawler.MyUri) cannot be accessed with an instance reference; qualify it with a type instead"

I would like to know if there is a better way of doing what I am trying to do. Any help, comments and suggestions would be greatly appreciated. Thank you. :)

[GaryTexmo]

I think your problem is that parser is both a type and a namespace. Line 7 of the first code block defines a variable of type Parser, but that's your namespace, defined on line 1 of the second code block.

In your main file, you'll need a "using Parser;" statement as well as a project reference to whatever project FormParser is in (if it is in a separate file). Then line 7 would become...

FormParser p = new FormParser();

Or, if you didn't have the using statement and/or wanted to be more specific...

Parser.FormParser p = new Parser.FormParser();

[tlhintoq]

Using Parser;
namespace Crawler
{
   public void Main()
{
     MyUri uri = new MyUri();
     Parser p = new Parser();
     p.GetPage(uri);
}
 
}

The problem here is that you shouldn't make a new Parser. Parser is a namespace, not a class object. You would make a new Parser.FormParser. You can either specify "Parser.FormParser" (just to make sure it is not confused with any other namespac'es "FormParser" class, or since you have already specified you are *using* the namespace Parser you can just make a new FormParser()

namespace Parser
{
 
class FormParser
{
     public void GetPage(url)
     {
    //whatever coding here...
      }
 
}
}

You need to make the class FormParser *public* if you want other classes to be able to see it and make new instances of them.

Putting that all together should look something like this...

Using Parser;
namespace Crawler
{
   public void Main()
{
     MyUri uri = new MyUri();
     FormParser fp = new FormParser();
     p.GetPage(uri);
}
 
}
 
namespace Parser
{
 
public class FormParser
{
     public void GetPage(url)
     {
    //whatever coding here...
      }
 
}
}

Let me make another suggest: Not so many namespaces and not such generic namespaces. I'll guarantee you're not the first guy to make a Parser or Crawler namespace. Hopefully you will enjoy coding so much that these are not the only classes you make. This scheme will quickly get out of hand if you don't plan now how you will grow your common code. What about this sort of thing?

Using yllanger.web;
public void Main()
{
     // This is the main of  your app, it doesn't need it's own namespace
     // It will already be in the namespace of your project name.
     MyUri uri = new MyUri();// your *using* statement keeps you from having to specify this as   yllanger.web.MyURI   but that is what it really is
     yllanger.web.FormParser fp = new yllanger.web.FormParser(); // just to be specific
     p.GetPage(uri);
}
 
namespace yllanger.web
{
public class FormParser
{
     public void GetPage(url)
     {
    //whatever coding here...
      } 
}
 
public class MyUri
{
    // build your 'MyURI class
}
// put all your other 'web' classes inside this namespace
}
 
namespace yllanger.Windows.Forms
{
  // put all your custom windows forms classes here
  //  Notice how we are keeping synchronous with
  //  System.Windows.Forms   just so we don't confuse ourselves
  //  6 months from now, wondering where we put a given class
}
 
 
 

You are now on your way to your own framework.