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. The Lounge
  3. 3.5 SP1 fixes 2.0 VM issues

3.5 SP1 fixes 2.0 VM issues

Scheduled Pinned Locked Moved The Lounge
csharpcomhelpquestion
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.
  • U Offline
    U Offline
    User of Users Group
    wrote on last edited by
    #1

    There is one, seemingly silent as I cannot find the reference anywhere, positive sign. They seemed to have fixed some bugs that no longer crash the VM on older systems. Even VS2008 is working with property pages, debugging, and editing without occasionally vanishing off the screen. Boxes that had .NET Runtime 2.0 Error and mscorwks.dll, or Fatal Execution Engine Error string in their event logs are now usable. About bldy time.. The only detail that gives it away is the 2.0.50727.1433 bump up to 2.0.50727.3053. ( in chinese: http://www.xvision.com//search?hl=zh-CN&q=Fatal%20Execution%20Engine%20Error&meta=&aq=f&oq=[^] )

    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