{
	"id": "90c97c28-6ab3-4714-9c90-cbfab5884a0a",
	"created_at": "2026-04-06T00:11:05.969231Z",
	"updated_at": "2026-04-10T13:12:59.050754Z",
	"deleted_at": null,
	"sha1_hash": "6b78c13282dc2992a825d1dfcb593011fafb0555",
	"title": "Manifests - Win32 apps",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 33227,
	"plain_text": "Manifests - Win32 apps\r\nBy drewbatgit\r\nArchived: 2026-04-05 22:27:04 UTC\r\nManifests are XML files that accompany and describe side-by-side assemblies or isolated applications. Manifests\r\nuniquely identify the assembly through the assembly's assemblyIdentity element. They contain information used\r\nfor binding and activation, such as COM classes, interfaces, and type libraries, that has traditionally been stored in\r\nthe registry. Manifests also specify the files that make up the assembly and may include Windows classes if the\r\nassembly author wants them to be versioned. Side-by-side assemblies are not registered on the system, but are\r\navailable to applications and other assemblies on the system that specify dependencies in manifest files.\r\nManifest files enable administrators and applications to manage side-by-side assembly versions after deployment.\r\nEvery side-by-side assembly must have a manifest associated with it. The installation of Windows XP installs the\r\nsupported Microsoft side-by-side assemblies with their manifests. If you develop your own side-by-side\r\nassemblies, you must also install manifest files. For more information, see Installing Side-by-Side Assemblies and\r\nManifest Files Reference.\r\nManifests and configuration files are not localized.\r\nThe following types of manifests are used with side-by-side assemblies:\r\nAssembly manifests describe side-by-side assemblies. They are used to manage the names, versions,\r\nresources, and dependent assemblies of side-by-side assemblies. The manifests of shared assemblies are\r\nstored in the WinSxS folder of the system. Private assembly manifests are stored either as a resource in the\r\nDLL or in the application folder\r\nApplication manifests describe isolated applications. They are used to manage the names and versions of\r\nshared side-by-side assemblies that the application should bind to at run time. Application manifests are\r\ncopied into the same folder as the application executable file or included as a resource in the application's\r\nexecutable file.\r\nApplication Configuration Files, are manifests used to override and redirect the versions of dependent\r\nassemblies used by side-by-side assemblies and applications.\r\nPublisher Configuration Files, are manifests used to redirect the version of a side-by-side assembly to\r\nanother compatible version. The version that the assembly is being redirected to should have the same\r\nmajor.minor values as the original version.\r\nSource: https://msdn.microsoft.com/en-us/library/aa375365\r\nhttps://msdn.microsoft.com/en-us/library/aa375365\r\nPage 1 of 1",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://msdn.microsoft.com/en-us/library/aa375365"
	],
	"report_names": [
		"aa375365"
	],
	"threat_actors": [],
	"ts_created_at": 1775434265,
	"ts_updated_at": 1775826779,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/6b78c13282dc2992a825d1dfcb593011fafb0555.pdf",
		"text": "https://archive.orkl.eu/6b78c13282dc2992a825d1dfcb593011fafb0555.txt",
		"img": "https://archive.orkl.eu/6b78c13282dc2992a825d1dfcb593011fafb0555.jpg"
	}
}