The routes "/" and "/admin" are relative to the URL serving your angular app. So if your app is at "http://www.blah.com/Office/Index/73/";, then your dashboard would be at "http://www.blah.com/Office/Index/73/#/"; and your admin screen would be "http://www.blah.com/Office/Index/73/#/admin";. Your routes can stay as-is. As far as getting the "73" value into your angular app there are a few ways to do it. I'm not a .NET developer but I think whatever page or script is building the "http://www.blah.com/Office/Index/73"; page could inject the "73" as a value into your page, something like:
<script>var office_id=73;</script> On Tuesday, January 27, 2015 at 6:41:22 AM UTC-6, Brian Power wrote: > > Hi Guys, > > I read the other threads on this,but I'm still confused. > > We are building a web site with .net mvc. We have one complex entity, lets > say it an "Office". An office has staff, resources, budgets etc. A user > can have many offices to manage. We have other areas of the system already > built with just .Net. I have a .net view with a list of offices. When the > user clicks on one they're sent to the spa for that Office. The request > goes to a .net controller called OfficeController. The Index method takes > an Id. I want its view to be an Angular spa. > > My route to the spa is http://www.blah.com/Office/ > <http://www.blah.com/Office/?officeid=52>Index/73/#!/ > > My angular stuff is in a folder called 'app' at the root of the website. > Within the spa I have links to other views of the spa. I want it to have > routes like this. > > http://www.blah.com/Office/52/staff > <http://www.blah.com/Office/?officeid=52/staff> > http://www.blah.com/Office/52/budgets > <http://www.blah.com/Office/?officeid=52/budgets> > > I'm using John Papa's HotTowel demo as a starting point for my spa. In his > routing config. He has this... > > return [ > { > url: '/', > config: { > templateUrl: 'app/dashboard/dashboard.html', > title: 'dashboard', > settings: { > nav: 1, > content: '<i class="fa fa-dashboard"></i> Dashboard' > } > } > }, { > url: '/admin', > config: { > title: 'admin', > templateUrl: app/admin/admin.html', > settings: { > nav: 2, > content: '<i class="fa fa-lock"></i> Admin' > } > } > } > ]; > > > > When I can access these views via the the browser with > http://www.blah.com/Office/ > <http://www.blah.com/Office/?officeid=52>Index/73/#!/ and > http://www.blah.com/Office/ > <http://www.blah.com/Office/?officeid=52>Index/73/#!/Admin . Do I need to > "pass in" something like "Office/ > <http://www.blah.com/Office/?officeid=52>Index/73/#!/" to angular and build > dynamic routes? > > > > Thanks for reading > > Brian > > > > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
