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 / CLR / June 2004

Tip: Looking for answers? Try searching our database.

Q: Shared assemblies?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jiho Han - 14 Jun 2004 21:26 GMT
What is Shared Assemblies?  Does it have anything to do with .NET?  Or is
this for existing win32 .dlls?  Then why are they suddenly calling them
"assemblies"?
Scott M. - 14 Jun 2004 22:12 GMT
Yes, this is a .NET thing.  In .NET, the code that you compile down to is
generically called the "assembly", the actual file could be an .exe or a
.dll, but that is besides the point.

A "shared assembly" is one that has been registered into the "Global
Assembly Cache" (GAC) of a particular computer.  Shared assemblies allow the
developer to maintain just one copy of the actual assembly file and have it
available from a centralized point.

> What is Shared Assemblies?  Does it have anything to do with .NET?  Or is
> this for existing win32 .dlls?  Then why are they suddenly calling them
> "assemblies"?
Jiho Han - 14 Jun 2004 23:01 GMT
Apparently, there are two types of assemblies: CLR(.NET) and win32.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/assem
blies.asp


Well, in the context of .NET world, as we are in this NG, it'd seem that an
assembly refers to what you have defined and shared assemby, to some degree,
as you have defined.
Shared assemblies and side-by-side execution seem to mean a slightly
different things when spoken outside of the .NET context.

Please correct me if I'm wrong.
Thanks

> Yes, this is a .NET thing.  In .NET, the code that you compile down to is
> generically called the "assembly", the actual file could be an .exe or a
[quoted text clipped - 8 lines]
> > this for existing win32 .dlls?  Then why are they suddenly calling them
> > "assemblies"?
Scott M. - 14 Jun 2004 23:14 GMT
Not many people refer to Win32 components as assemblies, but the term
assembly is a fairly generic term, so I suppose it could apply to Win32.  To
know the difference, you will hear people speak in terms of the assembly
being "managed" or not.  If it is managed, then it means that it is managed
by the .NET Framework Common Language Runtime (CLR), if it is un-managed,
then it is not managed by the CLR (and therefore is COM based).

> Apparently, there are two types of assemblies: CLR(.NET) and win32.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/assem
blies.asp


> Well, in the context of .NET world, as we are in this NG, it'd seem that an
> assembly refers to what you have defined and shared assemby, to some degree,
[quoted text clipped - 20 lines]
> > > this for existing win32 .dlls?  Then why are they suddenly calling them
> > > "assemblies"?

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.