Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Migrate creates csproj based off of outputName
See original GitHub issueMigrating a project.json with a buildOption outputName chooses to create the new csproj with the outputName instead of the original project name.
RazorTooling in ASP.NET is a great example of this. Migrate ends up creating dotnet-razor-tooling.csproj instead of Microsoft.AspNetCore.Razor.Tools.csproj.
/cc @livarcocc
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How to change the output name of an executable built by ...
Open the Project Properties in Visual Studio (right click on project in Solution Explorer and select "Properties" from popup menu) ...
Read more >Project.json to MSBuild conversion guide
"The SDK will automatically create build constants based on your framework. Here is how they convert from TargetFramework to a constant: https ...
Read more >dotnet migrate does not migrate outputName · Issue #7022
We are going to add the PackageId set to the current folder name to the csproj if the OutputName is different than the...
Read more >Upgrading an existing .NET project files to the lean new ...
Great a new project file with something like "dotnet new classlib" and then manually get your projects building from the top (most common ......
Read more >Common MSBuild Project Properties
Creates a Windows-based program. For C# and Visual Basic, this property is equivalent to the /target switch. The output type can be ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This should be fixed with https://github.com/dotnet/cli/pull/4536
Woohoo! Awesome, glad we’re taking this approach. Makes a lot more sense in my opinion 😄