Propriedades de Arquivo

Artigo
08/08/2011

You can use file properties to indicate what actions the project system should perform on the files. For example, you can set file properties to indicate whether a file should be compiled or embedded into the build output as a resource.

You can select any file in Solution Explorer and then examine its properties in the Properties window. Arquivos de Visual Basic e C# Visual têm quatro propriedades: Nome do arquivo, criar a ação, ferramenta personalizada, e Custom Tool Namespace.

Observação
O Build Action, Ferramenta personalizada, e Custom Tool namespace propriedades são fornecidas para cenários avançados. The default values are typically sufficient and do not have to be changed.

Propriedade de nome de arquivo

Você pode renomear um arquivo clicando no Nome de arquivo propriedade na janela Properties e digitando o novo nome. Notice that if you change the file's name, Visual Studio will automatically rename any .vb or .resx files that are associated with it.

Propriedade da ação de compilação

O Build Action propriedade indica o que Visual Studio faz com que um arquivo, quando uma compilação é executada. Ação de compilação pode ter um dos vários valores:

None - The file is not included in the project output group and is not compiled in the build process. An example is a text file that contains documentation, such as a Readme file.
Compile - The file is compiled into the build output. This setting is used for code files.
Content - The file is not compiled, but is included in the Content output group. For example, this setting is the default value for an .htm or other kind of Web file.

Embedded Resource - This file is embedded in the main project build output as a DLL or executable. It is typically used for resource files.

Observação
O Build Action propriedade é extensível. Como resultado, você poderá ver opções adicionais listadas para esta propriedade que foram adicionadas por outros produtos e recursos.

O valor padrão para Build Action depende da extensão do arquivo que você adiciona à solução. Por exemplo, se você adicionar um Visual Basic o projeto ao Solution Explorer, o valor padrão para Build Action é compilar. This is because the extension .vb indicates a code file that can be compiled. File names and extensions appear in Solution Explorer.

Note that the name of the file in your project will not be the identifier for the managed resource in the assembly manifest (see Assembly Manifest for more information). O identificador será namespace.filename.extension, onde namespace é o valor da DefaultNamespace propriedade em um projeto do Visual C# ou RootNamespace propriedade em um Visual Basic project. Filename and extension remain the same as their original designation. If the file is a .resx file, the project system will run resgen.exe on the file, creating a .resource file. The .resource file will be embedded in the assembly. Therefore, the assembly manifest will refer to the .resources file and not the .resx file.

For example, if you add the file MyFile.bmp to a project whose default namespace is MyProj, and set the build action to Embedded Resource, MyProj.MyFile.bmp will be the identifier in the assembly manifest. If you then add the file MyFile.resx to the project, the default build action will be Embedded Resource and MyProj.MyFile.resources will be the identifier in the assembly manifest.

Note that when the resource editor adds an image, it sets Build Action to None, because the .resx file references the image file. At build time, the image is pulled into the .resources file created out of the .resx file. The image can then easily be accessed by way of the strongly-typed class auto-generated for the .resx file. Therefore, you should not change this setting to Embedded Resource, because doing this would include the image two times in the assembly.

Para obter mais informações sobre como acessar os arquivos de recurso (compilados a partir de arquivos. resx) em tempo de execução, consulte ResourceManager. Para obter mais informações sobre como acessar todos os outros incorporados a arquivos e recursos em tempo de execução, consulte GetManifestResourceStream.

Copiar para a propriedade de diretório de saída

This property specifies the conditions under which the selected source file will be copied to the output directory. Select Do not copy if the file is never to be copied to the output directory. Select Copy always if the file is always to be copied to the output directory. Select Copy if newer if the file is to be copied only when it is newer than an existing file of the same name in the output directory.

Para obter informações sobre como alterar o diretório de saída, consulte Compilação de página, Designer de projeto c (#) ou Compilar a página, Designer de projeto (Visual Basic).

Observação
In smart device projects, the newness of a .dll or .exe file is determined by comparing the Win32 versions as follows: If the device-side version is less than that of the desktop, the file is copied. If the device-side version is greater than that of the desktop, the file is not copied. If the versions are the same, a checksum comparison is made. If the checksums are the same, the file is not copied. If the checksums are different, the file is copied. The newness of files other than .dll and .exe is based only on checksum.

In smart device projects, the newness of a .dll or .exe file is determined by comparing the Win32 versions as follows:

If the device-side version is less than that of the desktop, the file is copied.

If the device-side version is greater than that of the desktop, the file is not copied.

If the versions are the same, a checksum comparison is made. If the checksums are the same, the file is not copied. If the checksums are different, the file is copied.

The newness of files other than .dll and .exe is based only on checksum.

Observação
Data files will be copied to a subfolder named Data Files in the output directory.

Propriedade personalizada da ferramenta

Custom tools are components that can be used to transform files from one type to another at design time. For example, a custom tool might be a dataset code generator that reads in an XML Schema (.xsd) file and generates classes in a code file that programmatically exposes its tables and columns. There is a predefined list of custom tools available in the product; this property enables you to see which custom tool is applied to a file. In rare circumstances, you might have to change the value of this property. The value of this property must be either blank or one of the built-in custom tools.

To set or change the custom tool, click the CustomTool property in the Properties window and type the name of a custom tool.

Propriedade Namespace de ferramenta personalizada

Se você tiver uma ferramenta personalizada atribuída ao seu projeto, o Namespace da ferramenta personalizada propriedade permite que você especifique o namespace que você deseja atribuir ao código gerado pela ferramenta personalizada. Quando você especifica um valor para o Custom Tool namespace propriedade, o código gerado pela ferramenta é colocada no namespace especificado. If the property is empty, generated code is put in the default namespace for the folder in which the converted file is located. For Visual Basic, this is the project's root namespace, and for Visual C# this corresponds to the setting of the DefaultNamespace property for the folder.