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. Upgraded from VS 2003 to VS 2005 then few of the strongly type (.xsd) datasets throws exceptions. Please look into it.

Upgraded from VS 2003 to VS 2005 then few of the strongly type (.xsd) datasets throws exceptions. Please look into it.

Scheduled Pinned Locked Moved ASP.NET
visual-studiohelpquestionannouncement
1 Posts 1 Posters 0 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.
  • S Offline
    S Offline
    Slow Learner
    wrote on last edited by
    #1

    Hello, I have upgraded all of my VS 2003 built xsd files to VS 2005. For some reason I just can’t compile the upgraded version of the project (in VS 2005) because of the exceptions (blue lines) I get in few of the “.xsd” files in the VS 2005 IDE. Error: I see blue lines under the below lines in my few of my DataSets System.ComponentModel.DesignerCategoryAttributeSystem.ComponentModel.ToolboxItemSystem.ComponentModel.CollectionChangeEventHandler _ When I mouse hover under the first one line of code it says “ ‘DesignerCategoryAttribute’ is ambiguous in the name space ‘System.ComponentModel’” On the second line I get “ ‘ToolBoxItemAttribute’ is ambiguous in the name space ‘System.ComponentModel’” On the third line On the second line I get “ ‘CollectionChangeEventHandler’ is ambiguous in the name space ‘System.ComponentModel’” And on the fourth line I get “ ‘Browsable’ is ambiguous in the name space ‘System.ComponentModel’” And so on… But just to give you note I don't see the same thing happerning for all of the .xsd file but for just few of them. I tried to compare both of these files to see if there is any difference in them but couldn't notice any thing different. Am I missing some thing in here? Do I have to reference any dlls in the VS 2005? If it was the case why few of the .xsd files are smiply fine? Any help is greatly appreciated. Thanks, -L

    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