Running "bower-install-simple:dev" (bower-install-simple) task
Executing Bower (Command: install)
bower ENOGIT git is not installed or not in the PATH
Warning: Task "bower-install-simple:dev" failed. Use --force to continue.
Aborted due to warnings.
I've not tried running it with --force as my knowledge of GRUNT/BOWER/Node is nil. I've always just used Nuget for package management.
When I try to run the solution I get no build errors but I'm presented with an error page in my web browser:
A server error occured
This is most likely fur to an error during application startup
Some image that fails to display shows here
Did you know
{{installer.feeback}}
No errors exist in the umbraco log so I'm at a bit of a loss as to where to start resolving this as I suspect the latter error is caused by the former failed command.
To be honest, I actually tried that first before I found the link about how to build and run the source. Once it eventually built (the first time resulted in loads of CNC errors so I had to build each project individually) I got the same errors.
Next on my list is to try starting again with a clean clone and see what happens.
I started fresh with a clean clone of the dev-v7 branch. Once it cloned I built the solution. The first build failed due to nuget package restoration, but telling it to build a second time resulted in a successful build.
However, I still get the same issue when I run the site.
This is the web address that it tries to re-direct to:
So, some more information for you regrading this issue:
If I clone the repo via Visual Studio 2015 on a windows 10 machine it's worked no problem.
Yet I still cannot get it to work on Windows 7 with Visual Studio 2013.
Is there a pre-requisite that isn't documented anywhere?
There was a noticeable behavioural difference with Visual Studio 2015 I opened the solution file after the clone it went off on it's own and ran all the bower, grunt and NPM commands. Then when I built it, it already had all the nuget packages (or at least it seemed to). The build then completed with no problems and the site launched as I expected.
Could the latest project be dependant on VS2015 to build successfully?
However, for me this was just the start of the problem. Even though I installed NodeJs and Grunt, you also Bower installed.
How many package managers do we need?!
So, once that was installed I tried again.. still, same problem. Okay, so basically Visual Studio 2013 doesn't have built in support for all of these things.
I then proceeded to install all 3 of the packages.
Still I had some issues and had to re-register some Path variables.
Finally, things started to look promising.
Using Task Launcher (one of the plugins) I see all of the tasks in the source code and after telling it to run the Build-Dev task everything is now working!
Building the Core
Hi Guys,
So this might be a fairly noobish question but I'm interested in exploring the Umbraco Core with a look to possibly contributing moving forward.
So, my first task was to build the core.
I took a clone of the Github repository here: https://github.com/umbraco/Umbraco-CMS/
And follows the instructions here: http://umbraco.github.io/Belle/#/tutorials/Building
I'm running Visual Studio 2013 Update 4.
However, when I run the
command it all goes fine until it runs this:
I've not tried running it with --force as my knowledge of GRUNT/BOWER/Node is nil. I've always just used Nuget for package management.
When I try to run the solution I get no build errors but I'm presented with an error page in my web browser:
No errors exist in the umbraco log so I'm at a bit of a loss as to where to start resolving this as I suspect the latter error is caused by the former failed command.
Any help would be appreciated.
Hi Nik,
i think you can just clone the solution from github and build/run it from visual Studio.
The belle building part is not necessary. It was just there before v7 to have a look at the new ui.
Regards David
Hi David,
To be honest, I actually tried that first before I found the link about how to build and run the source. Once it eventually built (the first time resulted in loads of CNC errors so I had to build each project individually) I got the same errors.
Next on my list is to try starting again with a clean clone and see what happens.
Maybe check which branch you used. I think the dev-v7 is up-to-date.
Haven't cloned it for a while so don't know if there are some errors in the branch.
Hi David,
I started fresh with a clean clone of the dev-v7 branch. Once it cloned I built the solution. The first build failed due to nuget package restoration, but telling it to build a second time resulted in a successful build.
However, I still get the same issue when I run the site.
This is the web address that it tries to re-direct to:
So, some more information for you regrading this issue:
If I clone the repo via Visual Studio 2015 on a windows 10 machine it's worked no problem.
Yet I still cannot get it to work on Windows 7 with Visual Studio 2013.
Is there a pre-requisite that isn't documented anywhere?
There was a noticeable behavioural difference with Visual Studio 2015 I opened the solution file after the clone it went off on it's own and ran all the bower, grunt and NPM commands. Then when I built it, it already had all the nuget packages (or at least it seemed to). The build then completed with no problems and the site launched as I expected.
Could the latest project be dependant on VS2015 to build successfully?
I haven't heard about a VS2015 dependency.
But Umbraco 7.3 used MVC 5 and some Identity features. So maybe thats why it dies work out if the box with the new VS.
Thats the only thing i can imagine right now.
I'm going to try a different VS2013 machine tonight/tomorrow and see how that behaves. I'll let you know how I get on.
For those who happen to have the same issue it seems to be caused by various dependencies being required.
So, as I mentioned in my first post I had followed the instructions for running the source on the link http://umbraco.github.io/Belle/#/tutorials/Building
However, for me this was just the start of the problem. Even though I installed NodeJs and Grunt, you also Bower installed.
How many package managers do we need?!
So, once that was installed I tried again.. still, same problem. Okay, so basically Visual Studio 2013 doesn't have built in support for all of these things.
Next, I found this blog post by the very helpful Scott Hanselman http://www.hanselman.com/blog/IntroducingGulpGruntBowerAndNpmSupportForVisualStudio.aspx
I then proceeded to install all 3 of the packages.
Still I had some issues and had to re-register some Path variables.
Finally, things started to look promising.
Using Task Launcher (one of the plugins) I see all of the tasks in the source code and after telling it to run the Build-Dev task everything is now working!
is working on a reply...