This solution works for me (Visual Studio 2017 and xUnit 2.2.0.3545). Try adding the below configuration in the App.Config file. (I don’t know why. It was just needed. If it doesn’t exist, just add a new one in your test project.) <?xml version=”1.0″ encoding=”utf-8″ ?> <configuration> <appSettings> <add key=”xunit.diagnosticMessages” value=”true”/> </appSettings> </configuration> The output information will be … Read more
Take a look at what EntityFramework does. They target 3 TFMs: net45, .NETPortable,Version=v4.5,Profile=Profile7, frameworkAssemblies and they have both csproj and xproj in the same folder. Basically, for each project you have two project files. However I cannot find a way to reference ClassLibrary-dnx from WindowsService.csproj. Unfortunately, that’s not possible, yet. You can only reference csproj … Read more
It looks like RealProxy won’t come to .NET Core/Standard. In the issue, a Microsoft developer suggests DispatchProxy as an alternative. Also, some existing AOP frameworks may support .NET Core already or in the future (as seen in the comments on the question). An alternative is the DispatchProxy, which has a wonderful example here: http://www.c-sharpcorner.com/article/aspect-oriented-programming-in-c-sharp-using-dispatchproxy/. If … Read more
So if you squint and look at the project.json, it’s basically a nuspec with a little bit of goop to describe what compilation options and sources are needed to build to project. Nuspecs today have 2 sections, frameworkAssemblies for “built in” stuff and dependencies for other nuget dependencies. It has the same meaning here. When … Read more
Answering your question in a different way: A library should target environments which SDK its requires. If you do not require a SDK use netstandard (or before .NET Core RC2 dotnet). dnxcore50 DNX SDK running on CoreCLR/CoreFx (deprecated, use netcoreapp1.0 instead). dnx451 DNX SDK running on .Net 4.5.1 (Desktop CLR / Full BCL and FCL) … Read more
This is a known issue. ASP.NET 5: On Windows 7 SP1, DNX SDK cannot be installed without Powershell 3.0. Symptoms When you create an ASP.NET 5 project, you receive the following error message: DNX SDK version ‘dnx-clr-win-x86.1.0.0-beta5’ failed to install. The solution will use DNX SDK version ‘dnx-clr-win-x86-1.0.0-beta5’ for this session Workaround To work around … Read more
To answer my own question: What helped, was Jed Grant’s comment and link to this GitHub discussion. I did the following in a terminal: source dnvm.sh dnvm upgrade -u And suddenly the “dnu” command was available so that I could run dnu restore As the installation instructions told me.
It should be in %userprofile%\.dnx\runtimes\<runtime name>\bin. If it is not on the path, run dnvm upgrade. If dnvm is not recognized, install it by following the instruction on the Home repo
As @axelheer mentioned IHostedService is the way to go in .NET Core 2.0 and above. I needed a lightweight like for like ASP.NET Core replacement for HostingEnvironment.QueueBackgroundWorkItem, so I wrote DalSoft.Hosting.BackgroundQueue which uses.NET Core’s 2.0 IHostedService. PM> Install-Package DalSoft.Hosting.BackgroundQueue In your ASP.NET Core Startup.cs: public void ConfigureServices(IServiceCollection services) { services.AddBackgroundQueue(onException:exception => { }); } To … Read more
If you want to use ASP.NET 2.x or 3.x you need to change it a bit. The watch tool is a global tool now and you don’t need to add it as a reference any longer The syntax is slightly different “Watch”: { “executablePath”: “dotnet.exe”, “workingDirectory”: “$(ProjectDir)”, “commandLineArgs”: “watch run”, “launchBrowser”: true, “launchUrl”: “http://localhost:5000/”, “environmentVariables”: … Read more