-
Notifications
You must be signed in to change notification settings - Fork 10.3k
dotnet publish -> can't find resource files #2035
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
Comments
same problem here
|
Hmm... Following setup works :
But, as soon i'am adding an additional resource file (Resource.de.resx) it doesn't work anymore:
|
Unfortunately, I can only confirm that the problem still exist with us and currently the continuous integration/deployment pipeline for this project is broken. |
I also recently encountered this issue with .NET Core SDK 2.0.0. I stumbled across this issue first but it seems like more of a dotnet/MSBuild issue than ASP.NET. Check out https://github.com/dotnet/cli/issues/6089 instead. |
Closing because this appears to be unrelated to ASP.NET Core, so please refer to the .NET CLI issue. |
* Block enabled 2fa in the UI without cookie consent * Guard against feature not being there * Set up tweak * Fix
I am creating a build in TFS where I have a command line task Publish which runs the following:
Tool: dotnet
Arguments: publish Foo.Api.cproj -c "Release" -f "net461" -r "x86" -o "PublishOuputFolder"
cproj is a dotnet core project, referencing 4.6.1 Framework.
It references a legacy Resource library which references 4.6.1 as well.
Everything is migrated to VS2017.
dotnet --version -> 1.0.1
If I try to publish the proj by using the above task in TFS build or just run it manually from the command prompt, I am getting the following error:
When I check the project folder, I see that all the *.resource files exist in subfolder ...\Foo.ResourceResourceLibrary\obj\Release\ but no dll files
If I build/publish the project in VS 2017 with the same configuration settings, than it creates folder:
...\Foo.ResourceResourceLibrary\obj*x86*\Release\
where all the dll resource files are created properly, then moved to bin folder and publishing is successful.
But if I use dotnet publish (command line or task in tfs build), it doesn't create the dll files in the intermediate output (obj) folder and the Publish task fails.
Any ideas?
The text was updated successfully, but these errors were encountered: