dotnet-cli

dotnet publish command is not creating zip file package for asp.net core web application project

半城伤御伤魂 提交于 2019-11-29 14:00:17
I am trying to create a web deployment package for asp.net core web application. When I tried to publish the output as a package using VS2017, I got all the necessary files in "Publish" folder as well a zip file containing all those files in given location. However I want to have the same using command line. I am able to get "Publish" folder, but not a zip file. What am I doing wrong? Can someone correct my command? dotnet publish /p:target=package /p:WebPublishMethod=Package /p:LastUsedBuildConfiguration=Release /p:LastUsedPlatform="Any CPU" /p:LaunchSiteAfterPublish=True /p:ExcludeApp_Data

C# - F# Interop support in Visual Studio 2015 on .NET Core

感情迁移 提交于 2019-11-29 09:17:00
Note: here I talk about dotnet core and not full framework! For full framework there are plenty of docs on this, but this is dotnet core. I have an F# library created by dotnet new --lang F# And an ASP.NET Core RC2 C# application (created by File->New Project in VS). Now I use my F# library from C# (I guess a very common scenario…). The F# project is referenced in the project.json as any other .net library (by listing it under dependencies) Now all this compiles and works fine, which is great! The only problem is that VS does not seem to support it. There is no intellisense and lines, where I

Is .NET Core ready to run on Raspberry PI 3?

陌路散爱 提交于 2019-11-28 20:59:27
问题 I can find a lot of obsolete threads but a lot have been changed the last months. Is there currently any possibility to run .NET Core and/or ASP.NET Core on Raspberry with Raspbian (currently Jessie) without Mono? Or what do I need? I can find some dnvm samples, but I cannot find one tutorial which is up to date and uses the dotnet cli. I know Windows 10 IoT is planned for v1.1.0 but I can find nothing for ARM based CPUs. Also there is no Docker sample for ASP.NET Core on Raspbian... Even

Relationship between the dotnet cli and the new vs2017 msbuild

我是研究僧i 提交于 2019-11-28 16:10:24
With the move from project.json to the new csproj format introduced with VS2017, I'm struggling to understand the difference between the dotnet cli and the new msbuild and when to use one over the other. 1) To build a new csproj netstandard library from the command line, should I be calling the dotnet cli (for example dotnet restore dotnet build ) or use msbuild (for example msbuild ExampleNetstandard.sln ). 2) Also, my understanding is that there are two versions of msbuild , one built on the full framework and another targeting dotnet core . Is this correct? Should I always use the dotnet

dotnet publish command is not creating zip file package for asp.net core web application project

偶尔善良 提交于 2019-11-28 07:28:28
问题 I am trying to create a web deployment package for asp.net core web application. When I tried to publish the output as a package using VS2017, I got all the necessary files in "Publish" folder as well a zip file containing all those files in given location. However I want to have the same using command line. I am able to get "Publish" folder, but not a zip file. What am I doing wrong? Can someone correct my command? dotnet publish /p:target=package /p:WebPublishMethod=Package /p

C# - F# Interop support in Visual Studio 2015 on .NET Core

核能气质少年 提交于 2019-11-28 02:41:22
问题 Note: here I talk about dotnet core and not full framework! For full framework there are plenty of docs on this, but this is dotnet core. I have an F# library created by dotnet new --lang F# And an ASP.NET Core RC2 C# application (created by File->New Project in VS). Now I use my F# library from C# (I guess a very common scenario…). The F# project is referenced in the project.json as any other .net library (by listing it under dependencies) Now all this compiles and works fine, which is great

Writing custom Code generator for Dotnet Core

£可爱£侵袭症+ 提交于 2019-11-27 23:08:35
问题 I am trying to write a custom code generator for dotnet core, but had little success so far with the limited documentation around it. Poked around the CodeGeneration source code a bit, found out how to trigger the generators from command line and how it internally works. Since the generators available within dotnet core wouldn't suffice my needs I tried writing my own CodeGenerator, but doesn't seem to be able to invoke it through "dotnet aspnet-codegenerator" command. Below is my custom code

How to apply database code first migrations in an azure deployed application?

末鹿安然 提交于 2019-11-27 16:31:35
I just deployed an application into an azure App Service. My project does has migrations to be applied. But I was not able to apply them by using azure app command line dotnet ef database update D:\home\site\wwwroot> No executable found matching command "dotnet-ef" How can I apply them remotely? For dotnet-ef , I assumed that you are talking about Entity Framework Core. I have tried to run dotnet ef database update under D:\home\site\wwwroot of KUDU and Package Manager Console of VS, I could encounter the same issue as you mentioned. I found a similar issue No executable found matching command

The library hostpolicy.dll was not found

冷暖自知 提交于 2019-11-27 14:34:36
I have a simple .NET Core project (console app) that I'm trying to compile and run. dotnet build succeeds, but I get the following error when I do dotnet run : λ dotnet run Project RazorPrecompiler (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation. A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in [path]. My project.json looks like this: { "buildOptions": { "warningsAsErrors": true }, "dependencies": { "Microsoft.AspNetCore.Razor": "1.0.0", "Microsoft.NETCore.App": { "type": "platform", "version": "1.0.0" } }

dotnet publish doesn´t publish correct appsettings.{env.EnvironmentName}.json

杀马特。学长 韩版系。学妹 提交于 2019-11-27 01:05:54
When I issue the following command in the command line: dotnet publish -o "./../output" -c Release The dotnetcli publishes the project correctly. However, it does not copy the appsettings.Production.json file, only the appsettings.json . Why is this? I have googled around and read the official core docs, but haven't found how the correct environment appsettings.json is supposed to end up in the publish output. Should I copy appsettings.Production.json manually to the published folder? Set Update: For current (new) .csproj format the CopyToPublishDirectory attribute should be used. It