.NET Core - build project specifying ReferencePath

Error processing SSI file

Answers

  1. Kyro

    • 2016/1/7

    Problem is coused by Microsoft.NET.Sdk.props: AssemblySearchPaths has no ReferencePath. Fixed by adding to csproj:

    <PropertyGroup>
        <AssemblySearchPaths>
            $(AssemblySearchPaths);
            $(ReferencePath);
        </AssemblySearchPaths>
    </PropertyGroup>
    
  2. Joel

    • 2016/8/5

    Problem is coused by Microsoft.NET.Sdk.props: AssemblySearchPaths has no ReferencePath. Fixed by adding to csproj:

  3. Tristian

    • 2020/5/3

    You can still build .net CORE/Standard projects in solution using MSBUILD. It is seem to be a bug which I reported to Microsoft that (and this is not about core/standard but rather new project file format) referencePath is ignored with new project file format.

  4. Nixon

    • 2018/2/3

    This item applies to projects using the SDK for .NET 5 (and .NET Core) and later versions. InternalsVisibleTo. Specifies assemblies to be 

  5. Krasniqi

    • 2017/7/1
    1. You can still build .net CORE/Standard projects in solution using MSBUILD.
    2. It is seem to be a bug which I reported to Microsoft that (and this is not about core/standard but rather new project file format) referencePath is ignored with new project file format.
    3. Supply add /t:restore to msbuild command along with build target, so it will restore and build at same time.
    4. The work-around for your CI/Build server situation is to create a special solution configuration, and add similar to following into your project file
    <Choose>  
      <When Condition="'$(Configuration)|$(Platform)'=='YourSpecialConfiguration|x64'"><!-- attention here -->
        <ItemGroup>
          <Reference Include="your.dllname">
            <HintPath>yourSpecialPath\your.dllname.dll</HintPath><!-- attention here -->
            <Private>true</Private>
          </Reference>
          <!-- more references here -->
      </When>
      <Otherwise>
        <ItemGroup>
          <Reference Include="your.dllname">
            <HintPath>yourRegularPath\your.dllname.dll</HintPath><!-- attention here -->
            <Private>true</Private>
          </Reference>
          <!-- AND more references here -->
      </Otherwise>
    </Choose>  
    

    This will allow you to just change configuration name in CI/Build and will do the job.

  6. Adonis

    • 2019/12/22

    You can specify command line arguments to csc.exe for .NET Framework projects. Compiled ASP.NET pages : .NET Framework projects use a section of the web.config file for compiling pages. For the new build system, and ASP.NET Core projects, options are taken from the project file.

  7. Landry

    • 2019/4/10

    The PackageReference and ProjectReference tags allow you to specify a NuGet package and project dependencies respectively. The former lets you specify the ID 

  8. Zion

    • 2019/2/25

    The following table lists frequently used properties that are defined in the Visual Studio project files or included in .targets files that MSBuild provides. Project files in Visual Studio ( .csproj, .vbproj, .vcxproj, and others) contain MSBuild XML code that runs when you build a project by using the IDE. Projects typically import one or more

  9. Francisco

    • 2017/1/7

    But the "dotnet build" has no similar argument.

    Why are you saying that?

    The dotnet cli still support "property injection" with -p instead of /p. Link (Search for "-p")

    For your question, the build command will look like this command:

    dotnet build -p:ReferencePath=xxx

  10. Emiliano

    • 2016/3/19

    5 I ran into an error while building an existing WPF project: The item "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild 

  11. Wyatt

    • 2018/8/22

    I’m using VS 2017. The project would not build on my computer but it would on a co-workers computer. So I used DiffMerge to compare the two folders and there was ONE difference in the same file you mention (“Microsoft.Common.CurrentVersion.targets”). So I made the change on my computer and re-opened the project and it compiled without the

  12. Charles

    • 2019/12/10

    They can also be edited in Visual Studio using the PostSharp project property NET Core process requires it's build-time dependency NuGet packages to be 

  13. Graham

    • 2017/1/24

    I am building a simple ToDo List App with API using ASP.NET Core and I want authentication to use JWT. The official docs suggest following three options for authenticating users accessing web API: Azure Active Directory. Azure Active Directory B2C. IdentityServer4. But I don't want to use third party providers.

  14. Joel

    • 2016/5/29

    impossible to load or build your projects from the command-line or the IDE. NETCore. Imports for .NETFramework is a superset of that for .NETCore-->.

  15. Fisher

    • 2018/5/8

    Creating a project in VS can be done in many different ways, Files (x86)\Kvaser\Canlib\dotnet\win32\fw40\</ReferencePath> 

  16. Ryan

    • 2015/10/12

    All projects and all configurations in them are initially set to output into ApiBuild folder, and to take references from same ApiBuild folder. On build server 

Comments are closed.

More Posts