Import Statement

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Debora
    New Member
    • Aug 2007
    • 3

    Import Statement

    I am trying to use the import statement to access my class object, but it does not recognize the classes -- . In order words the intellisense does not show my project name
  • kestrel
    Recognized Expert Top Contributor
    • Jul 2006
    • 1071

    #2
    Originally posted by Debora
    I am trying to use the import statement to access my class object, but it does not recognize the classes -- . In order words the intellisense does not show my project name
    Hey Debora, Welcome to the Scripts.
    Do you think i could have a bit more detail on what you are trying to accomplish? Your description is pretty vague.

    --
    Kestrel

    Comment

    • Debora
      New Member
      • Aug 2007
      • 3

      #3
      I created a Web Application named Debora_CRPP. I also created several classes. One of which was called clsUtilities. After creating a new WebForm I attempted to add an import statement to access the clsUtility. When I typed the import statement the intellisense showed ASP, Microsoft and System. My project name was not listed. So, I typed it in anyway and it shows with the green squilly lines. The comments reads "Namespace or type specified in the imports 'clsUtility' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.

      Comment

      • kestrel
        Recognized Expert Top Contributor
        • Jul 2006
        • 1071

        #4
        Im going to move this thread to the ASP forum

        Comment

        • jhardman
          Recognized Expert Specialist
          • Jan 2007
          • 3405

          #5
          Originally posted by kestrel
          Im going to move this thread to the ASP forum
          and I'm going to move it to the .NET forum, as ASP classic does not use classes.

          Comment

          • kestrel
            Recognized Expert Top Contributor
            • Jul 2006
            • 1071

            #6
            Go for it, i have to idea where things go, unless its in plain print.

            Comment

            • jhardman
              Recognized Expert Specialist
              • Jan 2007
              • 3405

              #7
              Originally posted by kestrel
              Go for it, i have to idea where things go, unless its in plain print.
              Oh I don't expect you to see the difference. You'd be surprised (except you probably wouldn't) how many .NET users post C# questions in the asp forum, and we scratch our heads and think "What in the world could that mean?" I do expect them to see the difference, except that microsoft insists on discontinuing the old technology and calling the new technology the exact same thing, so the newbies should be excused too. the whole fault lies with microsoft. In the end, that's what it all boils down to.

              Jared

              Comment

              • Debora
                New Member
                • Aug 2007
                • 3

                #8
                The answer was I had put the clsUtility in the App_Data folder instead of the App_Code folder.

                Comment

                • jhardman
                  Recognized Expert Specialist
                  • Jan 2007
                  • 3405

                  #9
                  Originally posted by Debora
                  The answer was I had put the clsUtility in the App_Data folder instead of the App_Code folder.
                  Sorry we weren't more help but glad to see you found the solution anyway.

                  Jared

                  Comment

                  Working...