If you are programming a custom Windows Runtime component by hand, one of things you must to do is generate the IDL (Interface Definition Language) file. Once you have that file, you can get the metadata file (.winmd) by using the "MIDLRT" tool.
MIDLRT is a command line tool used to create metadata (.winmd) files that represent the API of your own custom Windows Runtime component.
You can use this nice tool as easy as writing this command:
C:>midlrt filename.idl
One option you can specify is the "metadata_dir" option, like in this example:
C:>midlrt MyRuntimeComponent.idl /metadata_dir "C:\windows\system32\WinMetaData"
When the tool MIDLRT has finished his job, you will have the following files in your current directory:
Another nice tool you can use with all this stuff is "WINMDIDL". This is also a command-line tool you can use to generate automatically IDL files from your metadata files (.winmd) like this:
C:>winmdidl MyRuntimeComponent.winmd
MIDLRT is a command line tool used to create metadata (.winmd) files that represent the API of your own custom Windows Runtime component.
You can use this nice tool as easy as writing this command:
C:>midlrt
One option you can specify is the "metadata_dir" option, like in this example:
C:>midlrt MyRuntimeComponent.idl /metadata_dir "C:\windows\system32\WinMetaData"
When the tool MIDLRT has finished his job, you will have the following files in your current directory:
- dlldata.c
- MyRuntimeComponent.h
- MyRuntimeComponent.winmd
- MyRuntimeComponent_i.c
- MyRuntimeComponent_p.c
Another nice tool you can use with all this stuff is "WINMDIDL". This is also a command-line tool you can use to generate automatically IDL files from your metadata files (.winmd) like this:
C:>winmdidl MyRuntimeComponent.winmd
Comentarios
Publicar un comentario