Re: Using .NET 2.0/3.0 component in ASP.NET 1.1

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks Phill. This helps.

My bad, I though it may be possible to “configure” a specific component of
..NET 1.1 application to use .NET 2.0 framework (which is what we want as we
do not want to migrate the entire application to .NET 2.0 platform). I guess
a single process/domain can use only one target framework at a time.

Thanks,
Rasheed


"Phil H" wrote:

On 29 Dec, 23:15, Rasheed <Rash...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks Scott. We do have the .NET 2.0 framework installed in addition to
.NET 1.1. Are you saying.NET 2.0 components cannot be accessed from ASP.NET
1.1 (.NET 1.1) application?

Thanks,
Rasheed



"Scott M." wrote:
This is not possible. If you use a .NET 2.0 component, you need the 2..0
..NET Framework to run the applicaiton.

"Rasheed" <Rash...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9B7F07FE-3882-42E8-9216-AFA0EF440AA5@xxxxxxxxxxxxxxxx
Hi,

We have an ASP.NET 1.1 application which uses .NET framework 1.1. The
application is hosted in IIS 5.0 win 2000. We want to write a .NET 2.0
component (which leverages .NET 2.0 Framework, Ex: Dataset Bulk Update
feature) and access it from ASP.NET 1.1. Is this possible? If so, please
provide inputs on how this can be done or direct me to the appropriate
resources?

Note: We have both the framework installed in the web server.

Appreciate your help!

Rasheed- Hide quoted text -

- Show quoted text -

Rasheed

You cannot expect ASP.NET v 1.1 to recognise and handle new components
introduced in v 2.0 The latter was developed ouside of the design
limitations of v 1.1 (it is reasonable to assume the ASP.NET v 1.1
developer's brief did not extend to unforseen enhancements), hence the
introduction of a new version of ASP.NET.

Had you put the question the other way round then the answer would be
Yes, ASP.NET v 2 is backward compatible with v 1.1 but that's only
because it was developed with full knowledge of the previous version.


.

Relevant Pages

  • Concerns with COM+
    ... as an application framework. ... Bloated - it takes up too many server resources for the support ... Platform Dependent - I don't want to say that J2EE is the end-all ... minimal library changes so that it could run in various platforms as ...
    (comp.programming)
  • Re: Using .NET 2.0/3.0 component in ASP.NET 1.1
    ... "Scott M." wrote: ... runtime would not understand something introduced in the 2.0 Framework. ... ..NET Framework to run the applicaiton. ... introduced in v 2.0 The latter was developed ouside of the design ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Using .NET 2.0/3.0 component in ASP.NET 1.1
    ... The .NET Framework consists of a set of base classes and a Common Language ... ..NET Framework to run the applicaiton. ... introduced in v 2.0 The latter was developed ouside of the design ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Concerns with COM+
    ... Are you sure your problem is with the framework and not with this "very ... If they want platform independence they can't use COM+. ... Java is interpreted, ...
    (comp.programming)
  • Re: Testing a package
    ... I looked at SUnit and ended up building my own framework that was friendly to package level testing and was simple. ... I suspect that a combination of singleton test resouces combined with a clear pattern for their use (perhaps a TestCase method to access them) would make it almost as easy as checking the #test* methods against references to the subclasses of TestResource. ... a TestCase subclass could override #requiredResources to add anything that slipped past the detection grid. ... a singleton implementation of resources. ...
    (comp.lang.smalltalk.dolphin)