Just a reminder. If you're writing an ASP.net page that invokes a RCW (runtime callable wrapper) to a COM component... you may need to include the attribute 'ASPCompat=True' in your page directive.
In particular, if you have this situation:
"It worked fine in traditional ASP, but now it fails in ASP.net"
then it may be because ASP uses a STA (single-threaded-apartment) threading model, which the COM component may rely upon when returning calls.
The way to get the component to behave in ASP.net is to include that attribute, 'ASPCompat=True' in the calling page's page directive.
You already knew that right?
Well, should you accidentally forget... the chances of working it out on your own are very slim indeed, even with Google's help.
(end of comment)
'ROSARIOFRANKIE25' on Wed, 27 Jul 2011 03:55:19 GMT, writes:
I took my first <a href="http://bestfinance-blog.com/topics/personal-loans">personal loans</a> when I was a teenager and this aided my relatives very much. However, I need the auto loan once more time.
URL: http://www.bestfinance-blog.com
'tarun pahuja' on Fri, 17 Oct 2008 15:29:58 GMT, writes:
Good 1 bro.. Well Done..
if u have collections of this Knowledge gaining things plz do mail me at pahujafamily@gmail.com
'Wade0' on Fri, 20 Jan 2006 02:54:45 GMT, writes:
ASPCompat is not supported on Hosted Trust levels which most hosting service providers have configured, is there a work around?
URL: http://www.webcentral.com.au
'Angus Logan' on Mon, 03 May 2004 23:03:15 GMT, writes:
I was at a Microsoft presentation and they benchmarked adding ASPCompat to the @page directive.
I think the results were at least half the performance (maybe more)...
Use ASPCompat wisely my young padwan.