In VS2013.4, when I try to add Mono.Cecil nuget package in my fsharp project :
PM> Install-Package Mono.Cecil
Installing 'Mono.Cecil 0.9.5.4'.
Successfully installed 'Mono.Cecil 0.9.5.4'.
Adding 'Mono.Cecil 0.9.5.4' to Ying.Unit.
No exact match found for removing reference 'Mono.Cecil.Mdb'. Trying case-insensitive search...
Failed to find match for removing reference 'Mono.Cecil.Mdb'.
No exact match found for removing reference 'Mono.Cecil.Pdb'. Trying case-insensitive search...
Failed to find match for removing reference 'Mono.Cecil.Pdb'.
No exact match found for removing reference 'Mono.Cecil.Rocks'. Trying case-insensitive search...
Failed to find match for removing reference 'Mono.Cecil.Rocks'.
Uninstalling 'Mono.Cecil 0.9.5.4'.
Successfully uninstalled 'Mono.Cecil 0.9.5.4'.
Install failed. Rolling back...
Install-Package : Failed to add reference to 'Mono.Cecil.Mdb'.
At line:1 char:1
+ Install-Package Mono.Cecil
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], InvalidOperationException
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
My project targets .NET 4.5 with F# 3.1 runtime (4.3.1.0).
Any thoughts ?
Thanks
Vianney
Related
I downloaded this sample MSGraph console app and got it to run. It uses .NET 4.6.1. I'm trying to convert it to .NET Core 2.0. I'm unable to install MSGraph using this NuGet package:
Install-Package Microsoft.Graph -Version 1.11.0
It gives the following error:
Installing Microsoft.Graph 1.11.0.
Install-Package : NU1605: Detected package downgrade: Microsoft.Graph.Core from 1.11.0 to 1.10.0. Reference the package directly from the project to select a different version.
ConsoleMSGraph -> Microsoft.Graph 1.11.0 -> Microsoft.Graph.Core (>= 1.11.0)
ConsoleMSGraph -> Microsoft.Graph.Core (>= 1.10.0)
At line:1 char:1
+ Install-Package Microsoft.Graph -Version 1.11.0
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], Exception
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand
Install-Package : Package restore failed. Rolling back package changes for 'ConsoleMSGraph'.
At line:1 char:1
+ Install-Package Microsoft.Graph -Version 1.11.0
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], Exception
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand
Time Elapsed: 00:00:14.1377482
PM>
Is there an MSGraph package that works with .NET Core 2.0?
You're missing some repro steps. That sample target 1.7.0 of the client. Yes, that package will work with Net Core 2. It targets NetStandard 1.1. Here's a Net Core 2 sample:
https://github.com/MIchaelMainer/GraphNetCore2
I'm relatively new to dot net core and EF core. In Package Manager Console, when I type 'EntityFrameworkCore\Add-Migration Initial' I get the following error.
PM> EntityFrameworkCore\Add-Migration Initial
Both Entity Framework Core and Entity Framework 6.x commands are installed. The Entity Framework Core version is executing. You can fully qualify the command to select which one to execute, 'EntityFramework\Add-Migration' for EF6.x and 'EntityFrameworkCore\Add-Migration' for EF Core.
EntityFrameworkCore\Add-Migration : Exception calling "CreateInstanceAndUnwrap" with "8" argument(s): "Could not load file or assembly
'Microsoft.EntityFrameworkCore.Design.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file
specified."
At line:1 char:1
+ EntityFrameworkCore\Add-Migration Initial
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Add-Migration], MethodInvocationException
+ FullyQualifiedErrorId : FileNotFoundException,Add-Migration
I've googled the error but have yet to find any working solutions. Any ideas? My machine is 64 bit running Windows 10. I am using VS 2017 professional 15.5.2
Many thanks
Neo4j3.3.3 community edition, while trying to install-service its show below error. Tried on different machines. How to resolve this?
I am using Java version 1.8.0_162
I have JAVA_HOME environment variable set to C:\Program Files\Java\jdk1.8.0_162\bin
Error:
Invoke-Neo4j : Unable to determine the version of the installation at
D:\neo4j\neo4j-community-3.3.3
At line:1 char:221
+ ... t.psd1'; Exit (Invoke-Neo4j install-service)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
tion
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
n,Invoke-Neo4j
I encountered this problem too, and got it right by setting JAVA_HOME to JRE folder, which is C:\Program Files\Java\jre-X.X.X.
I think install-service is trying to fix a jdk path by adding some postfix, which is weird and causes this problem.
When i run following command in package manager console:
install-package Thinktecture.IdentityServer3
I am getting error:
Install-Package : Unable to find package 'Thinktecture.IdentityServer3'
At line:1 char:16
+ install-package <<<< Thinktecture.IdentityServer3
+ CategoryInfo : NotSpecified: (:) [Install-Package], Exception
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand
I am following this tutorial to secure my restful api- https://identityserver.github.io/Documentation/docs/overview/simplestOAuth.html
and using visual studio 2015 express for web.
It should be install-package IdentityServer3
Check the latest tutorial here https://identityserver.github.io/Documentation/docsv2/overview/mvcGettingStarted.html
This error has perplexed me for the last few days and can find little to no information on Google regarding this. This started the other day when I was assigned a new laptop by work and I'm essentially running this on a clean install of Windows 7 x64 with VS2012 Update 1.
Whenever I start up a project using Entity Framework 5 or 6-alpha, this exception gets thrown to the package manager console:
New-Object : Cannot find an overload for "Version" and the argument count: "2".
At <project path>\packages\EntityFramework.5.0.0\tools\in
it.ps1:5 char:46
+ if ($PSVersionTable.PSVersion -ge (New-Object <<<< Version #( 3, 0 )))
+ CategoryInfo : InvalidOperation: (:) [New-Object], MethodException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand
Test-ModuleManifest : Invalid Module Manifest path '<project path>
\packages\EntityFramework.5.0.0\tools\'. The path argument must resolve to a single file in the file system with a '
.psd1' extension. Please fix the path specification and try again.
At <project path>\packages\EntityFramework.5.0.0\tools\in
it.ps1:14 char:34
+ $thisModule = Test-ModuleManifest <<<< (Join-Path $toolsPath $thisModuleManifest)
+ CategoryInfo : InvalidArgument: (C:\Users\stephe...rk.5.0.0\tools\:String) [Test-ModuleManifest], InvalidOper
ationException
+ FullyQualifiedErrorId : Modules_InvalidModuleManifestPath,Microsoft.PowerShell.Commands.TestModuleManifestCommand
Import-Module : Cannot bind argument to parameter 'Name' because it is null.
At <project path>\packages\EntityFramework.5.0.0\tools\in
it.ps1:31 char:18
+ Import-Module <<<< $thisModule
+ CategoryInfo : InvalidData: (:) [Import-Module], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.ImportModuleComma
nd
I can get rid of this error by editing the package scripts manually, but that feels like it would be the wrong approach. There are also multiple instances of it checking the Powershell version in this manner so I'm suspecting it's something that's wrong with my computers's configuration.
This is affecting multiple ASP.NET MVC 4 projects of mine targeting .NET 4.5. I can't run any Entity Framework commands such as Enable-Migrations or Update-Database as a result of this error. Any clues will be greatly appreciated.
I finally got it to work, it was as simple as upgrading to PowerShell 3.0. That kinda makes the version detection pointless, but hey, at least it works.