-
Notifications
You must be signed in to change notification settings - Fork 224
dnu pack fails when project.json is readonly. #1612
Comments
@victorhurdugaci Why is the InstallBuilder doing anything with the |
@victorhurdugaci , can you have a look? |
This is a simple fix. a One liner actually. |
I can fix it if @victorhurdugaci is working on something else. I'd suggest waiting on @troydai's change though. |
I can fix it too, I have time for this :) |
Great! |
|
That file moved into the package manager and there should be a new one from @troydai 's change in the runtime |
Hi, I am getting the exact same error and stack trace. My problem is trying to run an automated build on a TFS build agent. It copies the file to ...\Release\app\project.json and sets it to read-only. After that the build fails with the same stack trace you are showing at the top of this thread. I have not been able to run a build. TFS 2013 update 4 build controller and agent. Please update. |
@Darkonekt , what DNX version do you use? |
when I look in the .dnx folder for my user I see 1.0.0-beta-4 for all four folders under runtime. |
Unfortunately, the fix is only in beta5. The only solution is to update to the latest bits. Sorry for the inconvenience. |
How can I do that? I don't see the beta5 available as a nuget. Please advice how to do the update. This is the only thing preventing me from running an automated build. Thank you. |
I am probably abusing your time. But let me know or point me in the right direction on how to update my DNX installation to latest beta. This is very urgent to me. |
|
nice thanks I will try it |
ok I upgraded to version using dnvm install and passing "latest". which installed version beta4-11566 |
Nope, that didn't bring the latest dev bits. It should be Did you run From here:
|
My dnvm power shell script under C:\Program Files\Microsoft DNX\Dnvm DOES NOT contain a -u or -unstable switch. This is the function function dnvm-upgrade {
} As you can see there is no such switch any ides? |
Ok, no worries. We can fix that :) Edit the PATH environment variable and remove
Once you are done with that, you should get a new Dnvm in |
I think I had to remove dnvm* from |
When running dnu pack on a project where the project.json is a read-only file, the following exception and callstack is generated. This impacts SCC (TFS) scenarios where the project.json is not checked out.
The text was updated successfully, but these errors were encountered: