win2k com+ and MTS coexistence?

Results 1 to 2 of 2

Thread: win2k com+ and MTS coexistence?

  1. #1
    david boudah Guest

    Default win2k com+ and MTS coexistence?

    We have a situation where some developers are using win2k and hence com+ while other developers are using NT 4.0 and MTS. The target server is NT 4.0 and MTS. Is it possible for the win2k developers to compile VB dlls and have them run on the NT 4.0 box? Currently, the win2k developers are getting the following error on the createinstance statement when debugging vb on the local machine.<BR><BR>Set objData = objContext.CreateInstance("phxDataServices.CCheckI nPolicy")<BR><BR>Run-Time Error &#039 91&#039: Object variable or with block variable not set. <BR><BR>Under nt 4.0 you could make a registry change to get by this problem but how do you do this under win2k?<BR><BR>thanks for any help.<BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: win2k com+ and MTS coexistence?

    Your problem has nothing to do with Win2k. The problem is MTS....<BR><BR>when you compile your component to use the (MTS) ObjectContext, you cannot debug the component correctly if it uses the ASP-objects (request/response/etc.). There is an article on MSDN that describes a way to debug with the ObjectContext without getting those nasty errors, but you&#039ll end up with a set of dummy ASP-objects that don&#039t return or do anything at all (and that&#039s propably not what you want.).<BR><BR>You&#039ll need to use good old ScriptingContext to be able to debug your MTS components. My suggestion would be to read the article &#039conditional compiling of VB Components&#039 (or something like that) over at (by Doug Dean). It shows a way to create components that can use two contexts by setting a compilation switch. This allows you to use the SC when you are debugging, and the OC when you&#039re done.<BR><BR>There are some problems with the SC too, namely that if you call a class within the same project from another class in the project, the newly created class will not have access to the ASP-objects. The only solution for that is to use &#039Server.CreateObject&#039 inside the first class to call the other class with.... hard to explain, but you&#039ll propably run into it in time.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts