I'm just trying out Breeze.js and decided to convert an existing Web API 2.2 (.net 4.5.2) project to Breeze. I went to NuGet and installed the Breeze.ContextProvider and Breeze.ContextProvider.EF6 packages, since I used EF6 for this project. When I add the [BreezeController] attribute to my controllers Visual Studio (2015 CTP) doesn't know what it is ("Cannot resolve symbol 'BreezeController'" error). So I tried installing other NuGet packages that might contain this attribute (i.e. Breeze.Server.WebApi2), but couldn't find any. The docs don't seem to show what assembly I need to use for that attribute, so I'm stuck. Any help for this? Is that attribute deprecated? I can't find any mention of it in the docs... Thanks!
The BreezeControllerAttribute class is part of the Breeze.ContextProvider assembly. ( and is available as a standalone nuget package: Breeze.Server.ContextProvider or as part of the Breeze.Server.WebApi2 nuget) Not sure why you are having this issue, but nuget can be a little flaky... It might be worth removing all nugets and reinstalling them.
I just searched and installed "breeze.webapi2" and had the same issue. When I did a search for "breeze.server.webapi2", I noticed that that package wasn't installed (I thought it was a dependency on the "breeze.webapi2" package).
Installing just the "breeze.server.webapi2" currently doesn't do anything.
I'm doing this via VS2015 CTP6. My coworker was able to install the very same package using VS2013.
Related
I am trying to use some references in Visual Studio, I have installed NuGet to use some libraries.
Is there a way to use only part of the package installed with NuGet? For example, if I am using TeklaOpenApi and the following .dll files are installed with this package:
TeklaModel
TeklaDialog
TeklaDrawing
Use for example just TeklaModel, could I do this using NuGet?
Is there a way to use only part of the package installed with NuGet?
I am afraid that you cannot get what you want. It is designed by nuget package. Usually, when the nuget package contains other dlls which means they are probably depended on a master DLL, or used at runtime.
All of them play an important role in this nuget, so we cannot easily remove them.
Although we can use Assembly Reference format(Right-click on References-->Add Reference--> choose one Dll) to reference the specific dll, but there is a risk that if the DLL depends on other corresponding DLL, an error will be reported. So we don't recommend it.
The best way is to install the whole nuget package with all the related dlls.
Hope it could help you.
So pulling in version 18.9.0 of Aspose.Cells to a netcoreapp project results in the following error
warning NU1701: Package 'Aspose.Cells 18.9.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.
And if you open that nuget you can see that the netstandard target is suffixed with _AuthenticodeSigned.
If you look at the dependencies in the nuget gallery it lists netstandard2.0 as supported
So is _AuthenticodeSigned a valid convention? If so where is the doco? and how do i get NuGet/Visual Studio to recognise it?
We have been able to notice the problem on our end. An issue with ID CELLSNETCORE-9 is already logged in our issue management system for further investigations. Once, we will have some news for you, we will update you here.
Note: I am working as Support developer/ Evangelist at Aspose.
#Simon,
This is to inform you that issue with ID CELLSNETCORE-9 is resolved and updated version Aspose.Cells for .NET Core 18.10.0 is available via NuGet Package Manager. You may please try to update the package and provide your feedback.
I would like to be using sqlite such as I do for sqlserver, in my uses clauses:
using System.Data.Sqlite etc...
What steps should I do?
That did not solve the problem, because I do not have any reference del tipo system.data.sqlite to add. Therefore I cannot use the sqlite framework at all. All i have is the nuget package but I do not know how to install it in VS.
My Problem was to implement the usage of Sqlite in VisualStudio in one of my projects.
1)I started downloading: the system.data.sqlite.core.1.0.108 NUGet package, from here:
https://www.nuget.org/packages/System.Data.SQLite
2)But I did not know how to install it. Then someone pointed out that there is the Package Manager Console in Visual Studio and I can install by Console.
3)Following the tutorial on the same page I did this.
Notice: you must have a solution opened in the VS in order for the PM to install the package. Packages will be installed on that Application only.
4)After that you can access all the functionalities of SQLite by including it with:
Using System.Data.SQLite and System.Data.Sqlite.Generic
I'm trying to make a very simple Xamarin.Forms test application to explore some features of the System.Data.SQLite package (namely encryption). However, I can't seem to get Visual Studio 2012 to add a reference to the package to the project.
Here are the steps I am taking:
Created a new Xamarin.Forms Portable blank app.
Right-click on TestApp (core project) and select Manage NuGet Packages
Search for "sqlite"
Install the "System.Data.SQLite (x86/x64)" package. (This package is version 1.0.97.0 and it is described as "the official SQLite database engine for both x86 and x64 along with the ADO.NET provider.")
According to NuGet, the package was successfully installed.
However, I cannot see the reference added under my project's "References" folder, and I also cannot write "using System.Data.SQLite" without errors ("cannot resolve symbol 'Data'"). Does anyone have any idea why this is happening?
On a side note, I can follow the exact same process described above except instead of creating a Xamarin.Forms Portable blank app, I choose a regular C# console app. This allows me to install the NuGet package fine and it shows up in references as expected.
Posting an update to share what I've learned.
So as Jason sort of alluded to in his answer, the reason I was not able to reference the package in my Xamarin.Forms project is because Xamarin.Forms is, by definition, a PCL project. It's meant to work on all platforms. The package I was referring to in my question is not a PCL, which means that anything in the package that is platform dependent is inaccessable (which is basically the entire package). The SQLite.Net-PCL package is basically the same thing as System.Data.SQLite, but in PCL form, which means it is compatible for use in a Xamarin.Forms project.
Following this logic, it makes sense that I was able to access System.Data.SQLite from a console project, since a console project is not a PCL project and it targets a specific platform.
For PCL projects, use SQLite.Net-PCL.
Although I have added the System.Web.Http assembly to my project X the HttpSelfHostConfiguration type can not be resolved. And I use resharper...
The odd thing is that the HttpConfiguration works.
When I run some integration tests from project Y using static classes in project X I get a runtime exception: The file or assembly System.Web.Http, Version=5.0.0.0 can not be found etc...
Why can I not resolve the HttpSelfHostConfiguration?
HttpSelfHostConfiguration is located in the assembly System.Web.Http.SelfHost.dll and the namespace System.Web.Http.SelfHost. So you might need to add a reference to this assembly, maybe by adding the Self Host Nuget package.
If you've already added this package, the error might be related to the other errors you're experiencing regarding System.Web.Http v5.0.0.0: I've also experienced some strange behavior after upgrading a Web API project to VS2013. I could only solve this by removing the Web API Nuget packages (the error message resembled yours), deleting some remainders of old versions in the packages folder and adding the required Nuget packages anew.
Solution:
You can add reference from the NuGet Package Library.
Search for Package: Microsoft.AspNet.WebApi.SelfHost
and install it.
For those who has any confusion in adding NuGet Package Reference:
In Visual Studio Solution Explorer, Right Click References > Manage NuGet Packages