Azure publish not working

Question

Azure publish not working

Thibaut Fabrice 0

Dear everyone,

Can you help to know how to remove this error for Azure?

User's image

Awaitng your reply,

Best Regards,

Fabrice

Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-02T17:18:06.1266667+00:00
HI @Thibaut Fabrice

Thanks for posting the screenshots and the details I can see exactly what’s happening.

The two CS1570 warnings you’re seeing (in POSConverters.cs line 765) are just malformed XML documentation comments. They’re not errors and won’t stop a publish. You can quickly silence them by fixing the /// comments (escape any < or > characters) or by turning off XML documentation in the project properties if you don’t need it.

The real reason Azure Publish isn’t working is that you’re trying to publish the .NET MAUI Android project (POSJOSEA (net10.0-android)). Azure App Service is designed for web apps and APIs, not mobile apps. That’s why the Publish option looks broken or does nothing useful.

Quick fix:

In Solution Explorer, expand your solution.

Right-click the web/API project (the one that contains AzureBlobStorageService.cs, SaleRepository.cs, etc. — it should be a .NET web app or Azure Functions project, not the Android one).

Choose Publish> Azure > Azure App Service (Windows/Linux) and follow the wizard.

Reference :

https://learn.microsoft.com/en-us/dotnet/csharp/misc/cs1570

https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-10.0

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Thibaut Fabrice 0 Reputation points

2026-04-03T04:57:04.9233333+00:00

Awating your reply,

Best Regards,

Fabrice
Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-03T16:46:39.3666667+00:00
HI @Thibaut Fabrice

Thanks for the additional screenshots — that really helped clarify things.

The main issue is that your POSJOSEA.Api (the backend Web API) is currently excluded in the main project file. This is why you don’t see a separate web project in Solution Explorer and why the Azure Publish option isn’t behaving as expected.

Quick Solution:

In Solution Explorer, click the Show All Files button at the top.

Locate the POSJOSEA.Api folder.

Right-click the POSJOSEA.Api.csproj file >Include in Project.

If the .csproj file isn’t visible on disk, right-click your solution >Add > Existing Project, then browse to the POSJOSEA.Api folder and select the .csproj file.

Once the API project appears:

Right-click the POSJOSEA.Api project (not the MAUI one).

Select Publish > Azure > Azure App Service (Windows/Linux).

Follow the wizard to create or select your App Service and publish.

This should get your backend live on Azure.

Reference:

https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-10.0

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-sln

After publishing the API, just update the base URL in your MAUI app (usually in a config file or settings class) to point to the new Azure URL.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-06T16:00:39.87+00:00

HI @Thibaut Fabrice

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?

1 answer

Your answer

Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-02T17:18:06.1266667+00:00

HI @Thibaut Fabrice

Thanks for posting the screenshots and the details I can see exactly what’s happening.

The two CS1570 warnings you’re seeing (in POSConverters.cs line 765) are just malformed XML documentation comments. They’re not errors and won’t stop a publish. You can quickly silence them by fixing the /// comments (escape any < or > characters) or by turning off XML documentation in the project properties if you don’t need it.

The real reason Azure Publish isn’t working is that you’re trying to publish the .NET MAUI Android project (POSJOSEA (net10.0-android)). Azure App Service is designed for web apps and APIs, not mobile apps. That’s why the Publish option looks broken or does nothing useful.

Quick fix:

In Solution Explorer, expand your solution.

Right-click the web/API project (the one that contains AzureBlobStorageService.cs, SaleRepository.cs, etc. — it should be a .NET web app or Azure Functions project, not the Android one).

Choose Publish> Azure > Azure App Service (Windows/Linux) and follow the wizard.

Reference :

https://learn.microsoft.com/en-us/dotnet/csharp/misc/cs1570

https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-10.0

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Thibaut Fabrice 0 Reputation points

2026-04-03T04:57:04.9233333+00:00

Awating your reply,

Best Regards,

Fabrice
Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-03T16:46:39.3666667+00:00

HI @Thibaut Fabrice

Thanks for the additional screenshots — that really helped clarify things.

The main issue is that your POSJOSEA.Api (the backend Web API) is currently excluded in the main project file. This is why you don’t see a separate web project in Solution Explorer and why the Azure Publish option isn’t behaving as expected.

Quick Solution:

In Solution Explorer, click the Show All Files button at the top.

Locate the POSJOSEA.Api folder.

Right-click the POSJOSEA.Api.csproj file >Include in Project.

If the .csproj file isn’t visible on disk, right-click your solution >Add > Existing Project, then browse to the POSJOSEA.Api folder and select the .csproj file.

Once the API project appears:

Right-click the POSJOSEA.Api project (not the MAUI one).

Select Publish > Azure > Azure App Service (Windows/Linux).

Follow the wizard to create or select your App Service and publish.

This should get your backend live on Azure.

Reference:

https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-10.0

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-sln

After publishing the API, just update the base URL in your MAUI app (usually in a config file or settings class) to point to the new Azure URL.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-06T16:00:39.87+00:00

HI @Thibaut Fabrice

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?

Answer 1

You’re trying to use Azure “Publish” from a project that Visual Studio doesn’t treat as deployable to Azure. The project shown is net10.0-android, which is a mobile app, and those don’t get published to Azure App Service directly. Azure publishing in Visual Studio is designed for server-side projects like ASP.NET Core web apps or APIs. A mobile app is something you build into an APK or AAB and distribute through app stores or side-load, not deploy to Azure.

If your goal is to use Azure with this app, then what you actually need is a backend hosted on Azure. That means creating or using an ASP.NET Core Web API project and publishing that instead. The mobile app then calls that API over HTTP.

If you already have a backend project in the solution, right-click that project (not the Android one) and use Publish. If you don’t have one, create it with:

dotnet new webapi -n MyApi

Then move your data access code into that API and expose endpoints like:

[HttpGet("sales")]
public async Task<IEnumerable<Sale>> GetSales()
{
    return await _repo.GetSales();
}

After that, publish the API to Azure App Service, and point your Android app to the API URL.

If instead you’re directly using Azure services like Blob Storage from the app, then there is nothing to publish. You just configure the SDK with credentials and endpoints, but you need to be careful not to expose secrets in a mobile app.

Also note that your solution shows many warnings. Even if they’re not the root cause, they can break builds and publishing indirectly. Fix at least the XML comment errors like:

/// The character(s) '<' cannot be used here

Those come from malformed XML comments and should be cleaned up.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Praneeth Maddali 6,935 Reputation points Microsoft External Staff Moderator

2026-04-02T17:22:58.8833333+00:00

HI @Thibaut Fabrice

Kindly let us know if the above helps or you need further assistance on this issue.

If you have any other questions, let me know in the "comments" and I would be happy to help you

Share via

Azure publish not working

1 answer

Your answer