{"id":232105,"date":"2021-03-30T07:00:03","date_gmt":"2021-03-30T14:00:03","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=232105"},"modified":"2021-04-01T11:06:30","modified_gmt":"2021-04-01T18:06:30","slug":"angular-language-service-for-visual-studio-update","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/angular-language-service-for-visual-studio-update\/","title":{"rendered":"Angular Language Service for Visual Studio Update"},"content":{"rendered":"

Last August,\u00a0the\u00a0JavaScript\/TypeScript tools team\u00a0released\u00a0the\u00a0Angular Language Service for Visual Studio customers.\u00a0We wanted to appeal to the many ASP.NET\/ASP.NET Core users that\u00a0are\u00a0building their front-end projects with Angular. Though there was a lot of praise around this extension,\u00a0the experience was not so great for all\u00a0users. We want you to know we\u00a0heard\u00a0you\u00a0and we\u00a0have made\u00a0some\u00a0changes.\u00a0<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

Updates and Bug\u00a0Fixes\u00a0<\/span><\/strong><\/p>\n

We\u00a0constantly tracked issues in our\u00a0<\/span>Github<\/span><\/a> repository and monitored feedback from the Visual Studio Extension site to see what bugs needed to be prioritized and what features needed to be added. In this update we have tackled two major issues:<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

    \n
  1. A\u00a0System\u00a0Aggregate Exception\u00a0caused\u00a0by\u00a0the\u00a0extension<\/span><\/a><\/li>\n
  2. HTML Completions\u00a0not\u00a0working\u00a0properly<\/span><\/a>\u00a0<\/span><\/li>\n<\/ol>\n

    We also updated the extension to support the latest version of the language service (v11.2.8) and the latest version of TypeScript (v4.2.3)<\/span>\u00a0<\/span><\/p>\n

    An upcoming fix we are currently working on is being sure completions in project buffers are\u00a0handled properly with the extension. You can read\u00a0more\u00a0<\/span>here<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

     <\/p>\n

    Try\u00a0the\u00a0New Version\u00a0<\/span><\/strong>\u00a0<\/span><\/p>\n

    If you haven\u2019t tried the Angular Language Service extension and want to learn more about it, you can read more about it\u00a0<\/span>here<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

    Ready to try the new version now and\u00a0looking\u00a0for\u00a0the\u00a0extension download page? It can be\u00a0found\u00a0<\/span>here<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

    Please continue to submit all requests and bugs to our\u00a0<\/span>Github\u00a0repository<\/span><\/a>. You can also continue to leave feedback\u00a0in\u00a0the comments\u00a0of\u00a0the extension page as well.<\/span>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

    Last August,\u00a0the\u00a0JavaScript\/TypeScript tools team\u00a0released\u00a0the\u00a0Angular Language Service for Visual Studio customers.\u00a0We wanted to appeal to the many ASP.NET\/ASP.NET Core users that\u00a0are\u00a0building their front-end projects with Angular. Though there was a lot of praise around this extension,\u00a0the experience was not so great for all\u00a0users. We want you to know we\u00a0heard\u00a0you\u00a0and we\u00a0have made\u00a0some\u00a0changes.\u00a0\u00a0\u00a0 Updates and Bug\u00a0Fixes\u00a0 We\u00a0constantly tracked […]<\/p>\n","protected":false},"author":36368,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[],"class_list":["post-232105","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio"],"acf":[],"blog_post_summary":"

    Last August,\u00a0the\u00a0JavaScript\/TypeScript tools team\u00a0released\u00a0the\u00a0Angular Language Service for Visual Studio customers.\u00a0We wanted to appeal to the many ASP.NET\/ASP.NET Core users that\u00a0are\u00a0building their front-end projects with Angular. Though there was a lot of praise around this extension,\u00a0the experience was not so great for all\u00a0users. We want you to know we\u00a0heard\u00a0you\u00a0and we\u00a0have made\u00a0some\u00a0changes.\u00a0\u00a0\u00a0 Updates and Bug\u00a0Fixes\u00a0 We\u00a0constantly tracked […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/232105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/36368"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=232105"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/232105\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=232105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=232105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=232105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}