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. COM
  4. DLL - Firing an event - Exception

DLL - Firing an event - Exception

Scheduled Pinned Locked Moved COM
debugginghelpc++databasecom
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.
  • L Offline
    L Offline
    lgatcodeproject
    wrote on last edited by
    #1

    Hi All, I am building a com dll using vs2005. I have created two events. I have created a client application in VB and built an exe. When I run my application in debug mode, I get an exception in fire events dispatch method, which states "unhandled exception at 0x661068 second.exe: 0xc00000005. Access violation writing location 0x0000050." In the above error the "second.exe" is the exe name of my vb application. But when I run the application in vb I get the events is getting fired, some time the application gets crashed. When I put a break point in the fire_event method the application crashes for sure when an event gets fired for the first time. can any one help in this. And I have another query, does the vc++ through an error like the one I have stated above when we debug the application that contains a breakpoint? Kindly clarify! Regards, LG.

    lgatcodeproject

    J 1 Reply Last reply
    0
    • L lgatcodeproject

      Hi All, I am building a com dll using vs2005. I have created two events. I have created a client application in VB and built an exe. When I run my application in debug mode, I get an exception in fire events dispatch method, which states "unhandled exception at 0x661068 second.exe: 0xc00000005. Access violation writing location 0x0000050." In the above error the "second.exe" is the exe name of my vb application. But when I run the application in vb I get the events is getting fired, some time the application gets crashed. When I put a break point in the fire_event method the application crashes for sure when an event gets fired for the first time. can any one help in this. And I have another query, does the vc++ through an error like the one I have stated above when we debug the application that contains a breakpoint? Kindly clarify! Regards, LG.

      lgatcodeproject

      J Offline
      J Offline
      Ju ncho
      wrote on last edited by
      #2

      Maybe the interop file is corrupt so try 1) cleaning the entire solution and running again 2) Deleting the COM dlls references and objects from your vb proyect and putting them again.

      JO :)

      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