Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1819,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly " ". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Azure Error

-
I faced this problem during development of application https://www.qfles.com

Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1819,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "PageOne.Dependency". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\home\site\repository\QflesAdmin\QflesAdmin.csproj]



This Error I was facing when I was deploying the Code to Azure from GitHub.

Problem - Your Solution referring the dlls by HintPath like this.

 <Reference Include="PageOne.PD">
      <HintPath>..\PageOne.PD\bin\Debug\PageOne.PD.dll</HintPath>
    </Reference>
    <Reference Include="PageOne.Services">
      <HintPath>..\PageOne.Services\bin\Debug\PageOne.Services.dll</HintPath>
    </Reference>


Solution - It should not refer the dlls by hint Path. It should be like this.

<ItemGroup>
    <ProjectReference Include="..\PageOne.Core\PageOne.Core.csproj">
      <Project>{8DA1814E-3E51-4A88-A5F7-80345A7A7841}</Project>
      <Name>PageOne.Core</Name>
    </ProjectReference>
    <ProjectReference Include="..\PageOne.PD\PageOne.PD.csproj">
      <Project>{197492FB-2E97-4DB1-BCDB-83B6EBED3CE3}</Project>
      <Name>PageOne.PD</Name>
    </ProjectReference>
    <ProjectReference Include="..\PageOne.Services\PageOne.Services.csproj">
      <Project>{BC08A2FB-F043-4CA9-8146-1647D7AECFFE}</Project>
      <Name>PageOne.Services</Name>
    </ProjectReference>
  </ItemGroup>

Visual Studio do all these things automatically, do not add dlls manually to references. Use Auto resolve .


Thanks

Comments

Post a Comment

Popular posts from this blog

Swagger for Azure functions: Undocumented TypeError: Failed to execute 'fetch' on 'Window': Request with GET/HEAD method cannot have body. Fixed.

-
Error -  Undocumented TypeError: Failed to execute 'fetch' on 'Window': Request with GET/HEAD method cannot have body.  Root Cause: I have my Azure functions Project for which I am configuring swagger documentation using Nuget Package " AzureExtensions.Swashbuckle ". When I am opening swagger url in browser and I try one get method then I face this error because 'Get' method has body that should not. My function code is:  public async Task<IActionResult> Test(             [HttpTrigger(AuthorizationLevel.Anonymous, Http.Methods.Get, Route = Version + "/test")] HttpRequest request,             ExecutionContext context, IBinder binder)         { } Solution: To remove the body from 'Get' method, I need to specify some ignore attribute to function parameters as below.  public async Task<IActionResult> GetTest(             [HttpTrigger(AuthorizationLevel.Anonymous, Http.Methods.Get, Route = Version + "/test")] HttpRequ
Read more

Fixed: The required column was not present in the results of a 'FromSql' operation in asp.net core EF core

-
In EF core you will face this error many times. Error:  The required column was not present in the results of a 'FromSql' operation. To fix this error either remove the column from mapped model or add UnMapped attribute.     public class Customer     {         /// <summary>         /// Gets or sets the ID for the customer         /// </summary>         [UnMapped]         public int CustomerName { get; set; }     } Some Essential Interview Questions
Read more

Severity Code Description Project File Line Suppression State Error Unable to resolve dependencies. 'Xamarin.Android.Support.Design 24.2.1' is not compatible with 'Xamarin.Forms 2.3.3.180 constraint: Xamarin.Android.Support.Design (= 23.3.0)'. 0

-
Xamarin Forms is not always compatible with the latest version of the Google Support libraries. Xamarin publishes them so Android developers (not using Forms) can utilize them if they need them, but Forms developers can continue to use the older, compatible versions.
Read more