Changing the name of the output assembly and package using dnx/.net core

Question

I have a project which exists in a directory named Oracle and I would like the artifacts created to be called MyCompany.MyApp.Oracle instead of Oracle, what are my options for changing the output assembly name and nuget package name outside of changing the name of the directory?

I currently have a MyCompany.MyApp.Oracle.xproj next to my project.json file
I've also tried setting <AssemblyName>MyCompany.MyApp.Oracle</AssemblyName> in the xproj file but that didn't work
I've also tried setting {"id":"MyCompany.MyApp.Oracle"} in project.json and still no luck

Please note that things are different now with csproj based solutions. — Damian, Apr 03 '17 at 15:25

score 26 · Accepted Answer · answered Jun 29 '16 at 02:34

26

Based on comment of @Victor Hurdugaci

"buildOptions": {
    "outputName": "Some.Specific.Assembly.Name"
},

You need to put it inside project.json file. It will produce output with name: Some.Specific.Assembly.Name.dll

answered Jun 29 '16 at 02:34

Maxim

13,029
6
30
45

2

Please be careful Visual Studio still contains some bugs. So custom output name will breaks MVC application startup and discovering tests in Test Explorer. – Maxim Jul 27 '16 at 23:00

score 20 · Answer 2 · answered Apr 09 '17 at 11:22

From .NET Core 1.1 on, which uses csproj instead of package.json, you should use the <AssemblyName> configuration.

Example of x.csproj:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <AssemblyName>Name your assembly here</AssemblyName>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>

</Project>

Victor Hurdugaci · Answer 3 · 2016-09-02T05:39:45.273

7

Later edit: this answer was applicable to the pre-dotnet releases (dnx). Now it's possible to change the package name.

Old answer: The only way to change the package name is by changing the folder name.

edited Sep 02 '16 at 05:39

answered Oct 07 '15 at 16:35

Victor Hurdugaci

28,177
5
87
103

I upvoted, but going to keep this open in case alternatives come in. – Damian Oct 07 '15 at 19:01
Nope, there are no alternatives. Source: I work on the team that builds dnx – Victor Hurdugaci Oct 07 '15 at 22:32
1

I noticed that. Well here is to hoping this changes. – Damian Oct 07 '15 at 23:48
1

really hope this changes. – Ciel Feb 26 '16 at 10:31
@VictorHurdugaci Is there an option with dotnet cli? – Zygimantas May 19 '16 at 13:03
5

In the CLI you can now change the assembly name. So, the package name is still the folder name but you can specify a new assembly name like here: https://github.com/aspnet/dotnet-watch/blob/63a9d64394717f9876e307ccdc67c23ac49a16c7/src/Microsoft.DotNet.Watcher.Tools/project.json#L4 – Victor Hurdugaci May 19 '16 at 16:15

Changing the name of the output assembly and package using dnx/.net core

3 Answers3

Linked