398 packages tagged with “assembly”
Cecil is a library written by Jb Evain to generate and inspect programs and libraries in the ECMA CIL format. It has full support for generics, and support some debugging symbol format. In simple English, with Cecil, you can load existing managed assemblies, browse all the contained types, modify them on the fly and save back to the disk the modified assembly.
Contains the SDK reference assemblies for PowerShell version 5
Complement for System.Reflection, including an IL disassembler.
Extensions for ordered testing with Xunit. Full support for ordering at all levels - test collections, test classes and test cases. Support for AssemblyFixture including IMessageSink injection and IAsyncLifetime. Supports .NET Core 1.x, .NET Core 2.x. and .NET 4.5.2+
FluentRegistration
Contains the SDK reference assemblies for PowerShell version 3
Utilities and smaller MonoMod "components" (f.e. ModInterop, DynDll, DynData). Can be used for your own mods. Required by all other MonoMod components.
Contains the reference assemblies for PowerShell version 5.1
Flexible and easily extensible runtime detouring library. Wrap, replace and manipulate (Mono.Cecil) methods at runtime.
A typed assembly and project information generator.
NsDepCop is a static code analysis tool that enforces namespace and assembly dependency rules in C# projects.
Common building blocks used INTERNALLY by MonoMod and Harmony which can be used to build your own libraries, f.e. RuntimeDetour's platform abstraction and Utils' DynamicMethodDefinition. For code that is ready to use reliably, use MonoMod.Utils.
Reads and writes .NET assemblies and modules, Windows PDBs and Portable PDBs. For better *Windows PDB* writer support, you should add a reference to `Microsoft.DiaSymReader.Native` nuget package too, see the dnlib README for more info: https://github.com/0xd4d/dnlib#windows-pdbs . You don't need to do anything special for *Portable PDB* support.
A set of backports of new BCL features to all frameworks which MonoMod supports.
The code functionality for runtime detouring. Use `DetourFactory.Current` to get a DetourFactory capable of installing unique method detours. WARNING: THIS IS A LOW-LEVEL LIBRARY THAT IS DIFFICULT TO USE ON ITS OWN. If possible, use MonoMod.RuntimeDetour instead.
Package Description
Automatic strong-name signing of referenced assemblies. Utility software to strong-name sign .NET assemblies, including assemblies you do not have the source code for. If you strong-name sign your own projects you may have noticed that if you reference an unsigned third party assembly you get an error similar to "Referenced assembly 'A.B.C' does not have a strong name". If you did not create this assembly, you can use this tool to sign the assembly with your own (or temporarily generated) strong-name key. The tool will also re-write the assembly references (as well as any InternalsVisibleTo references) to match the new signed versions of the assemblies you create.
A tool to check binary compatibility of a set of assemblies and possibly baseline exclusions.
Raw PE file models for the AsmResolver executable file inspection toolsuite.
The base library for the AsmResolver executable file inspection toolsuite.
Stamps an assembly with a Timestamp.
Contains the SDK reference assemblies for PowerShell version 4
Scan and wire up assemblies based on directory and search patterns
Provides useful methods for extracting information from and interacting with assemblies using reflection.
Common framework for DAL and BIZ packages
PE image models for the AsmResolver executable file inspection toolsuite.
Allows emitting arbitrary assembly attributes, compatible with SDK-style projects and classic ones. Usage: declare @(AssemblyAttribute) items to include, such as: <ItemGroup> <AssemblyAttribute Include="[ATTRIBUTE_FULL_TYPENAME]" _Parameter1="[CTOR_ARG]" _ParameterN="[CTOR_ARG_N]" /> </ItemGroup> The `_ParameterN` attributes must match the attribute constructor arguments. Use the following properties to customize what is generated: <PropertyGroup> <GenerateAssemblyCompanyAttribute>true|false</GenerateAssemblyCompanyAttribute> <GenerateAssemblyConfigurationAttribute>true|false</GenerateAssemblyConfigurationAttribute> <GenerateAssemblyCopyrightAttribute>true|false</GenerateAssemblyCopyrightAttribute> <GenerateAssemblyDescriptionAttribute>true|false</GenerateAssemblyDescriptionAttribute> <GenerateAssemblyFileVersionAttribute>true|false</GenerateAssemblyFileVersionAttribute> <GenerateAssemblyInformationalVersionAttribute>true|false</GenerateAssemblyInformationalVersionAttribute> <GenerateAssemblyProductAttribute>true|false</GenerateAssemblyProductAttribute> <GenerateAssemblyTitleAttribute>true|false</GenerateAssemblyTitleAttribute> <GenerateAssemblyVersionAttribute>true|false</GenerateAssemblyVersionAttribute> <GenerateNeutralResourcesLanguageAttribute>true|false</GenerateNeutralResourcesLanguageAttribute> </PropertyGroup> And their corresponding values * AssemblyCompanyAttribute: $(Company) * AssemblyConfigurationAttribute: $(Configuration) * AssemblyCopyrightAttribute: $(Copyright) * AssemblyDescriptionAttribute: $(Description) * AssemblyFileVersionAttribute: $(FileVersion) * AssemblyInformationalVersionAttribute: $(InformationalVersion) * AssemblyProductAttribute: $(Product) * AssemblyTitleAttribute: $(AssemblyTitle) * AssemblyVersionAttribute: $(AssemblyVersion) * NeutralResourcesLanguageAttribute: $(NeutralLanguage)
This is targeted for signing the contents of NuGet packages that are using unsigned assemblies, in order to be able to link to these packages where the consuming project is strongly named. Access to the original source code is not required, and you may sign any assembly with your own strong naming key. You may also delay-sign if desired.
Enables module initialization, as described here: http://einaregilsson.com/module-initializers-in-csharp