Docker msbuild error msb1009 project file does not exist

I am trying to build a docker image for an ASP.NET Core 3.1 application and I fail to restore the packages. My solution has multiple projects and after copying all the project files, I am trying to create a layer which contains restored dependencies only.

The docker file

FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 AS base
WORKDIR /app
EXPOSE 80

FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build
WORKDIR /src
COPY ["ExampleApi/ExampleApi.csproj", "ExampleApi/ExampleApi/"]
COPY ["Common.Web/Common.Web.csproj", "ExampleApi/Common.Web/"]
COPY ["Example.Data/Example.Data.csproj", "ExampleApi/Example.Data/"]
COPY ["Example.Services/Example.Services.csproj", "ExampleApi/Example.Services/"]

RUN mkdir /tmp/build/
COPY . /tmp/build
RUN find /tmp/build -name *.csproj

RUN dotnet restore "ExampleApi/ExampleApi.csproj" --verbosity detailed
COPY . .
WORKDIR "/src/ExampleApi/ExampleApi"
RUN dotnet build "ExampleApi.csproj" -c Release -o /app --no-restore

FROM build AS publish
RUN dotnet publish "ExampleApi.csproj" -c Release -o /app

FROM base AS final
WORKDIR /app
COPY --from=publish /app .
ENTRYPOINT ["dotnet", "ExampleApi.dll"]

Docker build

I am running without cache to be able to output all the csproj files within the container for each run (otherwise it gets cached and the files are not longer displayed).

docker build --no-cache -f ExampleApi/Dockerfile .

Sending build context to Docker daemon  116.4MB
Step 1/22 : FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 AS base
 ---> a843e0fbe833
Step 2/22 : WORKDIR /app
 ---> Running in e33e9c821c0b
Removing intermediate container e33e9c821c0b
 ---> eec973a226e0
Step 3/22 : EXPOSE 80
 ---> Running in 8e813a3a8b85
Removing intermediate container 8e813a3a8b85
 ---> c8d95a3a1de4
Step 4/22 : FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build
 ---> cef7866e800b
Step 5/22 : WORKDIR /src
 ---> Running in f56bf9402ed1
Removing intermediate container f56bf9402ed1
 ---> 55694332db0e
Step 6/22 : COPY ["ExampleApi/ExampleApi.csproj", "ExampleApi/ExampleApi/"]
 ---> 4beb2e169ec7
Step 7/22 : COPY ["Common.Web/Common.Web.csproj", "ExampleApi/Common.Web/"]
 ---> ed7a9c81e8f7
Step 8/22 : COPY ["Example.Data/Example.Data.csproj", "ExampleApi/Example.Data/"]
 ---> aaca52c111b4
Step 9/22 : COPY ["Example.Services/Example.Services.csproj", "ExampleApi/Example.Services/"]
 ---> efb15c17a096
Step 10/22 : RUN mkdir /tmp/build/
 ---> Running in 7da9eae324ca
Removing intermediate container 7da9eae324ca
 ---> b06126b19a7f
Step 11/22 : COPY . /tmp/build
 ---> 04598eaab98c
Step 12/22 : RUN find /tmp/build -name *.csproj
 ---> Running in 2fd26dba963d
/tmp/build/ExampleApi/ExampleApi.csproj
/tmp/build/Example.Data/Example.Data.csproj
/tmp/build/Common.Web/Common.Web.csproj
/tmp/build/Example.Sql/Example.!Sql.csproj
/tmp/build/Example.Services/Example.Services.csproj
/tmp/build/Example.Services.Tests/Example.Services.Tests.csproj
/tmp/build/Example.IdentityServer.Infrastructure/Example.IdentityServer.Infrastructure.csproj
/tmp/build/Example.IdentityServer/Example.IdentityServer.csproj
/tmp/build/Example.Data.Tests/Example.Data.Tests.csproj
/tmp/build/ExampleIntegrationApi/ExampleIntegrationApi.csproj
Removing intermediate container 2fd26dba963d
 ---> 78eadf796305
Step 13/22 : RUN dotnet restore "ExampleApi/ExampleApi.csproj" --verbosity detailed
 ---> Running in 5dc9b5bbd04e
MSBUILD : error MSB1009: Project file does not exist.
Switch: ExampleApi/ExampleApi.csproj
The command '/bin/sh -c dotnet restore "ExampleApi/ExampleApi.csproj" --verbosity detailed' returned a non-zero code: 1

find indicates that ExampleApi/ExampleApi.csproj is there, yet the dotnet restore complains about not finding it.

Error MSB1009: Project file does not exist is no longer a problem with this handy solution by our Support Techs.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped out a customer with the error MSB1009: Project file does not exist.

How to resolve error MSB1009: Project file does not exist

Have you been facing the following messages recently?

MSBUILD: error MSB1009: Project file does not exist.

Switch: ProjectName.csproj

ERROR: Service 'ServiceName' failed to build: The command '/bin/sh -c dotnet restore "ProjectName.csproj"' returned a non-zero code: 1

Fortunately, our Support Techs have a solution up their sleeves. After helping several customers with a similar issue, our Support Team recommends ensuring the Dockerfile is in the root of the project. Furthermore, we have to modify the settings in the docker-compose.yml file as shown below:

FROM mcr.microsoft.com/dotnet/core/runtime:2.2-stretch-slim AS base

WORKDIR /app

EXPOSE PortNumberOpenedOnDatabaseServer


FROM mcr.microsoft.com/dotnet/core/sdk:2.2-stretch AS build

WORKDIR /src

COPY ["ProjectName.csproj", "ProjectName/"]

RUN dotnet restore "./ProjectName.csproj"

COPY . .

WORKDIR "/src/."

RUN dotnet build "ProjectName.csproj" -c Release -o /app/build



FROM build AS publish

RUN dotnet publish "ProjectName.csproj" -c Release -o /app/publish



FROM base AS final

WORKDIR /app

COPY --from=publish /app/publish .

ENTRYPOINT ["dotnet", "ProjectName.dll"]

Here, we will build the Docker Image via the sudo docker-compose build command. We can also build and run the container at the same time by running sudo docker-compose up in the folder where docker-compose.yml is present.

According to our Support Techs, the docker-compose.yml should include the correct path for this to work seamlessly and hence no longer see this error message

When we avoid pruning images or docker containers no longer in use, the second command for building images will fail. In other words, we have to clean the Docker System with the following command:

sudo docker system prune -a

Furthermore, we can verify this with the sudo docker images command and then proceed with the sudo docker-compose build command to build images. Once we get this doen, we will not come across the MSB1009 error message.

[Looking for a solution to another query? We are just a click away.]

Conclusion

In short, the skilled Support Engineers at Bobcares demonstrated how to resolve the Project file does not exist error.

Error MSB1009: Project file does not exist | How to fix

by Nikhath K | Jan 5, 2022

Error MSB1009: Project file does not exist is no longer a problem with this handy solution by our Support Techs.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped out a customer with the error MSB1009: Project file does not exist.

How to resolve error MSB1009: Project file does not exist

Have you been facing the following messages recently?

Fortunately, our Support Techs have a solution up their sleeves. After helping several customers with a similar issue, our Support Team recommends ensuring the Dockerfile is in the root of the project. Furthermore, we have to modify the settings in the docker-compose.yml file as shown below:

Here, we will build the Docker Image via the sudo docker-compose build command. We can also build and run the container at the same time by running sudo docker-compose up in the folder where docker-compose.yml is present.

According to our Support Techs, the docker-compose.yml should include the correct path for this to work seamlessly and hence no longer see this error message

When we avoid pruning images or docker containers no longer in use, the second command for building images will fail. In other words, we have to clean the Docker System with the following command:

Furthermore, we can verify this with the sudo docker images command and then proceed with the sudo docker-compose build command to build images. Once we get this doen, we will not come across the MSB1009 error message.

[Looking for a solution to another query? We are just a click away.]

Conclusion

In short, the skilled Support Engineers at Bobcares demonstrated how to resolve the Project file does not exist error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник

FreeCAD Forum

The help and development forum of FreeCAD

Compile on windows. MSBUILD error MSB1009 Project file does not exist.

Compile on windows. MSBUILD error MSB1009 Project file does not exist.

Post by DeepSOIC » Thu Sep 10, 2020 7:54 pm

22:45:30: Running steps for project FreeCAD.
22:45:30: Starting: «S:Qtcmake3-14-3bincmake.exe» —build . —target all
Microsoft (R) Build Engine version 16.0.461+g6ff56ef63c for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1009: Project file does not exist.
Switch: all.vcxproj
22:45:30: The process «S:Qtcmake3-14-3bincmake.exe» exited with code 1.
Error while building/deploying project FreeCAD (kit: Desktop (x86-windows-msvc2019-pe-64bit))
When executing step «CMake Build»
22:45:30: Elapsed time: 00:00.

Re: Compile on windows. MSBUILD error MSB1009 Project file does not exist.

Post by DeepSOIC » Thu Sep 10, 2020 8:23 pm

Qt Creator 4.13.0

In cmake output (see attached file), there are two things that catch my attention:

Re: Compile on windows. MSBUILD error MSB1009 Project file does not exist.

Post by DeepSOIC » Thu Sep 10, 2020 8:28 pm

Hmm. creating a symlink «ALL.vcxproj» to ALL_BUILD.vcxproj in the build directory seems to have solved it, it’s building something. now i just wait for it to finish.

EDIT: it is built, and runs. Still wondering, why did I have to do that, doesn’t look right to me.

Re: Compile on windows. MSBUILD error MSB1009 Project file does not exist.

Post by DeepSOIC » Thu Sep 10, 2020 9:25 pm

Источник

Ошибка развертывания .net core azure: файл проекта не существует

у меня есть приложение app-service, настроенное в Azure, которое будет развернуто после фиксации в репозитории team-services git. До сих пор это работало нормально, и развертывание завершается с ошибкой:

однако, если я открою консоль azure и компакт-диск в каталог проекта, я увижу, что файл проекта (asp.net ядро .xproj) действительно существует. Я знаю его в правильном каталоге из вывода в журнале развертывания, показывая, что пакеты находятся восстановлено:

интересно, что у меня есть два приложения app-service, указывающие на разные проекты в одном решении. Suddently они оба терпят неудачу с тем же сообщением об ошибке, даже если они развертывают разные проекты.

любая помощь очень ценится.

редактировать

у меня уже был глобальный.json в моем корне решения (на том же уровне, что и мой .sln файл), но это указывало на более старая версия SDK, поэтому я обновил это, и это не имело никакого значения. Затем я попытался избавиться от «тестового» проекта в файле json, и это тоже не имело значения. Все еще не удается с той же ошибкой

1 ответов

по-видимому, вам нужно явно указать версию SDK в вашем глобальном.JSON в противном случае Kudu использует последнюю версию, которая теперь является preview3, которая несовместима.

будьте осторожны, вы глобальной.файл json должен жить в корне вашего репозитория.

Источник

Msbuild error msb1009 файл проекта не существует

Answered by:

Question

Using VS2015 solution. Using VSTS Online (https:// .visualstudio.com/

). Using VS source control repository, Using Visual Studio Build process in VSTS. Using «Hosted» Agent queue for build process. Build configuration = «Release»

Created simple source controlled SSRS solution in VSTS successfully mapped and managed in VS2015. Able to build successfully in VS2015. However when building in VSTS I always get error: «MSB1009: Project file does not exist»

In VSTS the build process is comprised of only 2 processes 1: Get Sources & 2 Build Solution (Visual Studio Build).

Under the Get sources process I have the correct Repository and for Workspace mappings I have Type=Map & Server path = $/ / . I think the issue is with Local path under $(build.sourcesDirectory) I am leaving it blank because I do not know what to put in it.

The log from the build is shown below. As you can see the project file does exist (yellow highlighte). I am not sure what the «switch» means. Any help would be appreciated. I’m trying to learn how to Build in the Cloud. (DEVOps)

Источник

MSBUILD: ошибка MSB1009: файл проекта не существует

Я пытаюсь реализовать CI (непрерывная интеграция) с использованием TFS для моего веб-сайта ASP.NET(Website Project). Я постоянно получаю следующие ошибки в течение нескольких дней. Ниже приведен полный журнал. Его просто не получают последнюю версию в локальном каталоге, поэтому его выдача ошибки. MSBUILD: ошибка MSB1009: Файл проекта не существует. Я проверил, что TFS не получает последнюю версию, я не уверен, почему. .

Любая помощь действительно оценена, спасибо заранее.

Согласно вашему протоколу и описанию, кажется, что команда TFS get (Get Source Step) ошибочно возвращает «Все файлы обновлены». и привести к следующему шагу MSBuild.

Сначала попробуйте выполнить шаги, чтобы проверить, работает ли он, установив очистку во время получения источника:

Измените свое определение: в репозитории установите » Очистить» на » Истинный», » Очистить» параметр «Источники» (попробуйте установить исходный каталог, если это не работает) Также включите параметр » Очистить» для решения задачи сборки

Другая возможность — папка с корневыми источниками ( D:UAMCAgent_work3s ) не отображается, т. D:UAMCAgent_work3s пространство не содержит сопоставления корней.

И предложите вам дважды проверить соответствующее разрешение учетной записи сборки, а также дать ему разрешение локального администратора на агенте сборки.

Вы можете отключить исходные шаги по умолчанию в определении сборки. И используйте свой собственный скрипт, чтобы получить исходные/выталкивающие файлы, чтобы увидеть, получится ли у вас такая же ситуация. Как это сделать, пожалуйста, следуйте: возможно ли проигнорировать/отключить первый шаг? Получить источник в vNext Build?

Источник

I read some documentation on how to setup a docker file for an asp.net core project.
I have a rest api named dsi.rest.app and I try to create a dockerfile.

I followed tutorials and created a Dockerfile in the dsi.rest.app folder. The following folder is containing the solution i want to dockerise.

FROM mcr.microsoft.com/dotnet/sdk:5.0 AS build
WORKDIR /DockerSource

# Copy csproj and restore as distinct layers
COPY *.sln .
COPY *.csproj ./
RUN dotnet restore

# Copy everything else and build website
COPY /. ./
WORKDIR /DockerSource/dsi.rest.app
# RUN dotnet publish -c release -o /DockerOutput/dsi.rest.app --no-restore
RUN dotnet build "dsi.rest.app.csproj" -c Release -o /DockerOutput/dsi.rest.app --no-restore

# Final stage / image
FROM mcr.microsoft.com/dotnet/aspnet:5.0
WORKDIR /DockerOutput/dsi.rest.app
COPY --from=build /DockerOutput/dsi.rest.app ./
ENTRYPOINT ["dotnet", "dsi.rest.app.dll"]

I try to build the image:

docker build --pull -t dsi.rest.rest .

And I obtain an error message:

 => ERROR [build 8/8] RUN dotnet build "dsi.rest.app.csproj" -c Release -o /DockerOutput/dsi.rest.app --no-restore                    0.5s
#15 0.505 MSBUILD : error MSB1009: Project file does not exist.
#15 0.505 Switch: dsi.rest.app.csproj

the project file is situated at the same level as the dockerfile. the csproj file is at the same folder level as the Dockerfile.

My csproj file contains the following information :

<Project Sdk="Microsoft.NET.Sdk.Web">

    <PropertyGroup>
        <TargetFramework>net5.0</TargetFramework>
        <UserSecretsId>4b7e5335-798e-4066-a795-83e772338899</UserSecretsId>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.Bcl.AsyncInterfaces" Version="5.0.0" />
        <PackageReference Include="Pomelo.EntityFrameworkCore.MySql" Version="3.2.4" />
        <PackageReference Include="Microsoft.VisualStudio.Azure.Containers.Tools.Targets" Version="1.10.13" />
        <PackageReference Include="MsgReader" Version="3.12.4" />
        <PackageReference Include="Newtonsoft.Json" Version="13.0.1" />
        <PackageReference Include="Swashbuckle.AspNetCore" Version="6.1.1" />
    </ItemGroup>

    <ItemGroup>
      <Folder Include="PropertiesPublishProfiles" />
    </ItemGroup>

</Project>

I ran the command : dotnet build «dsi.rest.app.csproj» -c Release -o /DockerOutput/dsi.rest.app —no-restore
without any problem. It did generate my application in C:/DockerOutput/dsi.rest.app