0

According to the documentation, it is possible to deploy to Azure by updating a git repository.

I have attempted the walkthrough here.

I created this github repository, then generated an ASP.NET MVC project from the Visual Studio template.

Looking at the logs, Azure detected the checkin, but provided this unhelpful message:

Using the following command to generate deployment script: 'azure site deploymentscript -y --no-dot-deployment -r "D:\home\site\repository" -o "D:\home\site\deployments\tools" --basic'.

Generating deployment script for Web Site

Generated deployment script files

Found solution 'D:\home\site\repository\kudu-deployment-test.sln' with no deployable projects. Deploying files instead.

Why is my straight-out-of-the-box ASP.NET project not a 'deployable project'?

What can I do to fix it so it is?

1 Answer 1

2

Your solution file as it currently exists in your GitHub repository does not contain any project information as the error suggests. I downloaded a copy of your repo and opened the solution in Visual Studio 2015 and it did not have any projects associated with it.

https://github.com/AndrewShepherd/kudu-deployment-test/blob/master/kudu-deployment-test.sln

Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 14 VisualStudioVersion = 14.0.25420.1 MinimumVisualStudioVersion = 10.0.40219.1 Global GlobalSection(SolutionProperties) = preSolution HideSolutionNode = FALSE EndGlobalSection EndGlobal 

Once I added the existing project from the files in the repository, this is what my updated solution file looked like:

Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 14 VisualStudioVersion = 14.0.25420.1 MinimumVisualStudioVersion = 10.0.40219.1 Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "kudu-deployment-test", "kudu-deployment-test\kudu-deployment-test.csproj", "{AA0F0FD5-559E-4125-87A7-F7C3173DE079}" EndProject Global GlobalSection(SolutionConfigurationPlatforms) = preSolution Debug|Any CPU = Debug|Any CPU Release|Any CPU = Release|Any CPU EndGlobalSection GlobalSection(ProjectConfigurationPlatforms) = postSolution {AA0F0FD5-559E-4125-87A7-F7C3173DE079}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {AA0F0FD5-559E-4125-87A7-F7C3173DE079}.Debug|Any CPU.Build.0 = Debug|Any CPU {AA0F0FD5-559E-4125-87A7-F7C3173DE079}.Release|Any CPU.ActiveCfg = Release|Any CPU {AA0F0FD5-559E-4125-87A7-F7C3173DE079}.Release|Any CPU.Build.0 = Release|Any CPU EndGlobalSection GlobalSection(SolutionProperties) = preSolution HideSolutionNode = FALSE EndGlobalSection EndGlobal 

If your project is correctly visible in Visual Studio, I would make sure that your solution file is saved and the updated version is pushed to your repo. Since you have already setup continuous deployment from GitHub, once you fix the solution file, your project should automatically deploy correctly.

Sign up to request clarification or add additional context in comments.

1 Comment

Dammit. I didn't save the solution before I committed. :-(

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.