Quantcast
Channel: MSBuild forum
Viewing all 2763 articles
Browse latest View live
↧

Find shortest distance between cities based on txt files

June 21, 2020, 4:43 pm
$
0
0

First two columns are ID's of the cities, and the third is distance between the cities.

How I can do this in microsoft visual studio?

Thank you.

↧
Search

Visual Studio 2019 Build issue

June 23, 2020, 1:45 pm
$
0
0

While building solution which has VB.NET standard projects and Core 3.1 projects, I am getting following error for all new core projects: XXXXXX.csproj.metaproj: The project file "XXXX.csproj" is not supported by MSBuild and cannot be built.

I have the following settings but still getting error message:
- Build definition - Process - Advanced - Agent Settings - Tags Filter ---  VS2019_4.8 is selected
- Tag Comparison Operator ---- MatchAtLeast

What should I do to build the solution for all projects ?

Thanks, AT


↧
↧

UsingTask always is looking for Net framework assembly not .Net Core one

June 24, 2020, 2:23 am
$
0
0

I have an imported .targets file which would run on every build of a .net core project and have a custom task in it.

.targets file have this:

    <LibFolderPart2 Condition="'$(MSBuildRuntimeType)' == 'Core'">netstandard2.1\Emailing.dll</LibFolderPart2>    
<LibFolderPart2 Condition="'$(MSBuildRuntimeType)' != 'Core'">net472\Emailing.dll</LibFolderPart2>
And
      <UsingTask TaskName="CustomlTask"       
      AssemblyFile="$(LibFolder)\$(LibFolderPart2)"      />

In the project definition I have:

      <PropertyGroup>        <TargetFrameworks>netcoreapp3.1;netstandard2.0;netstandard2.1;netcoreapp3.0;net472</TargetFrameworks>      </PropertyGroup>

When trying to use **Visual Studio build menu** it always goes for net472 though the project is a .net core project.

Can anyone explain why that happens and how can I force the build menu to build under .net core platform?

If I remove those first runtime conditions the `UsingTask` will never find the "Emailing.dll", cause it is trying to find a .net framework DLL.

I personally didn't want/need to implement net472 there, but seems I am forced to do so, if want to use the Visual studio build menu.

If needed can provide code in Github.
↧

Running MSBuild custom tasks and MSBuildRuntimeType difficulties

June 24, 2020, 2:23 am
$
0
0

Main strategy:
Here we have a library NugLibEnforceCore, which contains a custom MSBuild task and we will put it in a folder: The solution folder\.libs

First step is to build this library and put it in the proper folder.
Then we may try to build the `Consumer` project, which has build.targets and will try to run that custom tasks.

Projects and tasks are the bare minimum needed things for what expected and they don't have anything special.

The .targets file in the Consumer project:

      <PropertyGroup>        <LibFolder>$(SolutionDir).libs</LibFolder>        <!-- <LibFolderPart2 Condition="'$(MSBuildRuntimeType)' == 'Core'">netstandard2.1\NugLibEnforceCore.dll</LibFolderPart2> -->        <LibFolderPart2 Condition="'$(MSBuildRuntimeType)' == 'Core'">NugLibEnforceCore.dll</LibFolderPart2>        <LibFolderPart2 Condition="'$(MSBuildRuntimeType)' != 'Core'">net472\NugLibEnforceCore.dll</LibFolderPart2>      </PropertyGroup>          <UsingTask        TaskName="TestTask"        AssemblyFile="$(LibFolder)\$(LibFolderPart2)"      />          <Target Name="DoTheTask" AfterTargets="Build">        <Message Text="=== Trying TestTask ===" Importance="high" />        <TestTask />        <Message Text=" == TestTask is finished" Importance="high" />      </Target>

Here I share the issues and some difficulties I experienced and the approaches I tried related to the topic.

Tried to reproduce an issue which was irritating and happened time to time for me.
I was able to use custom tasks, but want to find the reasons and solve this issue forever.

1. Approach 1: ALL based on .net core - Build via Visual Studio Build Menu
get this error:

    Error    MSB4062        The "TestTask" task could not be loaded from the assembly     ...\MSBuild13 Enforce Core\.libs\net472\WeRTheBest.NugLibEnforceCore.dll.     Could not load file or assembly 'file:///...\MSBuild13 Enforce Core\.libs\net472\WeRTheBest.NugLibEnforceCore.dll' or one of its dependencies.     The system cannot find the file specified.     Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.    Consumer    ...\MSBuild13 Enforce Core\Consumer\build\build.targets    27    

---

**2. Approach 2:** ALL based on .net core - Build via dotnet msbuild command

    dotnet msbuild NugLibEnforceCore\NugLibEnforceCore.csproj

get this error:

Error:

      === Trying TestTask ===    ...\MSBuild13 Enforce Core\Consumer\build\build.targets(27,5):     error MSB4062: The "TestTask" task could not be loaded from the assembly     ...\MSBuild13 Enforce Core\Consumer\build\.libs\netstandard2.1\NugLibEnforceCore.dll.     Could not load file or assembly '...\MSBuild13 Enforce Core\Consumer\build\.libs\netstandard2.1\NugLibEnforceCore.dll'.     The system cannot find the path specified.     Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.     ...\MSBuild13 Enforce Core\Consumer\Consumer.csproj]


3. Approach 3: Multi-target (.Net Core & .Net Framework) - Build via Visual Studio Build Menu:
will cause other difficulties, which I may bring more details on the next steps here if needed or as we continue this discussion.

The code is also provided here:
https://github.com/KKacer/MSBuild13-Enforce-Core

Brief:

In the first approach when the project is based on ".net standard" why `MSBuildRuntimeType` is trying to take net472 library?!

In the second approach, it can't understand the same path used in the first approach and is looking for:

...\[Solution]\Consumer\build\.libs\netstandard2.1\NugLibEnforceCore.dll

instead of

    ...\[Solution]\.libs\netstandard2.1\NugLibEnforceCore.dll

In the last build I commented/removed "netstandard2.1" for easier builds, cause it is currently a single-target assembly.

We know that the files are in the proper location, you can also put the library manually and take a test if needed, the only thing that matters is be able to run the consumer project's tasks without any issues and worry.
I can share videos about it if needed.

↧

NuGet.Packaging.Core.PackagingException: Unable to find fallback package folder 'C:\Program Files (x86)\Progress\ToolboxNugetPackages'.

June 25, 2020, 6:06 pm
$
0
0

I'm just trying to build the stock .NET Core Console app in Visual Studio 2019 Enterprise; I'm using the latest version of VS.

ErrorMSB4018The "ResolvePackageAssets" task failed unexpectedly.
NuGet.Packaging.Core.PackagingException: Unable to find fallback package folder 'C:\Program Files (x86)\Progress\ToolboxNugetPackages'.
   at NuGet.Packaging.FallbackPackagePathResolver..ctor(String userPackageFolder, IEnumerable`1 fallbackPackageFolders)
   at Microsoft.NET.Build.Tasks.NuGetPackageResolver.CreateResolver(IEnumerable`1 packageFolders)
   at Microsoft.NET.Build.Tasks.NuGetPackageResolver.CreateResolver(LockFile lockFile)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheWriter..ctor(ResolvePackageAssets task)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader.CreateReaderFromDisk(ResolvePackageAssets task, Byte[] settingsHash)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader..ctor(ResolvePackageAssets task)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ReadItemGroups()
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ExecuteCore()
   at Microsoft.NET.Build.Tasks.TaskBase.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()ConsoleApp1C:\Program Files\dotnet\sdk\3.1.301\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets 234

Tavi Truman

↧
↧

DownloadFile task Credentials

June 29, 2020, 4:54 am
$
0
0
While using the DownloadFile task, is there way to specify credentials, at least with a key instead of password? DownloadFile task allows download of only public / anonymous URLs or authenticated URLs also? How to download files without anonymous access? Please help.

Ven

↧

Error MSB4062 on RGiesecke.DllExport.MSBuild.DllExportAppDomainIsolatedTask

July 1, 2020, 10:54 am
$
0
0

Hi all,

I've succesfully imported the package UnmanagedExports ver 1.27 via the NuGet package manager, in order to obtain a dll to be invoked from a JNA app from my already exist C# project.

My method has been beautifully 'annotated' with

[DllExport("listReaders", CallingConvention = CallingConvention.Cdecl)]
public static bool ListReaders(out string[] sReaderName, out int iReadersFound) {...}

But when I try to compile what I get is:

The "RGiesecke.DllExport.MSBuild.DllExportAppDomainIsolatedTask" task could not be loaded from the assembly ${myprojectdir}\packages\UnmanagedExports.1.2.7\tools\RGiesecke.DllExport.MSBuild.dll.
Could not load file or assembly 'Microsoft.Build.Utilities, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
The system cannot find the file specified. Confirm that the declaration is correct, that the assembly and all its dependencies are available,
and that the task contains a public class that implements Microsoft.Build.Framework.ITask

The IDE is a Microsoft Visual Studio Community 2019 Versione 16.6.0

Any help appreciated.

PS: here's a fragment of my .csproj file

<ItemGroup><Reference Include="RGiesecke.DllExport.Metadata, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8f52d83c1a22df51, processorArchitecture=MSIL"><HintPath>packages\UnmanagedExports.1.2.7\lib\net\RGiesecke.DllExport.Metadata.dll</HintPath><Private>False</Private></Reference><Reference Include="System" /><Reference Include="System.Core"><RequiredTargetFramework>3.5</RequiredTargetFramework></Reference><Reference Include="System.Windows.Forms" /><Reference Include="System.Xml.Linq"><RequiredTargetFramework>3.5</RequiredTargetFramework></Reference><Reference Include="System.Data.DataSetExtensions"><RequiredTargetFramework>3.5</RequiredTargetFramework></Reference><Reference Include="System.Data" /><Reference Include="System.Xml" /></ItemGroup>

what it seems strange is the 3.5 version in the RequiredTargetFramework tag (I think a legacy settings because the project has been created a long time ago.

↧

WPF Problem I need Help about this

July 7, 2020, 5:39 am
$
0
0
SeverityCodeDescriptionProjectPathFileLineSuppression State
ErrorThe "ResourcesGenerator" task failed unexpectedly.
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)
   at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, String fullPath, Boolean checkForDuplicates, Boolean needFullPath)
   at MS.Internal.Tasks.TaskHelper.CreateFullFilePath(String thePath, String rootPath)
   at Microsoft.Build.Tasks.Windows.ResourcesGenerator.ValidResourceFiles(ITaskItem[] inputFiles)
   at Microsoft.Build.Tasks.Windows.ResourcesGenerator.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()Otsutsuki
↧
Search

MSHTML Big Error

January 24, 2019, 2:32 pm
$
0
0

SeverityCodeDescriptionProjectFileLineSuppression State
WarningCannot find wrapper assembly for type library "MSHTML". Verify that (1) the COM component is registered correctly and (2) your target platform is the same as the bitness of the COM component. For example, if the COM component is 32-bit, your target platform must not be 64-bit.Zombsroyale BR <g class="gr_ gr_8 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="8" id="8">Unoffical</g> App

It's a warning, it looks like <g class="gr_ gr_126 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="126" id="126">that :</g>http://prntscr.com/mbs9i4

It always happens when I add the MSHTML library <g class="gr_ gr_164 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="164" id="164">refrence</g>.

↧
↧

SignFile task to sign multiple dlls

July 7, 2020, 9:36 am
↧

Using SignFile on Multiple Files/Paths at once?

December 19, 2006, 3:33 pm
$
0
0
I was just wondering if it's at all possible to use the SignFile MSBuild Task to sign multiple files at once? Can you simply specify a path or location and have all files in that location signed? Any help is greatly appreciated, thanks again!
↧

SignFile task with Verbose output

July 7, 2020, 10:14 am
$
0
0
Is it possible to have SignFile task to provide verbose output? For example, when it is signing multiple files, can it provide a verbose output for each file?

Ven

↧

Where is MSBuild finding .metaproj

May 7, 2015, 4:52 pm
$
0
0

I have a solution that I can build from Visual Studio. Configuration manager is set to build "QL Release | Win32".   I saved all after building in Visual Studio 2013.

I tried a command line build:

"C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe" /nologo /p:Configuration="QL Release" /verbosity:detailed /t:Rebuild /fileloggerparameters:LogFile="d:\myProduct\windows_build_logs\QL_out.txt"  "d:\myProduct\mySolution\QL.sln"

The logfile references a non-existent ".metaproj" file:

Build started 5/7/2015 5:31:04 PM.
Project "d:\myProduct\mySolution\QL.sln" on node 1 (Rebuild target(s)).
Building with tools version "2.0".
Target "ValidateSolutionConfiguration" in file "d:\myProduct\mySolution\QL.sln.metaproj" from project "d:\myProduct\mySolution\QL.sln" (entry point):
Using "Error" task from assembly "Microsoft.Build.Tasks.v12.0, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "Error"
d:\myProduct\mySolution\QL.sln.metaproj : error MSB4126: The specified solution configuration "QL Release|X64" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [d:\myProduct\mySolution\QL.sln]
Done executing task "Error" -- FAILED.
Done building target "ValidateSolutionConfiguration" in project QL.sln" -- FAILED.
Done Building Project "d:\myProduct\mySolution\QL.sln" (Rebuild target(s)) -- FAILED.


Build FAILED.

"d:\myProduct\mySolution\QL.sln" (Rebuild target) (1) ->
(ValidateSolutionConfiguration target) -> 
  d:\myProduct\mySolution\QL.sln.metaproj : error MSB4126: The specified solution configuration "QL Release|X64" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [d:\myProduct\mySolution\QL.sln]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.06

I don't know where it is getting the ".metaproj" file as there isn't one.  I've done a clean, even removed the QL.sdf and QL.v12.suo files, but the command line build still wants to build a non-existent configuration.  That configuration most likely came from some experimental work which has since been removed. The solution contains 10 projects.  None of the project or solution files reference x64 so I can't tell where MSBUILD is getting this information.


↧
↧

SignFile task error in Build machine

July 8, 2020, 10:58 am
$
0
0

I have a Windows 10 VM with VS 2019 installed. MSBuild version is 16.6. I am using the following from msbuild command in Developer Command Prompt and it works fine.

<SignFile CertificateThumbprint="$(CertThumbprint)" SigningTarget="%(DLLFiles.FullPath)" TargetFrameworkVersion="v4.5" />

I have a build machine which is Windows Server 2019 Standard. It has Visual Studio 2019 Build Tools installed (but no VS) and hence MSBuild version is 16.5. The above SignFile task throws an error in the build machine 

"An error occurred while signing: SignTool.exe was not found at path <Location_of_Project_File>\signtool.exe"

Even in my Windows 10 machine, I don't have signtool.exe in the project file location. So, I am not sure why is this error occurring? Please help.

Ven

↧

Visual Studio 2019 C++/CLI Building without MSBuild

July 8, 2020, 11:56 am
$
0
0
Hello, I am trying to port a C++/CLI project to target .NET Core without MSBuild and I keep getting the following errors:

Error 1:
c:\dotnet\sdk\3.1.105\microsoft\microsoft.net.build.extensions\net461\lib\system.runtime.dll: fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'msc1.cpp', line 1528)
 To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
 Help menu, or open the Technical Support help file for more information
Internal Compiler Error in C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.24.28314\bin\HostX64\x64\cl.exe.  You will be prompted to send an error report to Microsoft later.
INTERNAL COMPILER ERROR in 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.24.28314\bin\HostX64\x64\cl.exe'

Error 2:
c:\dotnet\sdk\3.1.105\microsoft\microsoft.net.build.extensions\net461\lib\system.runtime.dll: fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'msc1.cpp', line 1528)
 To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
"(I believe this is a parse error, found something saying this in microsoft support pages)"
Help menu, or open the Technical Support help file for more information

When I researched these errors I found that most people rebuilt the project and it went away,
as I am not using MSBuild this is not an option.  To build I am using a Makefile with /clr:netcore,
this builds if I change the Makefile to target .NET Framework.

I have tried the following:
Deleting the old dll and rebuilding
Including mscrolib, and system.runtime using /FU
Including the directories using /AI
Linking in the ijwhost.lib using LINKLIBS, CPPFLAGS, and LIBDEPS
Creating a runtime config file in the following format:

{
  "runtimeOptions": {
    "tfm": "netcoreapp3.1",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "3.1.0"
    }
  }
}

Moving the runtime config file to the output directory
Removing Optimiazations
Adding ijwhost.dll to the output directory

I am using vs2019 (version 16.4.10) with the following attributes:
Windows 10 SDK (10.0.17134.0)
MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.24)
C++/CLI support for v142 build tools (14.24)
And the following .NET Core runtimes:

.NET Core 2.1 LTS Runtime

.NET Core 2.2 Runtime (EOL)

.NET Core 3.0 Runtime

.NET Core 3.1 SDK
↧
Search

Web Deploy ExcludeFromPackageFolders & ExcludeFoldersFromDeployment both not working for App_Code folder

July 8, 2020, 3:13 pm
$
0
0
Hi Build & Deploy Folk,

My Web Deploy from VS 2019 on my Windows 10 dev machine  to IIS on a separate Windows Server machine completes correctly but when it opens the home page of that newly deployed site I get the following error in the browser:

The directory '/App_Code/' is not allowed because the application is precompiled.

Because of this error, I am trying to EXCLUDE '/App_Code/' from my package and/or from my deployment


On docs.microsoft.com there appears to be two conflicting ways to do this:

(1) At https://docs.microsoft.com/en-us/previous-versions/aspnet/ee942158(v=vs.110)  it says to do the following in the .pubxml or the .wpp.targets file

<PropertyGroup">
  <ExcludeFilesFromDeployment>
    File1.aspx;File2.aspx
  </ExcludeFilesFromDeployment>
  <ExcludeFoldersFromDeployment>
    Folder1;Folder2
  </ExcludeFoldersFromDeployment>
</PropertyGroup> 

(2) while at https://docs.microsoft.com/en-us/aspnet/web-forms/overview/deployment/advanced-enterprise-web-deployment/excluding-files-and-folders-from-deployment it says to do the following in the  .wpp.targets file (and I assume this should also work in the appropriate  .pubxml file):

<Project ToolsVersion="4.0" 
         xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <ItemGroup>   
    <ExcludeFromPackageFolders Include="[semi-colon-separated folder list]">
      <FromTarget>[arbitrary metadata value]</FromTarget>
    </ExcludeFromPackageFolders>
    <ExcludeFromPackageFiles Include="[semi-colon-separated file list]">
      <FromTarget>[arbitrary metadata value]</FromTarget>
    </ExcludeFromPackageFiles>
  </ItemGroup>
</Project>

Are these both correct ?  If so which is preferred and why ?

In any case I have tried both in an attempt to NOT deploy my "App_Code" folder and neither appear to work.

Any assistance understanding why the App_Code folder is not being Excluded from the Package or from the Deployment, and how to fix this issue, would be appreciated.

Thanks all

Terry Clancy

ClanceZ

Terry Clancy


↧

Why there is a error while executing program in VS 2019?

July 11, 2020, 9:42 am
$
0
0

Hi,

I am trying to write a simple C++ code script on visual studio and it keeps getting detected as a Trojan:Win32/Ludicrouz.Z threat. Visual studio keeps timing out with the error that "operation did not complete successfully because the file contains a virus or potentially unwanted". I have reinstalled and installed VS2019 multiple times, and C++ works fine.  I dont know what the issue is. 

↧
↧

invalid parameter. path contains illegal character.

July 12, 2020, 8:40 pm
$
0
0

hi  friend ,  vs has an error : 

 C:\Program Files (x86)\Microsoft VisualStudio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): error MSB3095: invalid parameter. path contains  illegal character.

when i build my project by vs 2017

help me please

↧

Nuget restore task taking an excessive length of time

July 13, 2020, 7:33 am
$
0
0

Hi

We have DevOps pipelines being run on self-hosted build servers, building a large solution (~50 projects, currently a mix of full framework and NetStandard) with a lot of nugets being referenced. Unfortunately the codebase is far too large to be pulled onto the standard azure build servers.

We use the nuget restore step (v4.9.1) against the standard nuget feed & a couple of secured customer devops feeds but the restore time has gone from ~2 mins to more than 10 minute. At the outset of this the nuget restore was failing completely, allegedly due to authentication timeout. We have managed to get it working again, but taking these much longer times using the following settings:


  1.  steps:
  3. - task:NuGetCommand@2
  5.    displayName:'NuGet restore'
  7.    inputs:
  9.      restoreSolution: src/DesktopComponents.sln
  11.      feedsToUse: config
  13.      nugetConfigPath: nuget.config
  15.      disableParallelProcessing:true
  17.      restoreDirectory:.packages

Any assistance that anyone could offer would be much appreciated. If there are any logs/settings that would be useful please let me know

Thanks in advance

Mark Middlemist

↧

Error_MSB4018_The "ResolvePackageAssets" task failed unexpectedly.

May 17, 2020, 2:26 pm
$
0
0
SeverityCodeDescriptionProjectFileLineSuppression State
ErrorMSB4018 The "ResolvePackageAssets" task failed unexpectedly.
NuGet.Packaging.Core.PackagingException: Unable to find fallback package folder 'C:\Microsoft\Xamarin\NuGet\'.
   at NuGet.Packaging.FallbackPackagePathResolver..ctor(String userPackageFolder, IEnumerable`1 fallbackPackageFolders)
   at Microsoft.NET.Build.Tasks.NuGetPackageResolver.CreateResolver(IEnumerable`1 packageFolders)
   at Microsoft.NET.Build.Tasks.NuGetPackageResolver.CreateResolver(LockFile lockFile)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheWriter..ctor(ResolvePackageAssets task)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader.CreateReaderFromDisk(ResolvePackageAssets task, Byte[] settingsHash)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader..ctor(ResolvePackageAssets task)
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ReadItemGroups()
   at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ExecuteCore()
   at Microsoft.NET.Build.Tasks.TaskBase.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()ConsoleApp1C:\Program Files\dotnet\sdk\3.1.201\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets234
↧
Viewing all 2763 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>