The following are the errors that al.exe can generate.
Error | Description |
---|---|
al1001 | Internal compiler error
Try to determine if al.exe is failing because of its inability to parse unexpected syntax. Then, contact Microsoft Technical Support. |
al1002 | Out of memory
al.exe ran out of memory and halted. Increase the amount of available memory. |
al1003 | Compiler option 'option' must be followed by an argument
al.exe expected an argument to be passed to a command-line option. For example, if you specify /algid:, you have to pass an ID for an algorithm. |
al1004 | Unexpected NGWS runtime initialization error -- 'reason'
al.exe reported an error with the Visual Studio or NGWS installation. |
al1005 | File 'file' too big to open
All files opened by al.exe must be smaller than 4 GB. |
al1006 | Response file 'file' was already included
The same response file was specified (@file) more than once on the command line. The response file can only be included once. |
al1007 | Error opening response file 'file' -- 'reason'
al.exe could not open the specified response file for the specified reason. |
al1008 | Missing file specification for 'option' command-line option
al.exe expected a file to be passed to a command-line option. For example, if you specify the /out option, then you have to specify a file. |
al1009 | Can't open 'file' for writing
al.exe was unable to write to a file, such as the output assembly file. The disk may be full, the file may be read-only, or you may not have access rights to the file. |
al1010 | Command-line syntax error: Missing ':text' for 'option' option
al.exe expected an argument to be passed to a command-line option. For example, if you specify the /title option, you have to pass a string. |
al1011 | File 'file' is an executable file and cannot be opened as a text file
A binary file was specified where a text file was expected. For example, this error will occur if a binary file is passed on the command line as a response file. |
al1012 | 'value' is not a valid setting for option 'option'
A value was passed to a command-line option that was not expected. For example, this error will occur if you specify an invalid value to the /type option. |
al1013 | Unrecognized command-line option: 'option'
An invalid command-line option was specified. |
al1014 | Unexpected initialization error -- 'reason'
al.exe detected a COM initialization failure. This might be caused by a lack of memory, but a more likely cause is your system DLLs. In this case, you would get a similar error when you ran any OLE/COM-aware program, such as Visual Studio. Reinstall your operating system. |
al1015 | "Unable to find messages file 'alinkui.dll'"
al.exe requires alinkui.dll. Make sure that this file is on your path. If necessary, copy it from the product CD. |
al1016 | No input files were specified
al.exe requires as input one or more files that do not have assembly information. |
al1017 | No target filename was specified
A command-line option was specified but no file was specified. For example, this error will occur if you specify /keyname:. |
al1018 | Required file 'file' could not be loaded
Certain DLLs cannot be loaded. Reinstall Visual Studio or NGWS. |
al1019 | Metadata failure while creating assembly -- 'reason'
Generation of the assembly was interrupted for the specified reason. For example, this error will occur if you specify a file that is not found to the /win32res option. |
al1020 | Ignoring included assembly 'file'
An input file to al.exe had an assembly. al.exe takes as input files that do not have assemblies. |
al1021 | 'setting' : overriding previous setting
A module (MSIL file format but no assembly) had a value for a particular setting, perhaps via custom attributes, and that value was overridden with a value passed via an al.exe command-line option. |
al1022 | Error reading embedded resource 'file' -- 'reason'
al.exe could not read the file passed to the /embedresource option for the specified reason. |
al1023 | Error embedding resource 'file' -- 'reason'
The operating system could not embed the resource file in the assembly. See reason for the specific problem. |
al1024 | File 'file' is not in the same directory as the assembly file 'assembly file'
The input files to an assembly have to be in the same directory in which the assembly will be created, or a subdirectory of that directory. |
al1025 | ComType record 'record' points to an invalid file record 'record'
Metadata in the input module is invalid. The tool that produced the module needs to be fixed. |
al1026 | The version specified 'version' is invalid
See information on the /version option for valid formats. |
al1027 | The operating system specified 'os' is invalid
See information on the /os option for valid formats. |
al1028 | Key file 'file' is missing the private key needed for signing
A key file that only contained the public key was passed to the /keyfile option. The following command line generates a file with a public and private key: |
al1029 | The key container name 'container' does not exist
The value passed to the /keyname option is not a valid container. Use the sn.exe utility to create a container. |
al1030 | The cryptographic service is not installed properly or does not have a suitable key provider
You may need to either reinstall your operating system or install some cryptographic utility that was used in the creation of the key. |
al1031 | Error reading icon 'file' -- 'reason'
al.exe could not read the file that was passed to the /win32icon option. |
al1032 | Error generating resources for 'file' -- 'reason'
Your compilation either used the /win32icon option or did not use the /win32res option, which causes al.exe to generate a file that contains resource information. However, al.exe was unable to create the file due to insufficient disk space or some other error. If you are unable to resolve the file-generation problem, you could use /win32res, which does not generate a file that contains resource information. |
al1033 | Assembly custom attribute 'attribute' was specified multiple times with different values
Different values were passed to two custom attributes in source modules that are input to al.exe. |
al1034 | Assembly 'file' cannot be copied or renamed.
While using the al.exe syntax that allows you to both specify an input file and copy it, a name conflict arose such that the compiler could not continue. For example, this error will occur if you specify something like |
al1035 | Libraries cannot have a main method specified
When using the /type:lib option, which is the default, you cannot also specify the /main option. |
al1036 | Main method required for console and windows apps
When using the /type:exe or /type:win option, you must also specify the /main option. |
al1037 | Unable to find main method 'main'
al.exe was unable to find a Main method at the location specified by the /main option. |
al1038 | '/install' and '/out' cannot both specify a filename
If the /out option is specified, the assembly will be installed (/install) in the global cache with the name passed to /out. |
al1039 | Initialization of global assembly cache manager failed -- 'reason'
Reinstall Visual Studio or NGWS. |
al1040 | Failed to install assembly into cache -- 'reason'
Only signed assemblies can be installed into the cache. If an assembly is not signed, and you specify the /install option, you will get this error. There are other reasons why installing into the cache might fail; see the Global Assembly Cache help topics for more information. |
al1041 | 'method': main method does not have proper signature
A method was specified with the /main option, but that method either was not static, did not return int or void, or has invalid arguments. |
al1042 | 'exe': EXEs cannot be added modules
An .exe that did not have an assembly was specified as an input file to al.exe. al.exe can only take .dll files as input files without assemblies. |
al1043 | Manifest filename 'name' cannot be the same as any modules
The name specified to the /out option cannot be the same as any of the files that are specified as input to al.exe. |
al1044 | Error reading key file 'file' -- 'reason'
An error occurred while opening or reading from a file specified with /keyfile or KeyFileAttribute. |