We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In .NET projects, when a resource file is added using the VS UI, the files may not be indexed by default.
Examples of this issue:
If the files are added through UI, VS will automatically add something like this for a WPF app:
<ItemGroup> <Content Remove="<image file name>" /> </ItemGroup> <ItemGroup> <PRIResource Remove="<resw file name>" /> </ItemGroup>
For a WinForm/Console app, what’s added is a little different:
<ItemGroup> <Content Remove="<image file name>" /> </ItemGroup> <ItemGroup> <None Remove="<resw file name>" /> </ItemGroup>
Content Remove and PRIResource Remove entries should not appear in the CSPROJ file.
Content Remove
PRIResource Remove
To work around this issue, please remove the entries below in the CSPROJ file (the None Remove entries can remain):
None Remove
No response
1.0.0-preview3
Packaged (MSIX), Unpackaged
Insider Build (xxxxx)
Visual Studio 2019
The text was updated successfully, but these errors were encountered:
Closing since this is a dupe of #1674
Sorry, something went wrong.
rohanp-msft
No branches or pull requests
Describe the bug
In .NET projects, when a resource file is added using the VS UI, the files may not be indexed by default.
Steps to reproduce the bug
Examples of this issue:
If the files are added through UI, VS will automatically add something like this for a WPF app:
For a WinForm/Console app, what’s added is a little different:
Expected behavior
Content Remove
andPRIResource Remove
entries should not appear in the CSPROJ file.Work around
To work around this issue, please remove the entries below in the CSPROJ file (the
None Remove
entries can remain):Screenshots
No response
NuGet package version
1.0.0-preview3
Packaging type
Packaged (MSIX), Unpackaged
Windows version
Insider Build (xxxxx)
IDE
Visual Studio 2019
Additional context
No response
The text was updated successfully, but these errors were encountered: