We Keep Coding

Assembly references of PackageReference missing when building with jenkins and devenv.com

I'm building a solution that contains a class library, a UnitTest Project and a .vdproj setup project. Because MSBuild cannot handle vdproj I'm using devenv.com. I'm calling C:\NuGet\nuget.exe restore "%WORKSPACE%\solution.sln" -ConfigFile C:\NuGet\NuGet.config before the build starts and build with "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.com" rotring.tacton.export.sln /build "ci".
After that I execute the tests with "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" "%WORKSPACE%\testproject.test\bin\ci\tests.dll".
The nuget restore command tells me that every package has been restored correctly and to the right place:
Added package 'package.1.9.11' to folder 'C:\dev\workspace\solution\packages'.
But still I'm getting the error:
error CS0234: The type or namespace name 'sometype' does not exist in the namespace 'somenamespace' (are you missing an assembly reference?)
Local builds just work fine even when I'm executing the console build mentioned above manually.
Do I need to restore the packages somehow with devenv.com? Isn't the advantage of PackageReference that all packages are stored at the same place compared to packages.config?
Update: I managed to find a partly myself. One thing was that my Test-Project was not migrated to PackageReference and caused an error.
However I was able to build the solution by first restoring the packages with MSBuild:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exe" /t:Restore /p:RestoreConfigFile="C:\NuGet\NuGet.config"
And then building the solution with devenv.com:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.com" solution.sln /build "ci"
Now the only problem I face is that msbuild only restores the packages from the main project and doesn't care about the Test-Project.

Not able to use Windows Script Host Object Model in .net 3.5 project

I have a C# console application (.Net version 3.5) with following code
static void Main(string[] args)
{
IWshRuntimeLibrary.WshNetwork aNetworkInstance = new IWshRuntimeLibrary.WshNetwork();
}
When I run the program it is throwing following error.
An unhandled exception of type 'System.BadImageFormatException'
occurred in Microsoft.VisualStudio.HostingProcess.Utilities.dll
Additional information: Could not load file or assembly
'Interop.IWshRuntimeLibrary, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies. This assembly is
built by a runtime newer than the currently loaded runtime and cannot
be loaded.
I found that the generated interop file Interop.IWshRuntimeLibrary.dll is refering to 4.0.0.0 version of mscorelib.
.assembly extern mscorlib
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4..
.ver 4:0:0:0
}
If I change the .net version of the project to 4, then it is working fine. Any idea why the Interop.IWshRuntimeLibrary.dll is always refering to version 4 of mscorlib even when I select .net 3.5 in the project?
PS: The same program is working in other systems. The issue is only in one system.
EDIT: Following are the steps I have done.
Create a C# Console application (.Net version 3.5).
Add referece to Windows Scribt Host Object model
Add following line in the Main()
static void Main(string[] args)
{
IWshRuntimeLibrary.WshNetwork aNetworkInstance = new IWshRuntimeLibrary.WshNetwork();
}
When I run the application, it is throwing following exception.
An unhandled exception of type 'System.BadImageFormatException'
occurred in mscorlib.dll
Additional information: Could not load file or assembly
'Interop.IWshRuntimeLibrary, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies. This assembly is
built by a runtime newer than the currently loaded runtime and cannot
be loaded.
I am able to build and run the project in other machines.
If I copy the Interop.IWshRuntimeLibrary.dll generated in another machine, then also the program is running in my machine.
But I am not able to run the program with the Interop.IWshRuntimeLibrary.dll generated in my machine.
I know it is a strange problem. May be I have to reformat my hard disk as you suggested by Hans Passant :(
EDIT: Output of the detailed build
1> C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\TlbImp.exe C:\Windows\SysWOW64\wshom.ocx /namespace:IWshRuntimeLibrary /machine:X86 /out:obj\x86\Release\Interop.IWshRuntimeLibrary.dll /sysarray /transform:DispRet /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll" /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll" /reference:C:\WINDOWS\assembly\GAC\stdole\7.0.3300.0__b03f5f7f11d50a3a\stdole.dll
1> Microsoft (R) .NET Framework Type Library to Assembly Converter 4.0.30319.33440
1> Copyright (C) Microsoft Corporation. All rights reserved.
1>
1> TlbImp : Type library imported to C:\Users\IC007121\Documents\Visual Studio 2013\Projects\wsherrortest\wsherrortest\obj\x86\Release\Interop.IWshRuntimeLibrary.dll
1> Resolved COM reference for item "IWshRuntimeLibrary": "obj\x86\Release\Interop.IWshRuntimeLibrary.dll".

Visual Studio uses a SDK tool named TlbImp.exe to build COM references import files. The MsBuild task that does that is named ResolveComReference. This task uses an algorithm that tries to find the proper TlbImp version on the machine that builds the project.
In your case as we see it from msbuild diagnostics, it uses the TlbImp from "C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools". Unfortunately, this TlbImp builds CLR 4 assemblies. So you need to use another TlbImp. On my machine, it uses it from "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin" which builds CLR 2 assembly. You probably don't have that TlbImp installed on your build machine so the algorithm redirects silently to the newer one (sounds like a bug, I think it should report the problem, but I'm unsure).
To fix this, you can install an older version of Visual Studio or Windows SDK and it should work magically, or you can configure your project to use a proper TlbImp V3.5 if you have it on your machine somewhere (if you don't have it, then you must install something).
Here is how to modify the MsBuild project from Visual Studio:
right click on the project node, Unload Project
right click on the project node and Edit Project
add the following line to your msbuild project file
right click on the project node and Reload project
rebuild
...
<PropertyGroup>
... other properties ...
... <ResolveComReferenceToolPath should point to a directory that contains TLBIMP V3.5
<ResolveComReferenceToolPath>C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin</ResolveComReferenceToolPath>
</PropertyGroup>
...

error CS0103: The name `HttpClientFactory' does not exist in the current context

I'm trying to build this api_query https://github.com/CryptopiaNZ/CryptopiaApi-Csharp.git
$ uname -a
Linux kali 4.0.0-kali1-amd64 #1 SMP Debian 4.0.4-1+kali2 (2015-06-03) x86_64 GNU/Linux
Building with mono:
$ xbuild --version
XBuild Engine Version 12.0
Mono, Version 3.2.8.0
Copyright (C) 2005-2013 Various Mono authors
And trying to build this project:
$ xbuild CryptopiaApi.csproj
XBuild Engine Version 12.0
Mono, Version 3.2.8.0
Copyright (C) 2005-2013 Various Mono authors
Build started 08.09.2015 16:13:55.
__________________________________________________
Project "/usr/src/cryptopia/CryptopiaApi-Csharp/CryptopiaApi/CryptopiaApi/CryptopiaApi/CryptopiaApi.csproj" (default target(s)):
Target PrepareForBuild:
Configuration: Debug Platform: AnyCPU
Target GenerateSatelliteAssemblies:
No input files were specified for target GenerateSatelliteAssemblies, skipping.
Target GenerateTargetFrameworkMonikerAttribute:
Skipping target "GenerateTargetFrameworkMonikerAttribute" because its outputs are up-to-date.
Target CoreCompile:
Tool /usr/bin/mcs execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/CryptopiaApi.dll CryptopiaPrivateAPI.cs CryptopiaPublicAPI.cs DataObjects/Private/BalanceRequest.cs DataObjects/Private/BalanceResponse.cs DataObjects/Private/CancelTradeRequest.cs DataObjects/Private/CancelTradeResponse.cs DataObjects/Private/DepositAddressRequest.cs DataObjects/Private/DepositAddressResponse.cs DataObjects/Private/OpenOrdersRequest.cs DataObjects/Private/OpenOrdersResponse.cs DataObjects/Private/SubmitTipRequest.cs DataObjects/Private/SubmitTipResponse.cs DataObjects/Private/SubmitTradeRequest.cs DataObjects/Private/SubmitTradeResponse.cs DataObjects/Private/TradeHistoryRequest.cs DataObjects/Private/TradeHistoryResponse.cs DataObjects/Private/TransactionRequest.cs DataObjects/Private/TransactionResponse.cs DataObjects/Public/CurrenciesResponse.cs DataObjects/Public/MarketHistoryRequest.cs DataObjects/Public/MarketHistoryResponse.cs DataObjects/Public/MarketOrdersRequest.cs DataObjects/Public/MarketOrdersResponse.cs DataObjects/Public/MarketRequest.cs DataObjects/Public/MarketResponse.cs DataObjects/Public/MarketsRequest.cs DataObjects/Public/MarketsResponse.cs DataObjects/Public/TradePairsResponse.cs Implementation/AuthDelegatingHandler.cs Implementation/ICryptopiaApiPrivate.cs Implementation/ICryptopiaApiPublic.cs Implementation/IRequest.cs Implementation/IResponse.cs Implementation/PrivateApiCall.cs Implementation/PublicApiCall.cs Models/BalanceResult.cs Models/CurrencyResult.cs Models/MarketHistoryResult.cs Models/MarketOrderResult.cs Models/MarketOrdersResult.cs Models/MarketResult.cs Models/OpenOrderResult.cs Models/TradeHistoryResult.cs Models/TradePairResult.cs Models/TransactionResult.cs Properties/AssemblyInfo.cs /target:library /define:"DEBUG;TRACE" /reference:../packages/Newtonsoft.Json.7.0.1/lib/net45/Newtonsoft.Json.dll /reference:/usr/lib/mono/4.5/System.dll /reference:/usr/lib/mono/4.5/System.Net.dll /reference:/usr/lib/mono/4.5/System.Net.Http.dll /reference:/usr/lib/mono/4.5/System.Net.Http.Formatting.dll /reference:/usr/lib/mono/4.5/System.Web.dll /reference:/usr/lib/mono/4.5/System.Xml.Linq.dll /reference:/usr/lib/mono/4.5/System.Data.DataSetExtensions.dll /reference:/usr/lib/mono/4.5/Microsoft.CSharp.dll /reference:/usr/lib/mono/4.5/System.Data.dll /reference:/usr/lib/mono/4.5/System.Xml.dll /reference:/usr/lib/mono/4.5/System.Core.dll /warn:4
CryptopiaPrivateAPI.cs(23,14): error CS0103: The name `HttpClientFactory' does not exist in the current context
CryptopiaPublicAPI.cs(22,14): error CS0103: The name `HttpClientFactory' does not exist in the current context
CryptopiaPublicAPI.cs(70,11): error CS0433: The imported type `Newtonsoft.Json.Linq.JObject' is defined multiple times
/usr/src/cryptopia/CryptopiaApi-Csharp/CryptopiaApi/CryptopiaApi/CryptopiaApi/../packages/Newtonsoft.Json.7.0.1/lib/net45/Newtonsoft.Json.dll (Location of the symbol related to previous error)
/usr/lib/mono/4.5/System.Net.Http.Formatting.dll (Location of the symbol related to previous error)
Task "Csc" execution -- FAILED
Done building target "CoreCompile" in project "/usr/src/cryptopia/CryptopiaApi-Csharp/CryptopiaApi/CryptopiaApi/CryptopiaApi/CryptopiaApi.csproj".-- FAILED
Done building project "/usr/src/cryptopia/CryptopiaApi-Csharp/CryptopiaApi/CryptopiaApi/CryptopiaApi/CryptopiaApi.csproj".-- FAILED
Build FAILED.
Errors:
/usr/src/cryptopia/CryptopiaApi-Csharp/CryptopiaApi/CryptopiaApi/CryptopiaApi/CryptopiaApi.csproj (default targets) ->
/usr/lib/mono/4.5/Microsoft.CSharp.targets (CoreCompile target) ->
CryptopiaPrivateAPI.cs(23,14): error CS0103: The name `HttpClientFactory' does not exist in the current context
CryptopiaPublicAPI.cs(22,14): error CS0103: The name `HttpClientFactory' does not exist in the current context
CryptopiaPublicAPI.cs(70,11): error CS0433: The imported type `Newtonsoft.Json.Linq.JObject' is defined multiple times
0 Warning(s)
3 Error(s)
Time Elapsed 00:00:00.9231760
What does this err, means: "error CS0103: The name `HttpClientFactory' does not exist in the current context" ??
As I can google, HttpClientFactory is a part of namespace System.Net.Http which is included. Almost all of libmono- are installed on my system.
Edit:
Moreover, I've installed Microsoft Visual Studio Community 2015 14.0.23107.0 D14REL, latest version and errors are the same.
Edit2:
Probably, I've found the solution. It is Visual Studio 2013, not 2015. I do not know which mono shall it be, probably kind of downgrade would help to build HttpClientFactory...

Downgrade the Nuget package Microsoft.AspNet.WebApi.Client to v5.2.2.
It's worked for me.

Missing Automation from namespace 'System.Management'. Missing assembly reference

System: Windows 7 Professional 64 bit, PowerShell v 2.0, no Visual Studio (can't be installed and others too)
Trying to run PowerShell from C#. This is the code snippet:
using System;
using System.Management.Automation;
class Hello {
static void Main(string[] args) {
PowerShell ps = PowerShell.Create();
ps.AddCommand("Get-Process");
Console.WriteLine("Process Id");
Console.WriteLine("----------------------------");
foreach (PSObject result in ps.Invoke()) {
Console.WriteLine(
"{0,-24}{1}",
result.Members["ProcessName"].Value,
result.Members["Id"].Value);
}
}
}
Error:
e:\foo.cs(2,25): error CS0234: The type or namespace name 'Automation' does not exist in the namespace 'System.Management' (are you missing an assembly reference?)
Since no Visual Studio is there, I am running code in raw manner. Because of error, I downloaded dll from http://www.dll-found.com/system.management.automation.dll_download.html and placed in dir as per instruction. After rebooting machine, there was no success.
First, I want to ask a general question. How to install missing assembly or dll file (only), because for some you might have to install whole Windows or PowerShell SDK or .NET Framework.
EDIT
I have place downloaded dll file in C:\Windows\SysWOW64, C:\Windows\system32, C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5 and C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0.
I am compiling using:
C:\Windows\Microsoft.NET\Framework\v3.5\csc.exe /target:exe /out:E:\foo.exe E:\foo.cs

WARNING: Never ever download DLLs from random websites in any sane situation. Use NuGet packages (or whatever your preferred package manager is for your project) whenever possible. If a DLL is not found, there is almost always a good reason for it, and you need to find out what it is and fix it, not just get the DLL from the internet.
If you have this problem after re-targeting an old project to, for example, .NET 4.8, then it is because NuGet package names have changed.
Uninstall the package System.Management.Automation
Install the package Microsoft.PowerShell.5.1.ReferenceAssemblies (NuGet)
This package name appears in the documentation of classes in the namespace System.Management.Automation.

NuGet worked for me.
PM> Install-Package System.Management.Automation.dll -Version 10.0.10586

You must use /reference command line parameter to csc.exe, described in MSDN:
C:\Windows\Microsoft.NET\Framework\v3.5\csc.exe /reference:system.management.automation.dll /target:exe /out:E:\foo.exe /E:\foo.cs

How to Configure Bamboo to Build NUnit Tests?

I am working on setting a project to use bamboo for CI testing, but have hit a hitch when attempting to compile unit tests. We are using the .NET framework 4.5 and NUnit v2.6.3.13283. When I am in bamboo, I have set up the specific job to check out the source code when a new commit is pushed, and then use MSBuild to build the code. Unfortunately, when it reaches this second step, it decides that it no longer understands what NUnit is.
I have the nunit.framework.dll in the same directory (bin\Debug) as the class .dll, so I'm definitely confused as to how I should go about having MSBuild work out building the NUnit tests.
Any help would be appreciated.
EDIT: Error log for those not faint of heart.
c:\Windows\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig
/nowarn:1701,1702 /nostdlib+ /platform:AnyCPU /errorreport:prompt
/warn:4 /define:DEBUG;TRACE
/reference:c:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll
/reference:C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
/reference:"C:\build-dir\UCL-UNL-JOB1\Unit Class
Library\bin\Debug\Unit Class Library.dll" /debug+ /debug:full
/filealign:512 /optimize-
/out:obj\Debug\UnitClassLibraryNUnitTests.dll /target:library
AngleNUnitTests.cs
"C:\Users\Bamboo\AppData\Local\Temp.NETFramework,Version=v4.5.AssemblyAttributes.cs"
AngleNUnitTests.cs(5,7): error CS0246: The type or namespace name
'NUnit' could not be found (are you missing a using directive or an
assembly reference?)
[C:\build-dir\UCL-UNL-JOB1\UnitClassLibraryNUnitTests\UnitClassLibraryNUnitTests.csproj]
AngleNUnitTests.cs(12,10): error CS0246: The type or namespace name
'Test' could not be found (are you missing a using directive or an
assembly reference?)
[C:\build-dir\UCL-UNL-JOB1\UnitClassLibraryNUnitTests\UnitClassLibraryNUnitTests.csproj]
etc.

You need to use a previous task to MSBuild one (Maybe you could consider to use the VisualStudio Task it works like a charm).
This previous task is a Command Task, it will update the Dlls related to the NuGet Package, in order to achieve it:
Create a New Executable on Bamboo, pointing to the nuget.exe file (if you don't have it you could download from https://www.nuget.org/
Create a New Command Task with the executable your created on the previous step.
On the Argument field: "restore YourSolution.sln"
In my approach I am using a VisualStudio task and after this one a MSTest Runner task.

When using Nuget with a source code repository, you have a couple of options.
1) check in your nuget executable to source code and create a bamboo command task that calls that location relative to the build directory, ${bamboo.build.working.directory}\tools\Nuget.exe.
2) Install the Nuget exe directly on the build server. Then you can create a new executable on Bamboo that you can reference in any task.
To create a new executable for use in tasks, use this - https://confluence.atlassian.com/display/BAMBOO/Defining+a+new+executable+capability

I guess you are using NuGet?
If so, you need to enable NuGet Package restore, because MSBuild does not know how to resolve these NuGet packages. This will create a .nuget directory in your solution which needs to be pushed the repository bamboo uses for the build.
Second problem I encountered when configuring the NUnit test runner with bamboo: the nunit-console.exe uses .NET Framework 3.5 which was not installed on my build server.