Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / August 2005

Tip: Looking for answers? Try searching our database.

Performance hit running 1.1 assembly in 2.0?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Steve Franks - 01 Aug 2005 13:15 GMT
I have a web site built using ASP.NET 2.0 and Visual Studio 2005.  If also
have a C# assembly that was compiled using VS 2003, so this assembly runs
under the 1.1 framework.

If I use this assembly built for the 1.1 framework within my web app that
uses the 2.0 framework, is there any performance penalty incurred here?  In
other words, am I creating some sort of "cross boundary" communication that
has to occur between the 2.0 framework and 1.1 framework?  Or is there no
performance penalty and just a matter of the 1.1 code not having access to
specific features of the 2.0 framework.

The dilemma I have is that I have to redistribute to developers my C# class
library.  Some developers are building ASP.NET 2.0 apps, while others are
using 1.1.  I do NOT want to wind up creating separate installations, one
that has my 2.0 compiled assembly and another that has my 1.1 compiled
assembly.

I could do this within one installer package and dynamically determine the
.NET framework and install the appropriate version of my assembly
accordingly.  However even this approach has major problems.  Specifically,
I could easily see how someone would install on a ASP.NET 2.0 machine, and
then wind up transferring my assembly DLL to another machine that only had
the 1.1 framework which from what I understand would break things.  Or
likewise they may install on 1.1 and then transfer the DLL to a 2.0 machine
and never realize the assembly was really running under the 1.1 framework on
that machine despite their app using 2.0.

What is a developer to do?

Steve
Scott M. - 01 Aug 2005 13:18 GMT
> Or is there no performance penalty and just a matter of the 1.1 code not
> having access to specific features of the 2.0 framework.

Correct.
Cowboy (Gregory A. Beamer) - MVP - 01 Aug 2005 15:26 GMT
The 1.1 assembly will run as if it is a 2.0 assembly when loaded. As long as
it does not hit a breaking change (and they promised us last year there would
be none ;->), you are fine.

Short answer: As long as it runs, it will run faster.

Signature

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

> I have a web site built using ASP.NET 2.0 and Visual Studio 2005.  If also
> have a C# assembly that was compiled using VS 2003, so this assembly runs
[quoted text clipped - 26 lines]
>
> Steve

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.