help fixing a build warning

we have a .NET CORE 3.0 project. I have made a very simplified version. while building we regularly get the warning: >ALINK : warning AL1073: Referenced assembly '[login to view URL]' targets a different processor

we are unable to disable the warning, or fix the issue. We have pinned the issue down to the resource file, but need assistance fixing the build warning. Some research was done on [login to view URL] without success.

We need someone wiht some experience setting paths and working with the xml .csproj file in the attached solution.

The attached simplified .csproj file reproduces the problem. NOTE: we absolutley need to compile in x64 due to other dependencies, so we somehow need to work with [login to view URL] for 64bits for .NET core 3.0

Skills: Assembly, C# Programming, .NET

See more: visual studio 2017 error list not showing, visual studio 2019 treat warnings as errors, build error c++, visual studio error codes, compiler warnings, treat warnings as errors visual studio 2017, how to resolve build errors in visual studio, need help fixing cre loaded, help fixing html coding, help fixing joomla site, help fixing video chat, tutorial build directory indesign xml, build search box xml, oscommerce help fixing bugs, flex build accordion dynamically xml, flex build interface save xml, need help fixing pae, build expired video xml, need help fixing bugs mmorpg, need help fixing website

About the Employer:
( 36 reviews ) Lausanne, Switzerland

Project ID: #24588735

Awarded to:


Hello I have over 10 years of experience with C# and .NET Framework, including working with .NET Core I believe it's possible to solve in 1 hour of pure working time

$25 USD in 2 days
(817 Reviews)

3 freelancers are bidding on average $25 for this job


Hello, I have excellent knowledge on .net. I can fix error if it is fixable or i will let you know if its not possible. i have worked on slimier kind of project and successfully resolver error.

$30 USD in 2 days
(0 Reviews)

Hi, I recently faced with that bug. It's a known bug from Microsoft I can share the fixed one with you within minutes after.

$20 USD in 1 day
(0 Reviews)