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

Upgrade assistant changed unit test project from net6.0-windows to net9.0 causing issues with dependent projects #1622

Open
mobiletonster opened this issue Jan 6, 2025 · 0 comments

Comments

@mobiletonster
Copy link

I have a solution with 4 projects.

Application Current Version Post-Upgrade Version
app.server (ASP.NET Core Server) net6.0 net9.0
app.shared (.NET class library) net6.0 net9.0
app.client (WPF Desktop app) net6.0-windows net9.0-windows
app.test (windows test app) net6.0-windows **net9.0 **

Currently the .test project targets net6.0-windows because it has a reference to the .client (WPF) project and has units test that test the windows desktop application.

When I run the upgrader, it changes the WPF client project appropriately from net6.0-windows to net9.0-windows, however it changes the .test project from .net6.0-windows to just .net9.0. This breaks as a net9.0 project cannot reference another project that is a net9.0-windows project.

The upgrade-assistant should be more aware when upgrading the test project and preserve the -windows state when migrating to the new target.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant