Last post Dec 19, 2005 04:26 PM by xddg
Dec 19, 2005 04:47 AM|irfanzafar|LINK
Dec 19, 2005 07:15 AM|rodneyjoyce|LINK
Dec 19, 2005 07:17 AM|zoulou|LINK
Assemblies are basically the compiled code in .Net which contains the code in Microsoft Intermediate Langauge and one more thing that assembiles do for us as compared to dlls is they can maintain versioning with the help of the manifest.
You dont need to register the assemblies after compiling like we needed in dlls. you can put the assemblies in the bin folder and refer the namespaces from there.
In short find the assembly description as :
Assemblies are the building blocks of .NET Framework applications; they form the fundamental unit of deployment, version control, reuse, activation scoping, and security permissions. An assembly is a collection of types and resources that are built to work
together and form a logical unit of functionality. An assembly provides the common language runtime with the information it needs to be aware of type implementations. To the runtime, a type does not exist outside the context of an assembly.
Differences Between Shared and Private Assemblies and how to use them.
Shared and Private Assembly: A private assembly is a assembly that is available to particular applications where they are kept. And cannot be references outside the scope of the folder where they are kept.
In contrast, Shared Assemblies are the assemblies that are accessible globally/shared across the machine to all the applications. For using the shared assemblies you need to register the assembly with a strong name in the global assembly cache(GAC) using gacutil.exe.
GAC can be found on all the computers with .Net framework installed.
Dec 19, 2005 04:26 PM|xddg|LINK
This is an interesting comment and has been raised in the Core Team Chats when discussing ways to make something to none technical people a little more easier to understand.
Has anyone noticed some of the wording changing on the downloads..
.install & .source - this is to hopefully simplify the words and *lingo* of working in the DotNetNuke enviroment.
Having said that - has anyone looked at PHP words - gz, tar, gzips - I am lost when I look at PHP terminology so I guess it's something we all have to learn when are adopting new technology.