Casing behavior between KPM and KRE is different

[kirthik]

Here is my project.json

{
    "dependencies": {
        "Xunit.KRunner": "1.0.0-*",
        "Microsoft.AspNet.Server.IIS": "1.0.0-alpha3",
        "Microsoft.Aspnet.SignalR.Client": "2.1.1"
    },
    "commands": {
        "test": "Xunit.KRunner"
    },
    "frameworks" : {
        "net451" : { }
      }
}

I have MyClass.cs which has a test. It calls HubConnection class from signalr client

      [Fact]
      public void MyTest()
      {
          HubConnection c = new HubConnection("www.bing.com");
      }

When I run k test from command line, I see compilation exception

Microsoft.Framework.Runtime.CompilationException: E:\E2EApps\WebApplication3\WebApplication3\MyClass.cs(14,13): error CS0246: The type or namespace name 'HubConnection' could not be found (are you missing a using directive or an assembly reference?)
E:\E2EApps\WebApplication3\WebApplication3\MyClass.cs(14,35): error CS0246: The type or namespace name 'HubConnection' could not be found (are you missing a using directive or an assembly reference?)

I see the package in .kpm folder

[glennc]

The problem here is that the n in AspNet is lowercase in the project.json but not in the NuSpec. If you change the package name to Microsoft.AspNet.SignalR.Client in the project.json it will work.

We need to solve this problem with inconsistent casing rules.

I'm going to update the title of this to reflect the problem.

[glennc]

We think that we should be case sensitive, and so in this case restore should've failed.

We should be able to give an error message that tells the user that the case of the package Id is different to what was typed in the project.json and let people fix it. or at least that it could be different and show the two strings.

[desdesdes]

If names are case sensitive you might run into some .net and mono inconsistencies. System.Configuration.dll is named System.configuration.dll on windows and System.Configuration.dll on mono. So on windows the exact name should be System.configuration, but that would fail on mono. On mono the name should be System.Configuration. I currently use System.Configuration because windows is not case sensitive and mono on *nix is, but that would stop working if you decide to check casing.