`Breeze.Server.ContextProvider.NH not exist - breeze

Following the documentation described in this link, I'm trying to install the Breeze with NHibernate support.
But the Breeze.Server.ContextProvider.NH does not exist, what should I do? What are the steps to use Breeze with NHibernate?

The Breeze.ContextProvider.NH source and dll is available on GitHub, but we are still in testing on it, so we haven't created a nuget package for it yet.

The nuget package is now available, and the NorthBreeze sample
is now updated to use Breeze 1.4.8 and WebApi 2
I updated the sample by removing all the existing references, then installing the nuget package Breeze.WebApi2.NH
Except for some using statements, and one redundant line of the Web.config, I didn't need to change any code.

Related

I am not able to add insigths telemetry to new Asp .NET framework project

I want to test the Azure Insights telemetry and for this purpose, I have created a new free Azure account and a new MVC Web App Application (Framework 4.7.2)
The App runs correctly.
After that, I tried to add the telemetry: project -> Add Application Insights telemetry
Following the wizard. I get the following error that I am not able to solve.
System.NotImplementedException: The method or operation is not
implemented. at EnvDTE.SourceControl.CheckOutItem(String ItemName) at
Microsoft.WebTools.Shared.VS.VisualStudio.Wrappers.VsSourceControlWrapper.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown
I tried to update the NuGet packages too. But nothing to do.
I have followed step by step the official Microsoft docs.
Some details for the installation process:
I'm having problems only with the .NET framework.
With .NET Core, anything works correctly.
Googling I didn't find any solution.
There are some other dependencies you need to install as well,
Install-Package Microsoft.ApplicationInsights.DependencyCollector -Version 2.6.4
Install-Package Microsoft.ApplicationInsights.PerfCounterCollector -Version 2.6.4
Install-Package Microsoft.ApplicationInsights.Web -Version 2.6.4
Install-Package Microsoft.ApplicationInsights.WindowsServer -Version 2.6.4
Install-Package Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel -Version 2.6.4
Try as mentioned here
Choose the first option when adding insights, Application Insights SDK. That will install all the necessary packages.
Once that's done, you will need to add instrumentation key to the config file. Add that on top.
Your error looks more of source control rather that the project.
If you trying to work in source control and adding insights to already checked-in project, may be try creating a dummy project, and add insights to it. That will give more clarity on error, as well as help to pin-point exact issue.
I had the same issue with adding microsoft identity platform in VS 2022:
System.NotImplementedException: The method or operation is not implemented.
at EnvDTE.SourceControl.CheckOutItem(String ItemName)
When I changed Tools/Options/Source Control from "None" to "git" (also when I am using Git with an external tool, the error was gone.
To me it looks just like one of a VS bug on a certain configuration. Try to uninstall whole VS and then install latest version again. Try another PC if you can.
I encountered this problem also. The work around that eventually worked for me was to add Application Insights in Visual Studio 2017, instead of in 2019 which I normally use.
Your error looks more of source control rather that the project. If you trying to work in source control and adding insights to already checked-in project, may be try creating a dummy project, and add insights to it. That will give more clarity on error, as well as help to pin-point exact issue.
That does not seem to be the case for me. I completely disabled source control and the problem still persisted. When I got the issue "fixed" by using VS2017 source control was running.
To me it looks just like one of a VS bug on a certain configuration. Try to uninstall whole VS and then install latest version again. Try another PC if you can.
I tried this, did not work for me.

NuGet in a project template

This question is about how to set up a project template to satisfy dependencies.
First, some context.
I have a MVC4/Durandal project that I'm trying to turn into a project template that distils all the goodness from a recent project, for re-use.
After creating a new project, adding all the non-standard good bits and shaking down the stub project so that it compiles and runs properly, I copied the project folder and plonked it on another computer with a freshly minted VS2013 installation, to see what broke.
The following were MIA:
Antlr.Runtime
System.Net.Http.Extensions
System.Net.Http.Primitives
System.Web.Optimization
WebActivator
WebGrease
There are a couple of issues making it less than obvious to me as to how I should proceed.
Installation of these things happened so long ago that I really couldn't say how they got onto my development workstation
In many cases package dependencies mean that installing one NuGET package will implicitly satisfy other dependencies
I don't know how set up a project template so that it causes NuGET package(s) to be installed
A bit of guidance would be appreciated, not to mention advice on best practice.
Update
It appears there is direct NuGet support for project templates, I'm still reading about it here and also here.
Since allowing NuGet to automatically resolve dependencies is a good way to ensure compatible versions are installed in the right order, the remaining question is looking at the missing assemblies, how can I determine the most dependent package(s)?
It seems that omitting the packages folder produces a slim template, and the projects produced therefrom install the missing files as soon as you start a build. That's good enough for me.
I would simply start with a blank ASP.NET 4.5 MVC project. The most basic dependencies should be satisfied then. NuGet has basic packages for Mvc and other packages you may need. NuGet packages are designed to self contain the missing assemblies they need. They'll get published in IIS when you deploy so you don't install anything on the server.

How do I delete everything oath from my aspnetmvc project?

How do I find out what references what with the DLLs from 3rd party (and MS)?
I have an AspnetMvc 4 project and see a DLLs named *Oauth* and DotnetOpenAuth*.
Now I'd like to get rid of unnecessary load and my project is anonymous so I thought it would be a good idea to delete said DLLs and references.
So I delete through Nuget
UnInstall-Package Microsoft.AspNet.WebPages.OAuth
But to no avail. I delete the files and update packages.config to realise something needs them. But how do I find out what? My stuff is not the culprit afaik.
Here you can follow this tutorial step by step to create a webform ( same you can do in MVC ) also codes are available in GitHub. Here is the link :
It looks like you pulled in the security portion of the mvc4 application. If you do not use the library(s) then you can discard them.
The main packages for MVC are
Microsoft.AspNet.Mvc
Microsoft.AspNet.Razor
Microsoft.AspNet.WebPages
Microsoft.Web.Infrastructure
I don't think the above packages will pull in the oauth portions.

ASP.NET: NuGet/NuPack: Configuring location package files are put in

Okay, so help me understand something here. I've got a new MVC solution and want to use NuGet to keep Modernizr up to date.
The problem is, NuGet puts the Modernizr scripts under ~/Scripts. This won't work--we've decided to put our JS in ~/js.
How do I modify the configuration of this package to tell NuGet that the Modernizr package should go in ~/Scripts or ~/Scripts/global instead?
I don't think you can do this - I don't think this is functionality of NuGet, but rather the location of the scripts inside the NuGet package. This could vary from one package to another :-(
This is currently not a feature of NuGet, but it was mentioned in discussion on the a NuGet forums including members of the NuGet team. I don't see any work item that has officially been created for this yet, unfortunately. I performed a quick search of the NuGet issues list for the word "location" and didn't see one out there for this. You might want to request it as a feature.

NuGet Project > Add Library Package Reference not appearing

I have installed NuGet.
When I try to go to Project > Add Library Package Reference
"Add Library Package Reference" is not under the project menu. If I try to install NuGet again it says it is already installed. My application is an MVC 3 application targeting .net 4.
How can I get this option to appear?
You might also run VS as Admin (Ctrl-Shift-Click) then uninstall NuGet from the package manager dialog. Then update to NuGet 1.1 from http://nuget.codeplex.com and see if that fixes it. ASP.NET MVC is not needed.
Is it possible that some of the extensions of your Visual Studio are causing NuGet to not show the menu or crash? You could try to disable/remove them and then install NuGet from here: http://nuget.codeplex.com/
Besides, there is also a PowerShell-based Package Manager Console. You could take a look on that in case everything fails.
Make sure you have the project selected and not the solution in the solution explorer.
As of May 2012, it's now called "Manage NuGet Packages".
Especially confusing because the screenshots in the NuGet Docs have not been updated.
https://stackoverflow.com/a/9844659/24267
Normally NuGet is installed with ASP.NET MVC 3 so it should appear automatically. Try removing the NuGet package that you have installed and reinstall ASP.NET MVC 3.
Had this same issue, just realized that if you're not on the project (i.e., you have the solution highlighted in solution explorer) that the option for the Add Library Package Reference won't show. Select the project and it's there.
Whoops: Didn't notice that was already mention.
I've just had a similar problem, after trying to install a package over dial-up, which timed out.
To fix it, I renamed the registry key (so that I could rename it back if it didn't work) HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\NuGet, then restarted visual studio and opened a project. The Add Library Package Reference now works and the registry key has been recreated.

Resources