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 / ASP.NET / General / July 2007

Tip: Looking for answers? Try searching our database.

DLL Information

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Joe - 20 Jul 2007 15:04 GMT
Alright after much researching, I've come to the conclusion that I
need to post this here hoping to get a solid answer.  I'm looking to
create a DLL that is capable of being used on all platforms that I
mentioned in my subject (1.1 framework, 2.0 framework, old ASP)  I'm
hoping to be able to create this DLL via a 2.0 .net class library.
Once its created I want the ability to reference this DLL along with
all its methods and properties in both 1.1 .NET projects and an old
ASP project.  I know in regular ASP you can create.objects() and in
1.1 you can just add references but I'm always unclear whether or not
this is possible to do with a 2.0 DLL.  I seen to always have problems
adding a reference to a DLL in 1.1 when the DLL was created in 2.0.
Can anyone provide a reasonable answer to this question? The ideal
situation i'm looking for is 2.0 coding and then using that in the
other places.  Does anyone have a solid answer out there?
Cowboy (Gregory A. Beamer) - 20 Jul 2007 17:24 GMT
I have a solid answer, but you might not like it. :-)

The ASP.NET and ASP issue is fairly easy to solve. You simply make a COM
wrapper for the assembly. There is a tool called regasm.exe, in the
Framework, that allows you to both create the COM wrapper and register in
the Registry. Nice tool.

The 1.1 and 2.0 issue is a different story. There are two ways I can
recommend.

Way #1:
Create a 1.1 assembly and compile it. You can then use it in 2.0
applications, but I would consider recompiling in 2.0 regardless, as it is
more efficient.

Way #2
Create a 2.0 assembly and a web service (ASMX or WCF) to wrap it as a
service. Then, call this service from 1.1. Not true reuse, but it is a great
way to provide to all sorts of applications, .NET or otherwise.

Signature

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************

> Alright after much researching, I've come to the conclusion that I
> need to post this here hoping to get a solid answer.  I'm looking to
[quoted text clipped - 10 lines]
> situation i'm looking for is 2.0 coding and then using that in the
> other places.  Does anyone have a solid answer out there?

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.