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. C#
  4. something weird is going on

something weird is going on

Scheduled Pinned Locked Moved C#
visual-studiohelpquestion
2 Posts 2 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
    damianrda
    wrote on last edited by
    #1

    hey guys, just noticed something seriously odd. when (some) of my apps are ran on another machine, they crash with a kernel32.dll problem. everything works fine on my development machine (vs 2008), some run fine on another machine, and some just refuse to. ive tried playing with the application target framework when building, etc.. im stumped. has anyone come across something like this?

    L 1 Reply Last reply
    0
    • D damianrda

      hey guys, just noticed something seriously odd. when (some) of my apps are ran on another machine, they crash with a kernel32.dll problem. everything works fine on my development machine (vs 2008), some run fine on another machine, and some just refuse to. ive tried playing with the application target framework when building, etc.. im stumped. has anyone come across something like this?

      L Offline
      L Offline
      LongRange Shooter
      wrote on last edited by
      #2

      The only time I've seen this happen is when the developer only tests on his/her machine. Did you do deployment testing on a clean machine without your development environment in place? Usually you have not included a key DLL or library when you built your setup code. Setup everything on a test machine with Visual Studio debugger running. See if you can find out from a clean machine what is happening. Just because it works on your machine does not mean you have not screwed the pooch.

      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