Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Problem with declaring namespace

Problem with declaring namespace

Scheduled Pinned Locked Moved ASP.NET
helpcsharpdotnetvisual-studiocom
1 Posts 1 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    Eagle32
    wrote on last edited by
    #1

    Hi, I am trying to use an External Web Service in my Web Site application i am developing. The problem occurs when declaring the namespace such as this: using namespace.classname Error: The type or namespace cannot be found. Does this mean i have to put the C# class file into App_Code folder? I was wondering if somebody could help me please in terms of replicating the problem i am facing? I am trying to use the following web service: IMDB Web Service I have followed the instructions but it still doesnt work. I have even copied the following code from the generated output file which you will see when you access the above URL into my global WebConfig file and it still doesnt work. I am using .NET Framework 3.5 and VS 2008. Thanks & Regards,

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups