Strange question. It looks like, by some reason, you are convinced that everything in the world (or at least every single widely used media format) has some "namespace" (as if namespaces were some libraries), or in one or another way is exposed to the API you use, such as .NET FCL. This is not so and wasn't meant to be so. Sometimes you need just grab some standard (it it is even publicly available), read it and implement how semantically read/write it. Or find some 3rd-party library.
And this case is way much more typical then the opposite, when the file format is indirectly accessible (say, you can view an image and save your image in this format) but detailed access to the detail of format is not available. This is quite explainable. Exposing it all would require exposing even the detail which remains untouched by the library. Doing it would enormously bloat the library code, and, it would bloat the API even more. And this bloat would be done for the save of some 0.1% of the users, if not less. No such things would really be separate. Say, PE files (DLL and EXE) are written by compilers directly and through CodeDOM (which also uses compilers), but how many perverts would want to dig directly into the internal structure of PE?
At the same time, many formats are available. It's funny, but I can find out the all the formats you listed in your question. What to see:
- PE files (EXE, DLL and more):
This is a part of OpenXML standard, standardized as ECMA-376 and ISO/IEC 29500:
ECMA standard, as always, is publicly available: http://www.ecma-international.org/publications/standards/Ecma-376.htm[^]
The part of MSBuild standard which conforms to the appropriate XML schema and comprehensively described: