Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
OLEException errors after com object rebuids in ASP.net
Message
De
06/12/2005 19:59:31
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Titre:
OLEException errors after com object rebuids in ASP.net
Divers
Thread ID:
01075555
Message ID:
01075555
Vues:
64
Can someone please explain what is happening here? I am using a vfp mtdll com object in my asp.net application. The com object resides in a directory that permits the impersonated aspnet user full control. I have created a COM+ application that uses the 1 and only class in my vfp com object as its component. The impersonated aspnet user is also assigned to the COM+ application so that my com object takes on the idenity of the aspnet impersonated user. COM+ gives my vfp com object the proper security identity so that the com object can access the data tables all over my internal network. Everything works great. From time to time I modify the source code in the functions within my vfp com object. I rebuild the com object, without generating a new key, and simply copy it to the directory on the web server. However I find myself running into trouble when I do more than modify the code in a function. If I change the signature of a function ie: increase or decrease the number of passed in parameters or if add a function or if I change the position of a function in the code I run into trouble. I get all types of OLEException errors that are impossible to root out.

But the fix is simple: I create a new project with a *different* name, build a new mtdll from the newly named project, uninstall the old mtdll on the web server, remove the reference to the old mtdll from my asp.net application, add a new reference in my asp.net application to the newly named mtdll, register the mtdll on the web server and have it run under a newly name COM+ application.

There has got to be an easier way!

Regards,
Neil Gorin
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform