+ Reply to Thread
Results 1 to 6 of 6

Thread: ServiceModel does not Exist in namespace System

  1. #1
    Administrator richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich's Avatar
    Join Date
    Mar 2008
    Location
    Somewhere only we know...
    Posts
    3,207
    Blog Entries
    14
    Real Name
    Rich
    Rep Power
    14

    ServiceModel does not Exist in namespace System

    I'm doing some work on WCF web services etc. and this requires using System.ServiceModel namespace.

    When I add a using statement for this namespace though, VS underlines it saying it doesn't exist in the Namespace System. When I upload the app to the server and run it, it works fine.

    I've read the stuff on google and have uninstalled MS .NET Framework 3.5 completely. I've also uninstalled MS .NET CF 3.5 and then reinstalled that, but it still gives the same error.

    Any ideas what I can do to get it to recognise this namespace? If I open Object Browser, the namespace is in their, so I don't understand why it won't find it when I try using it in code.

    Any ideas?

  2. #2
    Administrator richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich's Avatar
    Join Date
    Mar 2008
    Location
    Somewhere only we know...
    Posts
    3,207
    Blog Entries
    14
    Real Name
    Rich
    Rep Power
    14

    OK. I think I sorted it by Adding a Reference to the project.

    Right click on the root of the project in Solution Explorer and select Add Reference. Then scroll to the reference needed and click add.

    Not quite sure why you need to add some references and not others, but that seems to have sorted the problem.

    Just having to reinstall all the .NET Frameworks now...

  3. #3
    Administrator richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich's Avatar
    Join Date
    Mar 2008
    Location
    Somewhere only we know...
    Posts
    3,207
    Blog Entries
    14
    Real Name
    Rich
    Rep Power
    14

    OK.

    I tried the same with System.ServiceModel.Web and that didn't work...

    I just have the .NET 3.5 SP1 Framework installed. Should I reinstall the Compact version as well.

    Any ideas?

    Perhaps a reboot will fix it...

  4. #4
    Administrator richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich's Avatar
    Join Date
    Mar 2008
    Location
    Somewhere only we know...
    Posts
    3,207
    Blog Entries
    14
    Real Name
    Rich
    Rep Power
    14

    The only way I seemed to be able to solve this issue was to copy and paste the dll into the bin folder.

    That can't be right....

  5. #5
    The Barnfather jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead has much to be proud of jmurrayhead's Avatar
    Join Date
    Mar 2008
    Location
    Reston, VA
    Posts
    4,533
    Blog Entries
    9
    Real Name
    Jason
    Rep Power
    22

    I've had to do that where the dll was missing from the web server. It's not a big deal, though.
    jmurrayhead
    If you agree, give me rep.
    If you like it here...throw us a few bones to help support us.


  6. #6
    Administrator richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich is a splendid one to behold richyrich's Avatar
    Join Date
    Mar 2008
    Location
    Somewhere only we know...
    Posts
    3,207
    Blog Entries
    14
    Real Name
    Rich
    Rep Power
    14

    Quote Originally Posted by jmurrayhead View Post
    I've had to do that where the dll was missing from the web server. It's not a big deal, though.
    I just thought that if it's part of the .NET Framework, it should be there already.

    No biggie though I guess...

+ Reply to Thread

Similar Threads

  1. ambiguous in the namespace 'ASP'
    By richyrich in forum .NET Development
    Replies: 10
    Last Post: May 30th, 2008, 05:11 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

SEO by vBSEO