I have versions 2.15 of Mailkit and MimeKit. Mimekit is dependent on System.Buffers 4.5.1. When running the code through VSCode there is no problem. But in Powershell Desktop it does not work because it is looking for System.Buffers 4.0.2.0 (which is not even available on nuget). One odd thing on top of this is that it still works in VSCode when I comment out the line to add the System.Buffers.dll, maybe this is a clue.
Add-Type -Path "C:\Program Files\PackageManagement\Nuget\Packages\system.buffers\4.5.1\lib\netstandard2.0\System.Buffers.dll"
Add-Type -Path "C:\Program Files\PackageManagement\NuGet\Packages\mimekit\2.15.0\lib\netstandard2.0\MimeKit.dll"
Add-Type -Path "C:\Program Files\PackageManagement\NuGet\Packages\mailkit\2.15.0\lib\netstandard2.0\MailKit.dll"
Exception calling "Send" with "1" argument(s): "Could not load file or assembly 'System.Buffers, Version=4.0.2.0,
Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file
specified."```
I am downloaded the zookeeper from link https://www.apache.org/dyn/closer.lua/zookeeper/zookeeper-3.6.1/apache-zookeeper-3.6.1-bin.tar.gz
My Java home path is C:\Program Files (x86)\Java\jdk1.8.0_151.
When I try to start the zkServer.cmd I am getting message as "\Java\jdk1.8.0_151 was unexpected at this time."
Put you java path into double quote, like this (in enviroment variables) :
"C:\Program Files (x86)\Java\jdk1.8.0_151"
or change your java installation path to another folder such as :
C:\java
I'm having a problem with testing example of code for STM32F103 from libopencm3.
I included a libopencm3 in directory with inc files, and added inc directory to "Path and Symbols". I get an error like no file or directory, even though i have file "libopencm3/stm32/common/rcc_common_all.h" in directory inc. What i'm doing wrong?
I cannot compile single ts-2.2.2 file, output I get is:
error TS5023: Unknown compiler option 'strictNullChecks'.
error TS5023: Unknown compiler option 'alwaysStrict'.
In the bottom-right corner VSCode displays TypeScript 2.2.2 which is the version I want to target. However, if I open my *.ts file, at the top of the screen a warning appears saying that "Version mismatch! global tsc (1.8.34) != VS Code's language service (2.2.2). Inconsistent compile errors might occur".
If I execute command 'where tsc' I get:
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.8\tsc.exe
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.8\tsc.js
How to excplicitly point the typescript compiler so that build process uses ts 2.2.2?
I've used NUnit before, but not in a while, and never on this machine. I unzipped version 2.4.8 under Program Files, and I keep getting this error when trying to load my tests.
Could not load file or assembly 'nunit.framework, Version=2.4.8.0, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77' or one of its dependencies. The system cannot find the file specified**
In order to simplify the problem, I've compiled the most basic possible test file.
using NUnit.Framework;
namespace test
{
[TestFixture]
public class Tester
{
[Test]
public void ATest()
{
Assert.IsTrue(false, "At least the test ran!");
}
}
}
I've added "C:\Program Files\NUnit-2.4.8-net-2.0\bin" to my PATH (and rebooted). Note that if I copy the test assembly into that folder, then
C:\Program Files\NUnit-2.4.8-net-2.0\bin>nunit-console test.dll
works, but
C:\Program Files\NUnit-2.4.8-net-2.0\bin>nunit-console c:\dev\nunit_test\test.dll
and
C:\dev\nunit_test>nunit_console test.dll
fail with the above error.
Presumably I could get around this by copying the NUnit.Framework DLL file into my project's bin folder, but I don't remember having to do this in the past. Moreover, I get the same error in the GUI. Shouldn't the GUI know where the framework is located (that is, in the same folder)?
I'm not using Visual Studio. I use the following line to compile the test project.
%windir%\Microsoft.NET\Framework\v2.0.50727\csc.exe /r:"C:\Program Files\NUnit-2.4.8-net-2.0\bin\nunit.framework.dll" /t:library /out:test.dll test.cs
I tried both the .msi and the .zip file with the same result.
Make sure you have added a reference to nunit.framework. If you have, then make sure the properties of that reference have the copy local property set to true.
I had the same problem, and I had installed using NUnit-2.4.8-net-2.0.msi. Expanding on the "add to the GAC" comment, here's what I did:
Open your "Visual Studio command prompt (generally: make sure gacutil is in your path) and: cd "C:\Program Files\NUnit 2.4.8\bin"
Unregister your NUnit entries from the GAC. You can do this by finding the NUnit entries registered in the GAC:
gacutil /l | find /i "nunit" > temp.bat && notepad temp.bat
Prepend the nunit.core and nunit.framework lines with "gacutil /uf", i.e.:
gacutil /uf nunit.core,Version=2.4.2.0,Culture=neutral,PublicKeyToken=96d09a1eb7f44a77
gacutil /uf nunit.framework,Version=2.4.2.0,Culture=neutral,PublicKeyToken=96d09a1eb7f44a77
Run your .bat file to remove them:
temp.bat
Register the NUnit DLL files you need:
gacutil /i nunit.core.dll
gacutil /i nunit.framework.dll
If you install using NUnit-2.4.8-net-2.0.msi, the NUnit assemblies are added to the GAC.
You can also reinstall manually by running gacutil from the Visual Studio 2005 command prompt.
Note that the current NUnit installation (2.5.10) doesn't register itself automatically in the GAC.
If you must use GAC, register it via gacutil /i <nunitframeworkpath> where nunitframeworkpath is usually %Program Files%\NUnit\net-2.0\framework\nunit-framework.
I got this error message today when I tried to add a new test assembly to an existing NUnit test project. It seems that my test projects had multiple path references to identical nunit.framework.dll assemblies.
If you have more than one test assembly in your NUnit project, you may want to verify the Path property of the nunit.framework reference in your test projects. Once I made them match, the error message went away.