build server not finding nuget package

May 31, 2017, 10:50 am

≫ Next: advapi32.dll load error in UWP Environment

≪ Previous: The command mc:VCEnd exited with code 1 (Microsoft.CppCommon.targets)

We are setting up a CI server for our UWP app and the build fails when using a system accout.

almost identical to: https://stackoverflow.com/questions/43276107/jenkins-not-finding-a-nuget-package

I'm setting a Jenkins CI server. I got the first step to run properly:

nuget restore -NonInteractive  -ConfigFile Nuget.config -Verbosity Detailed -NoCache

That works properly, but when I want to compile the app with:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\MSBuild.exe

and ${WorkSpace}\src\Weather.App.csproj It throws this error:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\NuGet\15.0\Microsoft.NuGet.targets(178,5): error : The package HockeySDK.Core with version 4.1.6 could not be found in C:\WINDOWS\system32\config\systemprofile\.nuget\packages\. Run a NuGet package restore to download the package. [C:\Program Files (x86)\Jenkins\workspace\MyApp\Weather\Weather.App.csproj]

The weird thing is that it the Hockey package clearly exists in the path:

a flishhorse fellow

↧

advapi32.dll load error in UWP Environment

September 17, 2019, 7:14 pm

≫ Next: MSBuild rerunning targets multiple times

≪ Previous: build server not finding nuget package

Hi, I am developing a program from unity and visual studio to read and write in an excel using the openxml library. I was able to run the program in Unity however when I build it to UWP environment, there are no build errors but during runtime I encounter a “DLLNotFoundException:Unable to load DLL 'advapi32.dll” error message in the console window. I tried looking at google for possible solutions but I cannot find anything. I cant even trace where I get this error. Do you have any advice for this matter?
Tools:
unity 2018.3.10 (Client Side)
Visual Studio 2017 (DLL Side) (latest 2017 update)
documentformat.openxml.dll (library) version 2.5.1

I tried generating this using unity 2019 version and latest visual studio version 2019. However same problem is shown.

↧

MSBuild rerunning targets multiple times

June 15, 2018, 9:04 am

≫ Next: Does MSBuild 14.0 supports Visual Studio 2017 version of MSBuild 15.0

≪ Previous: advapi32.dll load error in UWP Environment

I'm working on moving our custom build logic from VSTS build tasks into a directory.build.targets file. In the test project I have a single project inside a solution. Without my .targets file the project is built once. But when I add my target the project seems to get built 3 times. Only my custom target elements are running again so it seems like I'm missing something. I suspect it has something to do with the before, depends and after target properties but I don't see what.

directory.build.targets file

<?xml version="1.0" encoding="utf-8"?><Project ToolsVersion="15.0" InitialTargets="StartTarget" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"><!-- Starting target --><Target Name="StartTarget" BeforeTargets="DispatchToInnerBuilds"><Message Text="Start Target" /></Target><Target Name="_ChildTarget1" AfterTargets="StartTarget"><Message Text="Child Target 1" /></Target>  <Target Name="_ChildTarget2" AfterTargets="_ChildTarget1"><Message Text="Child Target 2" /></Target></Project>

Output when run on a solution containing a single project. The compilation output was removed to keep the length down.

Microsoft (R) Build Engine version 15.8.60.28450 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 6/15/2018 11:00:13 AM.
Project "C:\projects\Fsmb\multiplebuilds\Test.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Debug|Any CPU".
Project "C:\projects\Fsmb\multiplebuilds\Test.sln" (1) is building "C:\projects\Fsmb\multiplebuilds\TestCSharp\TestCSha
rp.csproj" (2) on node 1 (default targets).
StartTarget:
  Start Target
_ChildTarget1:
  Child Target 1
_ChildTarget2:
  Child Target 2
PrepareForBuild:
  Creating directory "bin\Debug\netstandard2.0\".
  Creating directory "obj\Debug\netstandard2.0\".
GenerateTargetFrameworkMonikerAttribute:
Skipping target "GenerateTargetFrameworkMonikerAttribute" because all output files are up-to-date with respect to the i
nput files.
CoreCompile:
   ...
    Using shared compilation with compiler from directory: C:\Dev\VS2017_Preview\MSBuild\15.0\bin\Roslyn
CopyFilesToOutputDirectory:
  Copying file from "obj\Debug\netstandard2.0\TestCSharp.dll" to "bin\Debug\netstandard2.0\TestCSharp.dll".
  TestCSharp -> C:\projects\Fsmb\multiplebuilds\TestCSharp\bin\Debug\netstandard2.0\TestCSharp.dll
  Copying file from "obj\Debug\netstandard2.0\TestCSharp.pdb" to "bin\Debug\netstandard2.0\TestCSharp.pdb".
Project "C:\projects\Fsmb\multiplebuilds\TestCSharp\TestCSharp.csproj" (2) is building "C:\projects\Fsmb\multiplebuilds
\TestCSharp\TestCSharp.csproj" (2:2) on node 1 (_GetBuildOutputFilesWithTfm target(s)).
StartTarget:
  Start Target
_ChildTarget1:
  Child Target 1
_ChildTarget2:
  Child Target 2
Done Building Project "C:\projects\Fsmb\multiplebuilds\TestCSharp\TestCSharp.csproj" (_GetBuildOutputFilesWithTfm targe
t(s)).

Project "C:\projects\Fsmb\multiplebuilds\TestCSharp\TestCSharp.csproj" (2) is building "C:\projects\Fsmb\multiplebuilds
\TestCSharp\TestCSharp.csproj" (2:5) on node 1 (_GetFrameworkAssemblyReferences target(s)).
StartTarget:
  Start Target
_ChildTarget1:
  Child Target 1
_ChildTarget2:
  Child Target 2
Done Building Project "C:\projects\Fsmb\multiplebuilds\TestCSharp\TestCSharp.csproj" (_GetFrameworkAssemblyReferences t
arget(s)).

GenerateNuspec:
  Successfully created package 'C:\projects\Fsmb\multiplebuilds\TestCSharp\bin\Debug\TestCSharp.1.0.0.nupkg'.
Done Building Project "C:\projects\Fsmb\multiplebuilds\TestCSharp\TestCSharp.csproj" (default targets).

Done Building Project "C:\projects\Fsmb\multiplebuilds\Test.sln" (default targets).


Build succeeded.

The project is an SDK format project targeting .NET Standard 2.0. MSBuild is version 15.8.60.28450 from VS 2017 Preview 15.8 2.0

Michael Taylor http://www.michaeltaylorp3.net

↧

Does MSBuild 14.0 supports Visual Studio 2017 version of MSBuild 15.0

September 18, 2019, 11:44 am

≫ Next: Getting a .NetFramework error on Build Server but works fine on locally when built

≪ Previous: MSBuild rerunning targets multiple times

Hi,

Does MSBuild 14.0 supports Visual Studio 2017 Solution version of MSBuild 15.0, Is it compatible with MSBuild 14.0

Project file contains ToolsVersion="15.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild

Please let me know any help would be appreciated.

Thanks,

info2m

↧

Getting a .NetFramework error on Build Server but works fine on locally when built

September 18, 2019, 11:49 am

≫ Next: Namespace issue when building a automated build in Visual Studio

≪ Previous: Does MSBuild 14.0 supports Visual Studio 2017 version of MSBuild 15.0

Hi,

Getting a .NetFramework error on Build Server but works fine on locally when built, "But .NET Framework version 4.6.2 exists on the Build Server".

Error MSB3644 The reference assemblies for framework ".NETFramework,Version=v4.6.2" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.

Please help to resolve this issue.

Thanks,

info2m

↧

Namespace issue when building a automated build in Visual Studio

September 18, 2019, 11:56 am

≫ Next: Offline Installer for MSBuild Tools 2019

≪ Previous: Getting a .NetFramework error on Build Server but works fine on locally when built

Hi,

But this namespace does exists in .CSPROJ file and it builds locally fine.

Error CS0234: The type or namespace name 'xxxx' does not exist in the names pace 'yyyyy' (are you missing an assembly reference?)

Please help to resolve the issue.

Thanks,

info2m

↧

Offline Installer for MSBuild Tools 2019

September 19, 2019, 4:38 am

≫ Next: TFS I am facing bug - in Backlog for some user stories the iteration path changed to default iteration without any action from my side

≪ Previous: Namespace issue when building a automated build in Visual Studio

Hello,

I'm looking for an offline installer for the MSBuild Tools 2019.
Earlier we used the offline installer for MSBuild Tools 2015, but it seems that for 2019 it isn't available for downloading anymore.
Since we have computers, were we do not have connection to internet to use the online installer, we would need an offline setup.exe.

Do you have any advice how I could solve this problem?

Thanks in advance,

↧

TFS I am facing bug - in Backlog for some user stories the iteration path changed to default iteration without any action from my side

September 22, 2019, 12:21 am

≫ Next: This project builds successfully and runs well. but....

≪ Previous: Offline Installer for MSBuild Tools 2019

I skim through backlog, and navigate through sprints open stories (view only)

After I complete the review for sprint user stories, I found that the system change iteration path for some stories (even these stories I did't access) to backlog default iteration path

would you please advise with solution or workaround for this issue

Many thanks ..

↧

This project builds successfully and runs well. but....

September 23, 2019, 2:23 am

≫ Next: My project builds successfully and runs well. but....

≪ Previous: TFS I am facing bug - in Backlog for some user stories the iteration path changed to default iteration without any action from my side

It consists of two projects in one solution.

One outputs as a dll and one outputs to an executable.

This project builds successfully and runs well.

But I get error CS0103 in the error list.

My Visual Studio Version is 2019. The latest version.

And....

I don't know the cause, but I found a solution.

In Solution Explorer-> References-> "Referenced Projects"(project name output as dll)-> Right-click-> Properties-> Embed Interop Types,

change the value to False-> true-> false.

Why? Is it VSbug?

I guess it is related to the .vs folder. Because

Doing the following will not generate an error :
1. Change the Value Interop type to False-> true-> False.
2. Copy the .vs folder to another location.
3. Delete the .vs, bin and obj folders, then overwrite the previously copied .vs folder in the solution folder.

↧

My project builds successfully and runs well. but....

September 23, 2019, 2:23 am

≫ Next: Will be Managed Binary Analysis removed from VS E 2017?

≪ Previous: This project builds successfully and runs well. but....

It consists of two projects in one solution.

One outputs as a dll and one outputs to an exefile.

My project builds successfully and runs well.

But I get error CS0103 in the error list.

My Visual Studio Version is 2019. The latest version.

And....

I don't know the cause, but I found a solution.

In Solution Explorer-> References-> "Referenced Projects"(project name output as dll)-> Right-click-> Properties-> Embed Interop Types,

change the value to False-> true-> false.

Why? Is it VSbug?

I guess it is related to the .vs folder. Because

↧

Will be Managed Binary Analysis removed from VS E 2017?

September 26, 2019, 1:32 am

≫ Next: How does a condition exists evaluate for a pre-processor definition in vcxproj file.

≪ Previous: My project builds successfully and runs well. but....

Hi,

I wonder if Managed Binary Analysis (FxCop static analysis) will be removed fromVisual Studio Enterprise 2017 in favor of FxCop Analyzers?

For instance I found that rule CA2202: Do not dispose objects multiple timesis not ported toFxCop Analyzers.

Is there some list of not ported rules?
Is there list of not ported but will-be ported rules?
Will there be a package for Managed Binary Analysis?

↧

How does a condition exists evaluate for a pre-processor definition in vcxproj file.

September 26, 2019, 6:17 pm

≫ Next: Strange build agent error - exceeded time

≪ Previous: Will be Managed Binary Analysis removed from VS E 2017?

I am trying to run MSBuild with following command

msbuild socwatch.sln /t:rebuild /p:Configuration=Release /p:platform=x64

and another build using the command

msbuild socwatch.sln /t:rebuild /p:Configuration=Release /p:platform=x64 /p:SOC='IAP'

My .vcxproj file has this setting

<PreprocessorDefinitions Condition= "!exists('$(SOC)')">%(PreprocessorDefinitions);IAP</PreprocessorDefinitions>
<PreprocessorDefinitions Condition="'$(SOC)'=='IAP'">%(PreprocessorDefinitions);IAP</PreprocessorDefinitions>

The purpose of the first PreprocesseorDefinition is to declare a pre-processor directive called IAP if SOC is not mentioned as a command line parameter for MSBuild. But the first line never works. How to implement this ?

I got Embedded in the Embedded. **************************************** This posting is provided "AS IS" with no warranties.

↧

Strange build agent error - exceeded time

September 27, 2019, 7:26 am

≫ Next: SmartStore.NET Building Errors

≪ Previous: How does a condition exists evaluate for a pre-processor definition in vcxproj file.

When a build starts, it fails immediately with the following error:

The job running on agent xxx has exceeded the maximum execution time of 01:00:00.

This began to happen in the last days.

Every build definition is set to 60 minutes. However, the builds last only a few seconds.

Do you have any idea??

Thank you so much!

Regards!

↧

SmartStore.NET Building Errors

September 29, 2019, 8:35 pm

≫ Next: MSB4062 The ProcessFrameworkReferences task could not be loaded from the C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll assembly.

≪ Previous: Strange build agent error - exceeded time

What Those Errors Mean

Build FAILED.

"Desktop\SmartStoreNET-4.x\SmartStoreNET.proj" (Deploy tar
get) (1) ->
"Desktop\SmartStoreNET-4.x\src\SmartStoreNET.sln" (Build t
arget) (2:2) ->
"Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Servic
es\SmartStore.Services.csproj" (default target) (7:38) ->
"Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\S
martStore.Data.csproj" (default target) (8:25) ->
(CoreCompile target) ->
Setup\MigrateDatabaseInitializer.cs(105,20): error CS8121: An expressi
on of type TConfig cannot be handled by a pattern of type MigrationsConf
iguration. [Desktop\SmartStoreNET-4.x\src\Libraries\SmartS
tore.Data\SmartStore.Data.csproj]
Setup\MigrateDatabaseInitializer.cs(105,69): error CS8121: An expressi
on of type TContext cannot be handled by a pattern of type SmartObjectCo
ntext. [Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore
.Data\SmartStore.Data.csproj]
Setup\MigrateDatabaseInitializer.cs(109,7): error CS0165: Use of unass
igned local variable 'coreConfig' [Desktop\SmartStoreNET-4
.x\src\Libraries\SmartStore.Data\SmartStore.Data.csproj]
Setup\MigrateDatabaseInitializer.cs(109,31): error CS0165: Use of unas
signed local variable 'ctx' [Desktop\SmartStoreNET-4.x\src
\Libraries\SmartStore.Data\SmartStore.Data.csproj]
Utilities\DataMigrator.cs(917,67): error CS0246: The type or namespace
name 'T' could not be found (are you missing a using directive or an as
sembly reference?) [Desktop\SmartStoreNET-4.x\src\Librarie
s\SmartStore.Data\SmartStore.Data.csproj]
Utilities\DataMigrator.cs(917,44): error CS1750: A value of type 'T' c
annot be used as a default parameter because there are no standard conve
rsions to type 'T' [Desktop\SmartStoreNET-4.x\src\Librarie
s\SmartStore.Data\SmartStore.Data.csproj]
Setup\SeedData\InvariantSeedData.cs(13790,10): error CS8121: An expres
sion of type T cannot be handled by a pattern of type Category. [C:\User
s\Abdo\Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\SmartStor
e.Data.csproj]
Setup\SeedData\InvariantSeedData.cs(13793,10): error CS8121: An expres
sion of type T cannot be handled by a pattern of type Manufacturer. [C:\
Users\Abdo\Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\Smart
Store.Data.csproj]
Setup\SeedData\InvariantSeedData.cs(13796,10): error CS8121: An expres
sion of type T cannot be handled by a pattern of type Product. [C:\Users
\Abdo\Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\SmartStore
.Data.csproj]
Setup\SeedData\InvariantSeedData.cs(13799,10): error CS8121: An expres
sion of type T cannot be handled by a pattern of type BlogPost. [C:\User
s\Abdo\Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\SmartStor
e.Data.csproj]
Setup\SeedData\InvariantSeedData.cs(13803,10): error CS8121: An expres
sion of type T cannot be handled by a pattern of type NewsItem. [C:\User
s\Abdo\Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\SmartStor
e.Data.csproj]
Setup\SeedData\InvariantSeedData.cs(13807,10): error CS8121: An expres
sion of type T cannot be handled by a pattern of type Topic. [C:\Users\A
bdo\Desktop\SmartStoreNET-4.x\src\Libraries\SmartStore.Data\SmartStore.D
ata.csproj]

↧

MSB4062 The ProcessFrameworkReferences task could not be loaded from the C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll assembly.

September 30, 2019, 1:58 am

≫ Next: MSBuildProcess keeps reappearing

≪ Previous: SmartStore.NET Building Errors

Hello, everyone,
after the update (VS 2019, ver. 16.3.1) I have an error message in a BLAZOR project and I can compile even the smallest project!

Error is:
"Severity Code Description Project File Line Suppress State Suppress State Suppress State
Error MSB4062 The ProcessFrameworkReferences task could not be loaded from the C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll assembly. Make sure the <UsingTask> declaration is correct, the assembly and all associated dependencies are available, and the task contains a public class implementing Microsoft.Build.Framework.ITask. ohaPortal C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets 59."

My VS information:

Visual Studio Professional 2019
Version 16.3.1
VisualStudio.16.Release/16.3.1+29324.140
Microsoft .NET Framework
Version 4.8.03752

Installierte Version: Professional

Allgemeine Azure-Tools 1.10
Bietet allgemeine Dienste für die Verwendung durch Azure Mobile Services und Microsoft Azure-Tools.

Application Insights-Tools für Visual Studio-Paket 9.1.00913.1
Application Insights-Tools für Visual Studio

ASP.NET and Web Tools 2019 16.3.283.64955
ASP.NET and Web Tools 2019

ASP.NET Web Frameworks and Tools 2019 16.3.283.64955
Weitere Informationen finden Sie unter https://www.asp.net/.

Azure App Service-Tools v3.0.0 16.3.283.64955
Azure App Service-Tools v3.0.0

Azure Functions and Web Jobs Tools 16.3.283.64955
Azure Functions and Web Jobs Tools

C#-Tools 3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
C#-Komponenten, die in der IDE verwendet werden. Abhängig von Ihrem Projekttyp und den zugehörigen Einstellungen kann eine andere Version des Compilers verwendet werden.

Extensibility Message Bus 1.2.0 (d16-2@8b56e20)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

IntelliCode-Erweiterung 1.0
Detaillierte Informationen zur IntelliCode Visual Studio-Erweiterung

Microsoft Azure-Tools 2.9
Microsoft Azure-Tools für Microsoft Visual Studio 0x10 – v2.9.20816.1

Microsoft Continuous Delivery Tools für Visual Studio 0.4
Die Konfiguration von Azure DevOps-Pipelines von der Visual Studio-IDE aus wird vereinfacht.

Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual Studio-Tools für Container 1.1
Jetzt können Sie Ihre ASP.NET Core-Anwendung in der Zielumgebung entwickeln, ausführen und überprüfen. Drücken Sie F5, um die Anwendung direkt in einem Container mit Debugfunktionen auszuführen, oder STRG+F5 zum Bearbeiten und Aktualisieren Ihrer Anwendung, ohne den Container erneut erstellen zu müssen.

Mono Debugging for Visual Studio 16.3.7 (9d260c5)
Support for debugging Mono processes with Visual Studio.

NuGet-Paket-Manager 5.3.0
NuGet-Paket-Manager in Visual Studio. Weitere Informationen zu NuGet finden Sie unter https://docs.nuget.org/.

ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

SQL Server Data Tools 16.0.61908.27190
Microsoft SQL Server Data Tools

TypeScript-Tools 16.0.10821.2002
TypeScript-Tools für Microsoft Visual Studio

Visual Basic-Tools 3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
Visual Basic-Komponenten, die in der IDE verwendet werden. Abhängig von Ihrem Projekttyp und den zugehörigen Einstellungen kann eine andere Version des Compilers verwendet werden.

Visual F# Tools 10.4 für F# 4.6 16.3.0-beta.19455.1+0422ff293bb2cc722fe5021b85ef50378a9af823
Microsoft Visual F# Tools 10.4 für f# 4.6

Visual Studio-Tools für Container 1.0
Visual Studio-Tools für Container

Visual Studio-Tools für Unity 4.3.3.0
Visual Studio-Tools für Unity

Visual Studio Code-Debugadapter-Hostpaket 1.0
Interopebene zum Hosten der Visual Studio Code-Adapter in Visual Studio

VisualStudio.Mac 1.0
Mac Extension for Visual Studio

Xamarin 16.3.0.274 (d16-3@06531f8)
Visual Studio-Erweiterung, um Entwicklung für Xamarin.iOS und Xamarin.Android zu ermöglichen.

Xamarin Designer 16.3.0.230 (remotes/origin/d16-3-xcode11@bbe518670)
Visual Studio-Erweiterung zum Aktivieren der Xamarin Designer-Tools in Visual Studio.

Xamarin Templates 16.3.565 (27e9746)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK 10.0.0.43 (d16-3/8af1ca8)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: mono/mono/2019-06@7af64d1ebe9
Java.Interop: xamarin/java.interop/d16-3@5836f58
LibZipSharp: grendello/LibZipSharp/d16-3@71f4a94
LibZip: nih-at/libzip/rel-1-5-1@b95cf3f
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.27.1@8212a2d
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-3@cb41333

Xamarin.iOS and Xamarin.Mac SDK 13.2.0.42 (5e8a208)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

↧

MSBuildProcess keeps reappearing

October 1, 2019, 1:35 am

≫ Next: Warning: (dll) does not contain any types that can be unregistered for COM Interop

≪ Previous: MSB4062 The ProcessFrameworkReferences task could not be loaded from the C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll assembly.

I am quite new to the MSBuild Process and I am stuck on this error for 2 days now. I have a consoletool, which gets called during a build process and is packed into a nuget, so it can easility be used by other projects. The consoletool analyzes used packages in the project where the nuget is included and creates a folder where the console tool places its output. This all works as expected, but the msbuild process never seems to really stop or at least reappears after the execution is finished. I can see, that the folder which is created during the build process just keeps getting recreated again and again. In the windows explorer I can see the processes disappearing just to reappear again.

Here are all the files, which are involved in my msbuildprocess:

myapp.target

<Project><Import Project="$(MSBuildThisFileDirectory)/../../tools/mytargets.targets" /></Project>

mytargets.targets

<Project><Target Name="check" AfterTargets="CoreCompile"><PropertyGroup><Output>files</Output><Directory>$(MSBuildProjectDirectory)$(Output)</Directory><Exe>dotnet $(MSBuildThisFileDirectory)mytool.dll</Exe><Call>$(Exe) $(MSBuildProjectFullPath) $(Directory)</Call></PropertyGroup><MakeDir Directories="$(Directory)"/><Exec Command="$(Call)" /></Target> </Project>

myapp.nuspec

<package xmlns="http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd"><metadata><id>testtool</id><version>1.0.0</version><authors>author</authors><description>
          bla</description></metadata><files><file src="lib\netstandard1.0\_._"                                target="/lib/netstandard1.0/" /><file src="build\netstandard1.0\myapp.targets"                  target="/build/netstandard1.0/myapp.targets" /><file src="tools\mytargets.targets"                               target="/tools/" /><file src="$publishdir$\netcoreapp2.1\**\*"                       target="/tools/netcoreapp2.1/" /></files></package>

myapp.csproj

<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><OutputType>Exe</OutputType><AssemblyName>assemblytest</AssemblyName><TargetFramework>netcoreapp2.1</TargetFramework></PropertyGroup><!-- Pack settings --><PropertyGroup><NoPackageAnalysis>true</NoPackageAnalysis><NuspecFile>myapp.nuspec</NuspecFile><IntermediatePackDir>$(MSBuildProjectDirectory)/bin/$(Configuration)/publish/</IntermediatePackDir><PublishDir>$(IntermediatePackDir)$(TargetFramework)/</PublishDir><NuspecProperties>publishDir=$([MSBuild]::NormalizeDirectory($(IntermediatePackDir)))</NuspecProperties></PropertyGroup><!-- Executes /t:Publish for all target frameworks before packing--><Target Name="PublishAll" BeforeTargets="GenerateNuspec"><ItemGroup><_TargetFramework Include="$(TargetFramework)" /></ItemGroup><MSBuild Projects="$(MSBuildProjectFullPath)" Targets="Publish" Properties="TargetFramework=%(_TargetFramework.Identity)" /></Target><ItemGroup><Folder Include="src\" /><Folder Include="tools\netcoreapp2.1\" /></ItemGroup><ItemGroup><PackageReference Include="Microsoft.Build.Framework" Version="16.0.461" /><PackageReference Include="Microsoft.Build.Utilities.Core" Version="16.0.461" /></ItemGroup></Project>

And this is the structure of the project, which produces the nuget package

myapp
build
netstandard1.0
myapp.targets
lib
netstandard1.0
_._
src
program.cs
tools
mytargets.targets
netcoreapp2.1
myapp.nuspec

The nuget is referenced as usual. I don't really know what to try anymore or how I could further analyze it. I'd be really thankful for some tips :)

↧

Warning: (dll) does not contain any types that can be unregistered for COM Interop

November 15, 2006, 6:13 pm

≫ Next: Create EmbeddedResource before build.

≪ Previous: MSBuildProcess keeps reappearing

I am getting a warning in a large project that I cannot clear.

"(dll) does not contain any types that can be unregistered for COM Interop" and also "(dll) does not contain any types that can be registered for COM Interop".

I have searched the Microsoft website and the web without finding anything useful. I would like to know whether or not it is important and, regardless of whether it is, how to clear it or at least suppress it. I can't even suppress it because there does not appear to be a warning number.

Rick Harrison

↧

Create EmbeddedResource before build.

July 31, 2018, 1:45 am

≫ Next: About problems in the VS build process in the Face Behavior Analysis Toolkit

≪ Previous: Warning: (dll) does not contain any types that can be unregistered for COM Interop

I want to embed local references in the assembly before compiling the main unit. But the written target does not work.

<Target Name="EmbedLocal" BeforeTargets="CoreCompile"><Message Text="Run EmbedLocal for $(MSBuildProjectFullPath)..." Importance="high"/>    <ItemGroup><EmbeddedResource Include="@( ReferencePath->WithMetadataValue( 'CopyLocal', 'true' )->Metadata( 'FullPath' ) )"/></ItemGroup><Message Text="Embed local references complete for $(OutputPath)$(TargetFileName)." Importance="high" /></Target>

@(EmbeddedResource) at this moment contains valid list of paths.

↧

About problems in the VS build process in the Face Behavior Analysis Toolkit

October 3, 2019, 12:49 pm

≫ Next: Integrating FileTracker

≪ Previous: Create EmbeddedResource before build.

严重性代码说明项目文件行禁止显示状态
错误MSB3073 命令“xcopy /I /E /Y /D "F:\大创二\OpenFace-master_new\OpenFace-master\lib\local\LandmarkDetector\model" "F:\大创二\OpenFace-master_new\OpenFace-master\x64\Release\model"
xcopy /I /E /Y /D "F:\大创二\OpenFace-master_new\OpenFace-master\lib\3rdParty\OpenCV\classifiers" "F:\大创二\OpenFace-master_new\OpenFace-master\x64\Release\classifiers"
:VCEnd”已退出，代码为 9009。LandmarkDetectorC:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets138\

严重性代码说明项目文件行禁止显示状态
错误MSB3073 命令“xcopy /I /E /Y /D /C "F:\大创二\OpenFace-master_new\OpenFace-master\lib\3rdParty\OpenCV\x64\v141\bin\Release" "F:\大创二\OpenFace-master_new\OpenFace-master\x64\Release\"
xcopy /I /E /Y /D /C "F:\大创二\OpenFace-master_new\OpenFace-master\lib\3rdParty\OpenCV\bin\opencv_ffmpeg410.dll" "F:\大创二\OpenFace-master_new\OpenFace-master\x64\Release\"
xcopy /I /E /Y /D /C "F:\大创二\OpenFace-master_new\OpenFace-master\lib\3rdParty\OpenCV\bin\opencv_ffmpeg410_64.dll" "F:\大创二\OpenFace-master_new\OpenFace-master\x64\Release\"
xcopy /I /E /Y /D /C "F:\大创二\OpenFace-master_new\OpenFace-master\lib\3rdParty\OpenCV\classifiers" "F:\大创二\OpenFace-master_new\OpenFace-master\x64\Release\classifiers"
:VCEnd”已退出，代码为 9009。UtilitiesC:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets138

↧

Integrating FileTracker

October 8, 2019, 11:07 pm

≫ Next: Build Error "...exited with code 3"

≪ Previous: About problems in the VS build process in the Face Behavior Analysis Toolkit

Hello, I'm trying to create an MSBuild task that makes use of tracker.exe or FileTracker API or TrackedVCToolTask and integrates directly with Visual Studio so that Visual Studio reads the tlogs generated by this task to determine if the task can be skipped or not. It is my understanding, according to Inside the Microsoft Build engine: using MSBuild and Team Foundation Buildthat tlogs belong in the intermediate directory of the project you are building. I've opted using FileTracker API in a custom task that inherits from MSBuild's Task base class.

I am able to produce tlogs through a custom task created through a C# dll that makes calls to the FileTracker API.

I am unable to find a way for Visual Studio to use these tlogs in detecting whether or not to skip the custom target/task.

I am aware of the simpler approach of using Input and Output TaskItem attributes but this approach is not what I'm looking for as it lacks the ability to automatically detect file dependencies.

I've looked at many resources but all references I could find stop just short of explaining the process of implementing and integrating FileTracker's Api/TrackedVCToolTask/tracker.exe with Visual Studio.

Looking forward to any help/resources that can be provided.

↧