You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into a problem when creating a NuGet package out of my project with NuGet pack and supplying it with my csproj file.
My package references the bootstrap.chosen package which contains (among other things) two images: chosen-sprite.png and [email protected]. When calling NuGet pack with my project the chosen-sprite.png file is correctly detected as not having changed and is therefore not included in the created NuGet package.
However, the [email protected] apparently is detected as having changed (although it surely hasn't, I even tried copying the file again directly from the bootstrap.chosen package without success) and is therefore wrongly included in the NuGet package. Additionally the file is not included as [email protected], but as chosen-sprite%25402x.png, so it looks like the file name is also being URL-encoded twice (@ => %40 => %2540).
Oh btw: I used NuGet.exe in version 3.3 to create my NuGet package.
The text was updated successfully, but these errors were encountered:
I ran into a problem when creating a NuGet package out of my project with
NuGet pack
and supplying it with my csproj file.My package references the
bootstrap.chosen
package which contains (among other things) two images:chosen-sprite.png
and[email protected]
. When callingNuGet pack
with my project thechosen-sprite.png
file is correctly detected as not having changed and is therefore not included in the created NuGet package.However, the
[email protected]
apparently is detected as having changed (although it surely hasn't, I even tried copying the file again directly from thebootstrap.chosen
package without success) and is therefore wrongly included in the NuGet package. Additionally the file is not included as[email protected]
, but aschosen-sprite%25402x.png
, so it looks like the file name is also being URL-encoded twice (@
=>%40
=>%2540
).Oh btw: I used NuGet.exe in version 3.3 to create my NuGet package.
The text was updated successfully, but these errors were encountered: