/usr/local/share/dotnet/sdk/3.0.100-preview7-012821/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Publish.targets(801,5): error MSB4018: System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath

[buckstephenh]

/usr/local/share/dotnet/sdk/3.0.100-preview7-012821/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Publish.targets(801,5): error MSB4018: System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath

Because there are no specifics in the error message about the actual multiple entries I'm not sure where to look.

[livarcocc]

Can you share a repro of this or share the contents of your csproj file? This is not much for us to go on!

[buckstephenh]

Right which is why the error message needs to be amended to include the multiple entries discovered. Will try to narrow the problem into a repro.

[jonmill]

@livarcocc, @buckstephenh - I hit this too and have a full repro available here: https://github.com/jonmill/bundle-repro

Repro instructions:

1. Clone repro
2. run yarn install
3. run yarn build
4. run dotnet publish -c Release -r linux-x64 /p:PublishSingleFile=true --self-contained

[jonmill]

@livarcocc - I minimized the repro as much as possible from our production code. The repro project is a .NET core project and a React project. I stripped out all JS and C# code and just have the Node dependencies and .NET dependencies without any custom code.

[buckstephenh]

Another one.. https://stackoverflow.com/questions/57224961/error-publishing-with-ppublishsinglefile-true-flag

[feliwir]

Any updates on this? We get this aswell.

[BryanEllis]

I am receiving this on dotnet publish using version 3.0.100-rc1-014190 working with a converted WinForms application. Any details on what is duplicated or what the BundleRelativePath references?

[liuzhy]

I have the same problem.

And I found duplicated reference in my projects, like:

• ProjectA, a library project, reference to "somelib.core.dll"
• ProjectB, an "EXE" project, reference to "somelib.core.dll" and ProjectA

If I publish ProjectB by using "dotnet publish -c Release -r win-x64 /p:PublishSingleFile=true", get an error:
"MSB4018: System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath".

So I removed the reference of "somelib.core.dll" in ProjectB, and publish method works.

[liuzhy]

My dotnet core version is 3.0.100

[Zheltov]

I have same problem!

I was creating new .net core console application with just one nuget reference "Microsoft.Azure.Cosmos".

It's my .csproj file:
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>netcoreapp3.0</TargetFramework> <PublishSingleFile>true</PublishSingleFile> <RuntimeIdentifier>win-x64</RuntimeIdentifier> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.Azure.Cosmos" Version="3.0.0" /> </ItemGroup> </Project>

And i was getting error when published:
The "GenerateBundle" task failed unexpectedly. System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath

[thomhurst]

I've got the same as above: one NuGet reference, Microsoft.Azure.Cosmos.
I'm guessing this package is messing things up ?

[MitchellBot]

I see the same on dotnet 3.1.100-preview1-014459 targeting netcoreapp3.0.
Build Engine 16.4.0-preview-19502-03+3af680463
Similar to @liuzhy, I have a .netcoreapp library which is referenced in a .netcoreapp self-contained exe. Library publishes fine but the exe throws the error.

1>Using "GenerateBundle" task from assembly "C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll".
1>Task Parameter:
1>    FilesToBundle=
1>..... { CONTENT TRIMMED FOR PRIVACY AND BREVITY } .....
1>Task Parameter:IncludeSymbols=False
1>Task Parameter:OutputDir=bin\out\
1>Task Parameter:ShowDiagnosticOutput=False
1>The "GenerateBundle" task failed unexpectedly.
1>System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath
1>   at Microsoft.NET.HostModel.Bundle.Bundler.GenerateBundle(IReadOnlyList`1 fileSpecs)
1>   at Microsoft.NET.Build.Tasks.GenerateBundle.ExecuteCore()
1>   at Microsoft.NET.Build.Tasks.TaskBase.Execute()
1>   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
1>   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========

I removed all unnecessary and duplicate references from the projects but the problem persists. I went through the "FilesToBundle" and find no duplicates there.

EDIT Instead of removing the references from the csproj itself I removed every NuGet package and everything is fine now.

[jtbrower]

SDK : 3.1.100-preview3-014645
Publish Cmd : dotnet publish -r win-x64 -c Release /p:PublishSingleFile=true

Before I make my complaint I should start by saying that this R2R and Publish Single EXE feature is amazing. It addresses something that I have had to do myself with custom work-arounds for years.

That said, I too am hitting this error. I have tried different variations of the publish command and the only variation that works is to not use R2R or Single EXE. I have it working in other simple example projects but put it to the test with a project that references about 128 of my own Nuget packages let alone the third party ones I use too. It would be challenging for me to take the time to pick it apart to find a repro that I could share.

I tried running the command through Visual Studio which threw an exception and pointed me to a log file that had data that was not useful to me personally, but maybe it is to your team. I have included both stack traces, the first was run from the command prompt and the second from within Visual Studio.

Cheers

PowerShell 5 Stack Trace
C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: The "GenerateBundle" task failed unexpectedly. [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj] C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj] C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: at Microsoft.NET.HostModel.Bundle.Bundler.GenerateBundle(IReadOnlyList1 fileSpecs) [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj]
C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: at Microsoft.NET.Build.Tasks.GenerateBundle.ExecuteCore() [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj]
C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: at Microsoft.NET.Build.Tasks.TaskBase.Execute() [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj]
C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj]
C:\Program Files\dotnet\sdk\3.1.100-preview3-014645\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(871,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) [D:\git\OSPOS5\WorkStation\Oceanside.Desktop.App.WorkStation\Oceanside.Desktop.App.WorkStation.csproj]`

Visual Studio Stack Trace
System.AggregateException: One or more errors occurred. ---> System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at Microsoft.Publish.Framework.Model.DefaultPublishSteps.<>c__DisplayClass26_0.<IsBuildCompletedSuccessfully>b__2() at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.Model.DefaultPublishSteps.d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.ViewModel.ProfileSelectorViewModel.d__213.MoveNext()
---> (Inner Exception #0) System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. <---

System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. `

[taori]

I am running into the same issue now. Oddly enough on appveyor it works, azure pipelines does not. even though they apparently use the same sdk version. Is there any fix to this?