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 has been archived by the owner on May 8, 2024. It is now read-only.
When installing TypeScript definitions to a ASP.NET 5 project, they will be installed in the /packages folder. For example for Angular this would look like: '\packages\angularjs.TypeScript.DefinitelyTyped'. At the moment I would have to manually copy these files to (for example) 'Scripts/typings', so that I can reference to these Typing in my JavaScript.
Please also see this stackoverflow post with more details:
This sounds less than idea. For now, I'm not sure how to resolve this issue for you because (unless I'm missing something) NuGet doesn't support the ability to re-map destination of output.
Until we find a better resolution, I'd recommend looking into using TSD.
If you or anyone has any thoughts or work-arounds on how to possibly resolve this issue, any clues here would be helpful...
I'm running into the same issue (also using project.json but in my case in conjunction with the old skool .csproj files)
The NuGet package needs to support the new project.json file format, and it looks that here it is explained how to do that: http://blog.nuget.org/20160126/nuget-contentFiles-demystified.html
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
When installing TypeScript definitions to a ASP.NET 5 project, they will be installed in the /packages folder. For example for Angular this would look like: '\packages\angularjs.TypeScript.DefinitelyTyped'. At the moment I would have to manually copy these files to (for example) 'Scripts/typings', so that I can reference to these Typing in my JavaScript.
Please also see this stackoverflow post with more details:
http://stackoverflow.com/questions/29801548/how-do-i-access-typescript-definitions-in-asp-net-5-with-the-nuget-package-manag/29801733?noredirect=1#comment47810762_29801733
The text was updated successfully, but these errors were encountered: