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

Function App In-Place Upgrade Breaks ImplicitUsings Tag #45509

Closed
Ibbylun opened this issue Mar 25, 2025 · 1 comment
Closed

Function App In-Place Upgrade Breaks ImplicitUsings Tag #45509

Ibbylun opened this issue Mar 25, 2025 · 1 comment

Comments

@Ibbylun
Copy link

Ibbylun commented Mar 25, 2025

Type of issue

Bug in Tool

Description

When running the Upgrade tool on a dotnet Function App and upgrading from dotnet version 6.0 to version 8.0 the tool will change the <ImplicitUsings> tag on the functions main .csproj file to enabled example.

<ImplicitUsings>enabled</ImplicitUsings>

This actually breaks the ImplicitUsing functionality around the project and makes it so the user has to add in many using values around the application, it should actually be changed to enable (no d).

<ImplicitUsings>enable</ImplicitUsings>

Page URL

https://learn.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-how-to-upgrade

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/porting/upgrade-assistant-how-to-upgrade.md

Document Version Independent Id

87fbda25-2049-2640-0359-1e31e964334a

Platform Id

9b7adc8d-0a98-c41b-9f65-e66892a831b2

Article author

@adegeo

Metadata

  • ID: 3efc6081-061e-5d0e-3faf-f8a22eadfc4f
  • PlatformId: 9b7adc8d-0a98-c41b-9f65-e66892a831b2
  • Service: dotnet-fundamentals

Related Issues

@adegeo
Copy link
Contributor

adegeo commented Mar 28, 2025

Hello 😄

I was going to tell you to report the issue on the correct repo, but then I found your old issue. You did the correct thing reporting it elsewhere. I would look for some people that work with pull requests in that repo and ping them on github through your issue. That might help get some eyes on the problem.

@adegeo adegeo closed this as completed Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants