• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 232
  • Last Modified:

MTS and debugging

I have problems with trying to debug an ActiveX DLL, which is supposed to run under MTS.
Function ObjectControl_Activate() is never called, so my object can't obtain ObjectContext, and later I can't create ather object using oContext.CreateInstance()...
Is it possible obtain ObjectContext in debugging mode and how?
Thanks!
0
ekc
Asked:
ekc
  • 4
  • 3
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
Try to code simply CreateInstance instead if oContext.CreateInstance, this should work during debugging (CreateInstance is replaced by CreateObject) and during runtime inside of MTS the adequate Context object is used
0
 
ekcAuthor Commented:
I know that, but would like to know if it is possible to debug in MTS enviroment, with ObjectContext and all...
0
 
rvsamuelCommented:
can u try to add this key in u'r registry --
Debug\RunWithoutContext
in MyComputer\LocalMachine\Software\Microsoft\TransactionServer\

So u'r registry will look like

MyComputer\LocalMachine\Software\Microsoft\TransactionServer\Debug\RunWithoutContext

hope this solves u'r problem!!!!!!!!!



0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
ekc:
It is not possible to debug in MTS environment + VB, if you want to debug, the only thing u can do is:
Write to a Log (NT/FILE/DB). This is annoying, but the onyl way I know.
0
 
ekcAuthor Commented:
Unfortunately, I've tried that registry update some time ago, but it didn't help.
0
 
ekcAuthor Commented:
AngelIII,
could you explain me your solution, a little bit more detailed.
Thank you...
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
In your component, you have log your activity to either the NT Log, or an Flat file (which is fastest) or eventually to a Database (which can be queried later). What exactly to log depends on what you are trying to debug: usually, i have one component that indicates what is being debugged, and there all the components query this information. If debugging mode is activated for a module/component/function, then the component will write the logging information, otherwise not. This is the general auditing method, but it will cost time to activate this functionality.
To log in NT Log, you normally have the App.Log method (use StartLog and EndLog to enable the logging)
The file logging can easily be done in a small sub which writes a string to a file (i usually name the file using the date of the day, to avoid getting huge files and being able to manage these files better)
The database Log has the unconvenient, that you need a database connection (and thus the connect information) plus it makes much more overhead, but it presents the great advantage to be queryable afterwards.
0
 
ekcAuthor Commented:
Comment accepted as answer
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now