Skip to content
New issue

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

Investigate dotnet CLI with MSTest project #4579

Open
1 of 3 tasks
mikebattista opened this issue Jul 22, 2022 · 1 comment
Open
1 of 3 tasks

Investigate dotnet CLI with MSTest project #4579

mikebattista opened this issue Jul 22, 2022 · 1 comment
Assignees
Labels
bug The issue relates to the wizard not working or a problem with the generated code.

Comments

@mikebattista
Copy link
Collaborator

mikebattista commented Jul 22, 2022

Describe the bug

dotnet build and dotnet test are failing with the current MSTest project we have. Adding EnableMSIXTooling = true to the test project csproj gets past the errors at least for an MSIX app project, but results in failures later on related to resources.pri not being dropped in the test build output. Setting WindowsPackageType = None in the app project to run unpackaged breaks dotnet build.

msbuild and vstest.console.exe don't hit these issues with the current test project we have.

To Reproduce

  1. Create a project with an MSTest project
  2. Run dotnet build from the solution folder

Additional context

40613036 - dotnet build of an unpackaged app doesn't work

No response

Applies to the following platforms:

  • WinUI
  • WPF
  • UWP

About your setup

  • Visual Studio Version:
  • Template Studio Wizard Version:
  • Windows Build:
@mikebattista mikebattista added the bug The issue relates to the wizard not working or a problem with the generated code. label Jul 22, 2022
@mikebattista mikebattista added this to the 5.2 milestone Jul 22, 2022
@mikebattista mikebattista self-assigned this Jul 22, 2022
@mikebattista
Copy link
Collaborator Author

The test project will need <EnableMsixTooling>true</EnableMsixTooling> to support .NET CLI. However, that results in resources.pri not being copied to the test project output as expected.

Also, dotnet build with an unpackaged app project seems to be broken independent of Template Studio or the test project.

@mikebattista mikebattista modified the milestones: 5.2, 5.3 Jul 27, 2022
@mikebattista mikebattista removed this from the 5.4 milestone May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue relates to the wizard not working or a problem with the generated code.
Projects
None yet
Development

No branches or pull requests

1 participant