dotnet pack – Produces a NuGet package of your code. That is the key difference – this will enable to publish to http://nuget.org, or to a nuget server that can be pulled down by other developers, or even for use with Octopus Deploy. dotnet publish – Produces a .NET framework-dependent or self-contained application. Keyword is … Read more
This is the new way since mid 2018 You have to install dotnet-aspnet-codegenerator. This is now done globally and not through a Nuget package: PowerShell: dotnet tool install –global dotnet-aspnet-codegenerator Then this is how you create a REST-Controller from an existing EF Model in PowerShell: dotnet-aspnet-codegenerator -p “C:\MyProject\MyProject.csproj” controller -name MyDemoModelController -api -m My.Namespace.Models.MyDemoModel -dc … Read more
Also ensure that “C:\Program Files\dotnet” is part of the “path” system environment variable. After uninstalling previous SDK versions, it had disappeared from mine.
I found another solution on Scott Hanselman’s blog: https://www.hanselman.com/blog/CAndNETCoreScriptingWithTheDotnetscriptGlobalTool.aspx It relies on a .NET CLI tool called dotnet-script, you can find its repository below: https://github.com/filipw/dotnet-script To use, it, first install it using dotnet tool install -g dotnet-script Then you can run dotnet script and use it as a REPL or run dotnet script file.csx to … Read more
I’m using .Net 6 with NUnit on macOS. Setting the verbosity level for dotnet test does not print a list of all executed tests (successful or otherwise). What does print such a list is setting the logger verbosity like this: dotnet test -l “console;verbosity=normal”
According to the Microsoft document, the SDK uses the latest installed version and this is an expected behavior: The .NET CLI must choose an SDK version for every dotnet command. It uses the latest SDK installed on the machine by default, even if the project targets an earlier version of the .NET runtime. So, it … Read more
Not that I know of (I was also researching that topic) but I found helpful extension for VS code called C# Extensions by jchannon, which helps you create classes and interfaces with correct namespace by right-clicking the folder in VS code explorer and selecting to create C# class or C# interface.
At the moment, this is not possible with dotnet run. dotnet run does call msbuild targets to do a restore and build but queries the actually program and arguments to run from a new static evaluation, which means that even if you add custom build logic to a solution (=> the “project” being built), you … Read more
sometimes you need to change the current directory in console/terminal eg: PM> cd E:\Projects\CrossTest\ PM> dotnet ef migrations add InitialMigration and Align your package versions. Either use preview1 packages or preview2. Mix of those are not supported.
ASPNETCORE_ENVIRONMENT is an environment variable (and AFAIK) not a switch to the dotnet cli. So what you would do is set it prior to using the tool: rem Windows C:\> set ASPNETCORE_ENVIRONMENT=Development C:\> dotnet … rem Unix $ export ASPNETCORE_ENVIRONMENT=Development $ dotnet …