You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Hi, I have a Controller/Action which renders a view in an Angular2 template syntax, available on url /angular-templates/navmenu-top. Typing this url in a browser, renders out html, so I know it works.
When I set the templateUrl in a @Component attribute to /angular-templates/navmenu-top, I get this error:
./ClientApp/app/components/navmenu/navmenu-top.component.ts
Module not found: Error: Can't resolve './/angular-templates/navmenu-top' in 'C:\Projects\...ClientApp\app\components\navmenu'
@ ./ClientApp/app/components/navmenu/navmenu-top.component.ts 21:18-55
@ ./ClientApp/app/app.module.ts
@ ./ClientApp/boot-client.ts
@ multi event-source-polyfill webpack-hot-middleware/client?path=%2F__webpack_hmr ./ClientApp/boot-client.ts
Do I need to change any webpack config, add any loader?
Thank you.
The text was updated successfully, but these errors were encountered:
@ADefWebserver yes, if I change the templateUrl totemplate: require("./navmenu-top.component.html") it works, the "navmenu-top.component.html" file is in the same folder as "navmenu-top.component.ts"
Where the /angular-templates/navmenu-top is an url to a Controller/Action, which renders the Angular2 HTML template.
skorunka
changed the title
How to user prerendered template by Asp.Net MVC Core razor engine as Angular2 template
How to use prerendered templates by Asp.Net MVC Core Razor Engine as Angular2 template
Apr 3, 2017
Hi, I have a Controller/Action which renders a view in an Angular2 template syntax, available on url
/angular-templates/navmenu-top
. Typing this url in a browser, renders out html, so I know it works.When I set the
templateUrl
in a@Component
attribute to/angular-templates/navmenu-top
, I get this error:The text was updated successfully, but these errors were encountered: