Click here to Skip to main content
15,916,180 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi,

Out of curriosity, I was trying to look at the content of MyApp.exe.manifest.

As expected, it has list of assembly dlls on which it depends as dependentassembly.

for example:

<dependentassembly dependencytype="preRequisite" allowdelayedbinding="true">
<assemblyidentity name="Microsoft.Windows.CommonLanguageRuntime" version="2.0.50727.0">



I am wondering, MyApp also references System.dll, System.Data.dll etc..so why these assemblies are not included in manifest file as dependent assembly.

Thanks!!!
Posted
Comments
Mohammad A Rahman 21-Feb-12 22:51pm    
Please explain bit more.
Rahul83 21-Feb-12 22:58pm    
I can see all the assembly dlls in generated app.exe.manifest file that I referred in my ConsoleApplications. It makes sense to me as well, because manifest need to have all reference of all dependent assemblies as well.

So I was expecting System.dll, System.Data.dll etc also to be present in manifest file as a dependent assembly, which is not the case, though I added them from Reference->AddReferences.

1 solution

There are few system default namespaces supplied by .NET BCL (Base Class Library), such as System.dll and System.Data.dll

Manifest is the reference for add on assemblies; not default. Hope, it clears your query.
 
Share this answer
 
Comments
Rahul83 22-Feb-12 0:28am    
So, it like that System.dll and System.Data.dll are loaded by CLR by default, inspite of there reference in manifest file as dependent assemblies?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900