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. General Programming
  3. Visual Studio
  4. Pocket PC Emulator Error in Visual Studio 2005

Pocket PC Emulator Error in Visual Studio 2005

Scheduled Pinned Locked Moved Visual Studio
helpcsharpvisual-studiocombeta-testing
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.
  • D Offline
    D Offline
    DigiOz Multimedia
    wrote on last edited by
    #1

    I am getting the following error message when trying to run "Pocket PC 2003 SE Emulator" in Visual Studio 2005: The operation could not be completed. No such interface supported In the Event Viewer of the development machine, I see the following entry related to the above: Event Type: Error Event Source: SideBySide Description: Dependent Assembly Microsoft.VC90.CRT could not be found and Last Error was The referenced assembly is not installed on your system. The problem seems to have started ever since I beta tested Visual Studio 2008 Beta 1 (which I uninstalled already). Does anyone have any suggestions on how to fix this?

    Pete Soheil DigiOz Multimedia http://www.digioz.com

    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