dynamic routing in angular js and asp.net mvc

Question

1.00/5 (1 vote)

See more:

Hi all,

I am very new to angularjs. For learning purposes I wrote a sample application that will render a partial page inside main page. For this I have used angularjs dynamic routing inside asp.net MVC project. Also I have hosted the website I created because I have used $location.

The problem I am facing is that When I try to click on the link "Client Information", i get the following error:

Error: [$compile:tpload] http://errors.angularjs.org/1.3.0/$compile/tpload?p0=ClientInfo
as seen in the F12-> Console

I had raised this in discussion forum in codeproject. But none replied. So thought of asking here.

Link for the question I asked in discussion forum is:

http://www.codeproject.com/Forums/12076/ASP-NET.aspx[^]

subject of the post is "angular js and asp.net mvc"

Posted 21-Oct-15 4:10am

Arjun Mourya

Add a Solution

Comments

Richard Deeming 21-Oct-15 10:34am

REPOST
As you mentioned, you have already posted this question in the ASP.NET forum:
http://www.codeproject.com/Messages/5144507/angular-js-and-asp-net-mvc.aspx[^]

You haven't had a response because nobody who has seen your question has an answer.

Reposting the same question is not going to change that.

Sreekanth Mothukuru 23-Oct-15 4:34am

Seems like you are not handling GotoClientInfo() or GotoFacilityInfo() methods in your controller. Try this.. instead of using ng-click="GotoClientInfo()" href="javascript:void(0);" just try to redirect to the router you created like href="#ClientInfo" or href="#FacilityDetails"

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)