What is an Assembly file ?
477320
In the Microsoft .NET framework an assembly is a partially compiled code library for use in deployment, versioning and security. In the Microsoft Windows implementation of .NET, an assembly is a PE (portable executable) file. There are two types, process assemblies (EXE) and library assemblies (DLL). A process assembly represents a process which will use classes defined in library assemblies. In version 1.1 of the CLR classes can only be exported from library assemblies; in version 2.0 this restriction is relaxed. The compiler will have a switch to determine if the assembly is a process or library and will set a flag in the PE file. .NET does not use the extension to determine if the file is a process or library. This means that a library may have either .dll or .exe as its extension.\n\nThe code in an assembly is partially compiled into CIL, which is then fully compiled into machine language at runtime by the CLR.\n\nAn assembly can consist of one or more files. Code files are called modules. An assembly can contain more than one code module and since it is possible to use different languages to create code modules this means that it is technically possible to use several different languages to create an assembly. In practice this rarely happens, principally because Visual Studio only allows developers to create assemblies that consist of a single code module.\n\nThe name of an assembly consists of four parts:\n\n   1. The short name. On Windows this is the name of the PE file without the extension.\n   2. The culture. This is an RFC 1766 identifier of the locale for the assembly. In general, library and process assemblies should be culture neutral, the culture should only be used for satellite assemblies.\n   3. The version. This is a dotted number made up for 4 values — major, minor, build and revision. The version is only used if the assembly has a strong name (see below).\n   4. A public key token. This is a 64-bit hash of the public key which corresponds to the private key used to sign the assembly. A signed assembly is said to have a strong name.\n\nThe public key token is used to make the assembly name unique. Thus, two strong named assemblies can have the same PE file name and yet .NET will recognise them as different assemblies. The Windows file system (FAT32 and NTFS) only recognises the PE filename, so two assemblies with the same PE file name (but different culture, version or public key token) cannot exist in the same Windows folder. To solve this issue .NET introduces something called the GAC (Global Assembly Cache) which is treated as a single folder by the .NET CLR, but is actually implemented using nested NTFS (or FAT32) folders.\n\nTo prevent spoofing attacks, where a cracker would try to pass off their assembly as yours, the assembly is signed with a private key. You keep your private key secret, so a cracker cannot have access to it, and cannot guess the associated public key. Signing the assembly involves taking a hash of important parts of the assembly and then encrypting the hash with the private key. The signed hash is stored in the assembly along with the public key. The public key will decrypt the signed hash. When the CLR loads a strongly named assembly it will generate a hash from the assembly and then compares this with the decrypted hash. If the comparison succeeds then it means that the public key in the file (and hence the public key token) is associated with the private key used to sign the assembly. This will mean that the public key in the assembly is the public key of the assembly publisher and hence a spoofing attack is thwarted.\n\n.NET code access security is based on assemblies and evidence. Evidence can be anything deduced from the assembly, but typically it is created from the source of the assembly — whether the assembly was downloaded from the Internet, an intranet, or installed on the local machine (if the assembly is downloaded from another machine it will be stored in a sandb
892614
you can use Siw, it's a system information tool, and free\n\nhttp://www.snapfiles.com/reviews/SIW/siw.html
12313
Assembler.  It is compiled into machine language.\n\nJust don't produce inefficient code with it.
631216
rundll32 is run dll as application\nctfmon is CTF loader \nBoth made by microsoft
1096817
search for it from the microsoft site .. its visualbasic 6 runtime files
162727
Imports System\nImports System.Reflection\n\n<Assembly: AssemblyDescription("Apple")> \n<Assembly: AssemblyProduct("Banana")> \n\nModule Module1\n\n\n    Sub Main()\n\n\n        Dim x As Integer\n        Dim a As System.Reflection.Assembly\n        Dim t As Object()\n        Dim s As System.Type\n\n        a = System.Reflection.Assembly.GetExecutingAssembly()\n        Console.WriteLine("FullName=" & a.FullName())\n        Console.WriteLine("CodeBase=" & a.CodeBase())\n\n        t = a.GetCustomAttributes(True)\n        For x = 0 To t.Length - 1\n            s = t(x).GetType()\n            Console.WriteLine(x & " " & s.ToString())\n            If TypeOf (t(x)) Is System.Reflection.AssemblyDescriptionAttribute Then\n                Console.WriteLine("  Product=" & CType(t(x), System.Reflection.AssemblyDescriptionAttribute).Description)\n            End If\n            If TypeOf (t(x)) Is System.Reflection.AssemblyProductAttribute Then\n                Console.WriteLine("  Description=" & CType(t(x), System.Reflection.AssemblyProductAttribute).Product)\n            End If\n        Next\n\n        Console.WriteLine(vbCrLf)\n\n    End Sub\n\nEnd Module
602042
First make a copy of it, then put the copy in windows/system32. Most of your .dll files are there. If thats not it you still have a copy. Make another copy and put it in windows/service pack files/i386.
724801
assembly is based on machine language.\n\nmachine language is limited (directly controlling bit value i.e 0  or  1)\nassembly is develloped by the user who uses the machine language to define some functions that one can then use directly .\n\n\n\n   "Transforming assembly into machine language is accomplished by an assembler, and the reverse by a disassembler. Unlike in high-level languages, there is usually a 1-to-1 correspondence between simple assembly statements and machine language instructions. However, in some cases, an assembler may provide pseudoinstructions which expand into several machine language instructions to provide commonly needed functionality. For example, for a machine that lacks a "branch if greater or equal" instruction, an assembler may provide a pseudoinstruction that expands to the machine's "set if less than" and "branch if zero (on the result of the set instruction)". Most full-featured assemblers also provide a rich macro language (discussed below) which is used by vendors and programmers to generate more complex code and data sequences."\n\n\nthis is from the wikipedia article on asembly language.\n\nhttp://en.wikipedia.org/wiki/Assembly_language
258111
It's a resource file for a program. In programming you try to reuse code as much as possible . . . in essence you make small machines that you can reuse, these small machines then form a larger machine (your program). Dynamically Linked Libraries (.DLL) reuse existing code in the Operating System or you can make your own for a special use. Below is a link to wikipedia . . . it's a okay place to start your research\n\n"In computer science, a Dynamic Library, also referred to as a Dynamically Linked Library, is a computer library that implements the concept of dynamic linking."
272567
Each computer where the common language runtime is installed has a machine-wide code cache called the global assembly cache. The global assembly cache stores assemblies specifically designated to be shared by several applications on the computer.\n\nAs a general rule, the Windows Registry is considered legacy within .NET and XCOPY deployment is highly encouraged, which in turn implies building assemblies that are private to a program’s main executable. Yet, there is a definite need for a central repository for .NET System assemblies as well as other user created Shared assemblies and it is this very need which is addressed by the GAC.\n\n it is important to understand the concept of Identity as it pertains to a .NET Assembly. An Assembly’s identity includes its simple textual name, a version number, an optional culture if the assembly contains localized resources, and an optional public key used to guarantee name uniqueness and to protect the name from unwanted reuse (name spoofing). An assembly with a simple Identity includes just the mandatory simple textual name and version number components. Since the GAC is the machine-wide repository for shared assemblies, it is very easy to run into the problem of name collisions if these assemblies only had simple identities because they are developed independently by different vendors and even developers within your own organization. Hence it is mandatory that every shared assembly installed in the GAC have a Strong Name. The formal definition of the term in the online documentation is\n\nA strong name consists of the assembly's identity — its simple text name, version number, and culture information (if provided) — plus a public key and a digital signature. It is generated from an assembly file (the file that contains the assembly manifest, which in turn contains the names and hashes of all the files that make up the assembly), using the corresponding private key.
393592
What you would need is a disassembler for the specific processor that the software runs on. Even then, the disassembled executable will be difficult to follow, as many compilers create very bizarre executable code for perfectly sensible source code. It's only worth doing for small programs and only if it's the only way to get the assembly language source. There is no way to get back to the original C / C++ source, no matter what anybody may write.\n\nIf this request is for a large program (>2000 bytes) that runs on a PC, then forget it. It's only worth doing for embedded software, which is typically fairly small.
1026682
It think that's an AutoCad file.  http://usa.autodesk.com/adsk/servlet/index-w?id=331041&siteID=123112
379900
You probably mean dll. There is a webiste where you can download .dll files, but you did not specify.
167955
Well you can if you compile it, I forget exactly how.\n\nBut if you just have the dll I don't believe you can. It would sort of defeat the purpose if that sort of information was editable by users.
373444
You can found assembly language wherever you want to.  Simply write a language and publicly announce it as your own with the moniker "assembly" - but don't be surprised if the real creator of the language comes after you for it.
356292
I don't understand your question.  Do you want to write an assembler in Visual Basic?  This sounds like a homework exercise for school.  Secondly, no one knows just what this SIC is.
298237
Download the file from the following site:\nhttp://www.dll-files.com/dllindex/dll-files.shtml?oleaut32\n\n\nThen save the file to the following location: c:&#92;windows&#92;system\n\nIf you receive a message asking if you want to overwrite an existing file, click yes or ok.\n\nAfter saving the file, restart your computer.