RE: Accessing .NET DLL(s) from Classic ASP

Hi Shamshad,

As for calling .NET component (assembly) directly from classic ASP, I think
COM interop is the only approach. Also, if you want to call multiple .NET
components, I think you'd better make sure they're built-in upon the same
version (or at least of compatible versions). Because for a single process,
only one version of CLR runtime will be loaded(and those built-in framework
components). .NET 3.X relies on .NET frameworrk 2.0, therefore, I think
components built-in upon .NET 2.0 and .NET 3.X can work together as long as
the process has loaded the higher version. And the order how you load
multiple .net components into unmanaged process will also affect the
behavior, the version of the first .NET component you load(in unmanaged
process) will determine the CLR runtime version it will load for the entire
process.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights--------------------
From: "Shamshad Ali" <sww@xxxxxxxxxxxxxxxxx>
Subject: Accessing .NET DLL(s) from Classic ASP
Date: Wed, 19 Mar 2008 12:50:11 +0500

Hi,

I have similar question that i saw yesterday (Calling .NET DLL from
Classic
ASP), but we have achieved some good results and we can't go back but not
sure that approach is perfect or need more efforts or any better is
available?

here is some details:

We have production website running on Classic ASP (Windows Server 2003
E.Ed
+ IIS and SQL Server 2000 SP-4). we are tracking hits of students on their
courses and other stuff in database. This is done by COM wirtten in C#
2.0.
there is no error and run fine until there is much traffic on site. We
faced
following error:

Server object error 'ASP 0177 : 80131509'
Server.CreateObject Failed

/includes/trk_SessionEndTime_Cookie.asp, line 32

I tried to find out any solution or details about this error on Microsoft
site but nothing found. the only solution is to re-start IIS. Our site is
providing credit to students and doing re-start is not solving our problem
and we lost online users credit for that period. The reason we wrote this
DLL was due to site performance issue with classic ASP code, so we used
..NET
2.0 DLL. that produced better results in performance.

This is not at all, further we have to send some users/students
information
to their respective colleges (they have provided us web services), calling
web service via ASP is done by creating another DLL written in 1.1, 2.0
and
3.5 version of .NET and all are tested on local system, that may update
users results online to their specific colleges/universities.

The is question is, is this a right way to do? (calling DLLs written in
different .NET version from classic ASP) is there any better solution
available? Right now we can't migration our whole classic ASP website to
.NET


Shamshad Ali.





.

Relevant Pages

  • Re: Accessing .NET DLL(s) from Classic ASP
    ... the normal approach is performing debugging to the ... process which launch the .NET component(also load CLR runtime). ... product support service since some support professional there can help ... Is there any issue/conflict using COM interop in classic ASP? ...
    (microsoft.public.inetserver.asp.components)
  • Re: Accessing .NET DLL(s) from Classic ASP
    ... As you are saying that problem occurs at high load, ... DLL to be failing? ... Microsoft MSDN Online Support Lead ... Is there any issue/conflict using COM interop in classic ASP? ...
    (microsoft.public.inetserver.asp.components)
  • Re: Accessing .NET DLL(s) from Classic ASP
    ... Since you've used multiple .NET components in the ... Microsoft MSDN Online Support Lead ... You can send feedback directly to my manager at: ... Is there any issue/conflict using COM interop in classic ASP? ...
    (microsoft.public.inetserver.asp.components)
  • Re: Accessing .NET DLL(s) from Classic ASP
    ... Is there any issue/conflict using COM interop in classic ASP? ... Microsoft MSDN Online Support Lead ... I have similar question that i saw yesterday (Calling .NET DLL from ... Right now we can't migration our whole classic ASP website to ...
    (microsoft.public.inetserver.asp.components)
  • Re: Future of ASP
    ... Microsoft will most likely continue to support classic ASP for a long, ... They still support IDC, which has been obsolete for about 7 years. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading