When building the Umbraco source code with the build.bat file like recommended I get the errors shown in the picture below. It seems like the build script is looking for a file in c:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications\. I do have the necessary file but it's located in c:\Program (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications\. Where and how do I update the <Import> declaration?
I'd like to push for making this fix to next release. I can't quite get it to work so I can't make a pull request for it. http://issues.umbraco.org/issue/U4-3571
I understand the issue but it's currently low priority, the next release is Thursday and we're all very busy preparing for CodeGarden. It'll either have to wait until for a future release or if you can make a pull request for it after all we MIGHT be able to squeeze it in. But if you're going the PR route then I would urge you to make it fast, as I said we're currently all super busy so we might not have time to review and think about implications of changing this.
Building umbraco source on VS 2013
When building the Umbraco source code with the build.bat file like recommended I get the errors shown in the picture below. It seems like the build script is looking for a file in c:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications\. I do have the necessary file but it's located in c:\Program (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications\. Where and how do I update the <Import> declaration?
Thanks,
Daniel
Get the one from the 12.0 folder and put it in the folder that the build is looking for. I have this on my todo list to fix.
Thank you Sebastiaan. Now it built successfully.
I'd like to push for making this fix to next release. I can't quite get it to work so I can't make a pull request for it.
http://issues.umbraco.org/issue/U4-3571
Thanks,
Daniel
I understand the issue but it's currently low priority, the next release is Thursday and we're all very busy preparing for CodeGarden. It'll either have to wait until for a future release or if you can make a pull request for it after all we MIGHT be able to squeeze it in. But if you're going the PR route then I would urge you to make it fast, as I said we're currently all super busy so we might not have time to review and think about implications of changing this.
is working on a reply...