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.

sourceName not replaced in Folder/File names in 2.0-preview2

See original GitHub issue

When switching from dotnet SDK 1.4 to dotnet SDK 2.0 preview 2 I noticed a change in how dotnet templating works and I’d like to know if that’s expected (basically an intentional breaking change) or a bug.

With 1.4 if sourceName was present in any folder or file name it would be replaced. SDK 2.0 preview 2 does not perform replacement in folder/file names.

For example, if the template.json contained sourceName: "HelloWorld" and following folder structure

└───HelloWorld
    │   dirs.proj
    │   HelloWorld.sln
    │   HelloWorld.v3.ncrunchsolution
    │
    ├───HelloWorld
    │       Hello.cs
    │       HelloWorld.csproj
    │       HelloWorld.v3.ncrunchproject
    │       Initializer.cs
    │
    ├───HelloWorld.Exports
    │       HelloWorld.Exports.csproj
    │       HelloWorld.Exports.v3.ncrunchproject
    │       IHello.cs
    │
    ├───HelloWorld.Extensions
    │       HelloExtensions.cs
    │       HelloWorld.Extensions.csproj
    │       HelloWorld.Extensions.v3.ncrunchproject
    │
    └───HelloWorld.UnitTests
            HelloWorld.UnitTests.csproj
            HelloWorld.UnitTests.v3.ncrunchproject
            HelloWorldTest.cs

after running dotnet new lib -n MyNewLibrary with SDK 1.4 I get following template created:

└───MyNewLibrary
    │   dirs.proj
    │   MyNewLibrary.sln
    │   MyNewLibrary.v3.ncrunchsolution
    │
    ├───MyNewLibrary
    │       Hello.cs
    │       Initializer.cs
    │       MyNewLibrary.csproj
    │       MyNewLibrary.v3.ncrunchproject
    │
    ├───MyNewLibrary.Exports
    │       IHello.cs
    │       MyNewLibrary.Exports.csproj
    │       MyNewLibrary.Exports.v3.ncrunchproject
    │
    ├───MyNewLibrary.Extensions
    │       HelloExtensions.cs
    │       MyNewLibrary.Extensions.csproj
    │       MyNewLibrary.Extensions.v3.ncrunchproject
    │
    └───MyNewLibrary.UnitTests
            MyNewLibrary.UnitTests.csproj
            MyNewLibrary.UnitTests.v3.ncrunchproject
            MyNewLibraryTest.cs

with the very same template and dotnet SDK 2.0 I’m getting following result:

├───HelloWorld
│   │   dirs.proj
│   │   HelloWorld.sln
│   │   HelloWorld.v3.ncrunchsolution
│   │
│   ├───HelloWorld
│   │       Hello.cs
│   │       HelloWorld.csproj
│   │       HelloWorld.v3.ncrunchproject
│   │       Initializer.cs
│   │
│   ├───HelloWorld.Exports
│   │       HelloWorld.Exports.csproj
│   │       HelloWorld.Exports.v3.ncrunchproject
│   │       IHello.cs
│   │
│   ├───HelloWorld.Extensions
│   │       HelloExtensions.cs
│   │       HelloWorld.Extensions.csproj
│   │       HelloWorld.Extensions.v3.ncrunchproject
│   │
│   └───HelloWorld.UnitTests
│           HelloWorld.UnitTests.csproj
│           HelloWorld.UnitTests.v3.ncrunchproject
│           HelloWorldTest.cs

cc: @rachit1503

Issue Analytics

State:
Created 6 years ago
Comments:13 (9 by maintainers)

Top GitHub Comments

1reaction

MarcinJuraszekcommented, Aug 3, 2017

The template is distributed in an internal NuGet feed, so I can’t really move them under ./src/libs. But the real workaround is to use 1.4 and not preview builds 😃

0reactions

seancpeterscommented, Aug 18, 2017

@MarcinJuraszek - the fix for this issue is available in the newest dotnet/cli release-2.0.0 daily build, it’s version 2.0.1-servicing-006933. You can download it here: https://github.com/dotnet/cli/tree/release/2.0.0

Please let us know if you’re still encountering problems.