1

Closed

NuGet can't be built when there is a space in path

description

Got the error below while building

Please specify a nuspec or project file to use.
J:\Michael Sync\NuGet-Myfork\Build\Build.proj(191,9): error MSB3073: The command ""J:\Michael Sync\NuGet-Myfork\Build..\bin\NuGet\Console\NuGet.exe" pack -oJ:\Michael Sync\NuGet-Myfork\Build..\bin\NuGet\Server -Build -p Configuration=Release -Symbols -exclude *\NuGet.Core." exited with code 1.

According to Haccked, it happened because there is a space in path (e.g. j:\Michael Sync\ )

Please read more details in this discussion.
http://nuget.codeplex.com/discussions/273835
Closed May 8, 2012 at 6:01 PM by CodePlexAdmin
Bulk resetting Issues that were moved to Fixed from Closed due to CodePlex bug.

comments

aldion wrote Oct 10, 2011 at 9:49 PM

let's fix this for 1.7 if it's not already fixed

michaelsync wrote Oct 12, 2011 at 8:57 AM

Hello,

Could you please give me some answers for this? Feel free to let me know if you are not clear anything on my post.
http://nuget.codeplex.com/discussions/274190

dotnetjunky wrote Oct 28, 2011 at 1:31 PM

I don't think this is the case because on my machine I have quote in my path and yet I can still build without problem. Notice that we quote the command path properly.

dotnetjunky wrote Oct 31, 2011 at 10:14 PM

no repro

michaelsync wrote Nov 1, 2011 at 11:49 AM

Did you run build.cmd? Would you like to create a folder called "Michael Sync" under C: and put nuget code and call build.cmd to see whether you can build it or not? I'm not sure whether someone has fixed it or not. You can also try the code from my fork? I didn't submit any of my changes yet.

dotnetjunky wrote Nov 1, 2011 at 5:53 PM

yes, I ran build.cmd from a repository "e:\nu pack" on my machine. It builds just fine.

dotnetjunky wrote Nov 1, 2011 at 6:00 PM

Oops, now I see the error. It happens on a brand new repository, not an existing one. I was just renaming my existing repo earlier, hence I didn't see it. When I cloned a brand new one, i saw the error.

It's an easy fix.

dotnetjunky wrote Nov 1, 2011 at 6:01 PM

Fixed in changeset 9d495fcd808d

pranavkm wrote May 4, 2012 at 12:28 AM

Fixed in changeset abab4f11efa1