Thursday, June 19, 2008

WCF - The type name ServiceReference1 does not exist in the type Namespace.ClassName

This is a short blog post about a strange error when adding a WCF service reference. A WCF service was created and I wanted to add a service reference to a client project. I added the reference through Visual Studio and everything went fine until I compiled. Then I got this error:
Error    3    The type name 'ServiceReference1' does not exist in the type 'MyWorld.MyWorld' ...\Service References\ServiceReference1\Reference.cs

I found that this is caused by me having the same namespace name as class name (MyWorld.MyWorld = Namespace.ClassName). Change your namespace to a name that is not the same name as your class and this will compile.

at

26 comments:

  1. Doguhan Uluca26 August, 2008 00:35

    Very good find. Saved me a lot of heartache.

    ReplyDelete
  2. Anonymous28 August, 2008 21:27

    Excellent, been wracking my head over this on and off for a few hours!

    ReplyDelete
  3. Anonymous15 October, 2008 05:14

    Thanks for posting this. You solved my problem.

    ReplyDelete
  4. Anonymous23 October, 2008 18:30

    I love you for this.

    ReplyDelete
  5. Unknown02 December, 2008 16:14

    Thanks a lot for this ! :)

    ReplyDelete
  6. Anonymous08 January, 2009 10:00

    Great find. Saved me major pain.

    ReplyDelete
  7. Anonymous08 January, 2009 10:01

    Great find. Saved me major pain.

    ReplyDelete
  8. Anonymous21 January, 2009 14:25

    Great:) Solved my problem.

    ReplyDelete
  9. Anonymous09 February, 2009 13:04

    Great Work!!

    ReplyDelete
  10. Anonymous16 March, 2009 16:06

    Another thank you... worked a charm!

    ReplyDelete
  11. Anonymous01 June, 2009 08:02

    Thanks
    I had been going at this for over an hour.

    ReplyDelete
  12. Unknown01 July, 2009 15:22

    Thanks a lot, my pain has gone

    ReplyDelete
  13. Anonymous04 August, 2009 16:21

    That was my headache, too! Thx!

    ReplyDelete
  14. WhiteRussian15 October, 2009 22:23

    This comment has been removed by the author.

    ReplyDelete
  15. seezeey27 October, 2009 20:17

    Thanks for saving me lots of time, great post...

    --engin

    ReplyDelete
  16. Unknown26 November, 2009 17:22

    thanks a lot dude..really helped me..

    ReplyDelete
  17. Dane Van Dyck30 November, 2009 22:43

    I want you to have my baby.

    ReplyDelete
  18. Unknown01 February, 2010 14:53

    So simple. Thank you very much for the assistance.

    ReplyDelete
  19. shparun09 April, 2010 03:05

    it's great that you wrote this post

    ReplyDelete
  20. Anonymous26 August, 2010 05:35

    Thanks so much!

    ReplyDelete
  21. Unknown26 August, 2010 10:25

    Thank you for your post.

    As it happens it's relevant to WCF 4.0 too

    ReplyDelete
  22. Anonymous01 September, 2010 21:48

    Thanks, this helped me out a ton.

    ReplyDelete
  23. Anonymous17 September, 2010 20:10

    How did you find/figure this out. I appreciate your posting it because I couldn't figure out how to make it go away.

    ReplyDelete
  24. Anonymous07 October, 2010 13:29

    Great, it worked for me. All I did was rename my namespace and it fixed the error. Well said.

    ReplyDelete
  25. Samchez26 November, 2010 09:56

    OMG thanks a lot, I can't believe I fell for this.

    ReplyDelete
  26. Anonymous24 February, 2011 00:06

    Also a big Thank you.

    This has wasted hours of my time.

    ReplyDelete