Changes to the web and JSON editor APIs in Visual Studio 2019

Changes to the web and JSON editor APIs in Visual Studio 2019

<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/02/changes-to-the-web-and-json-editor-apis-in-visual-studio-2019.jpg" width="150" height="150" title="" alt="" /></div><div><div class="row justify-content-center">
<div class="col-md-2">
<div><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/02/changes-to-the-web-and-json-editor-apis-in-visual-studio-2019.jpg" width="58" height="58" alt="Andrew B. Hall [MSFT]" class="avatar avatar-58 wp-user-avatar wp-user-avatar-58 alignnone photo" /></p>
<p>Andrew</p>
</div>
</div>
</div>
<div class="entry-meta">
<p>February 6th, 2019</p>
<p> &lt;!–<span class="posted-on">Posted on <a href="https://devblogs.microsoft.com/aspnet/changes-to-the-web-and-json-editor-apis-in-visual-studio-2019/" rel="bookmark"><time class="entry-date published" datetime="2019-02-06T09:00:45+00:00">February 6, 2019</time><time class="updated" datetime="2019-02-18T16:43:39+00:00"> (February 18, 2019) </time></a></span><span class="byline"> by <span class="author vcard"><a class="url fn n" href="https://devblogs.microsoft.com/aspnet/author/andrew-hall-msft/">Andrew B. Hall [MSFT]</a></span></span>–&gt; </div>
<p><!-- .entry-meta --> </p>
<p>In <a href="https://visualstudio.microsoft.com/vs/preview/">Visual Studio 2019 Preview 2</a>, The Web Tools team made some changes to improve extensibility features for extension developers. To standardize interfaces, the CSS, HTML, JSON and CSHTML editors renamed their assemblies as per the following table:</p>
<table>
<tbody>
<tr>
<td width="312"><strong>Old</strong></td>
<td width="312"><strong>New</strong></td>
</tr>
<tr>
<td width="312">Microsoft.CSS.Core</td>
<td width="312">Microsoft.WebTools.Languages.Css</td>
</tr>
<tr>
<td width="312">Microsoft.CSS.Editor</td>
<td width="312">Microsoft.WebTools.Languages.Css.Editor</td>
</tr>
<tr>
<td width="312">Microsoft.Html.Core</td>
<td width="312">Microsoft.WebTools.Languages.Html</td>
</tr>
<tr>
<td width="312">Microsoft.Html.Editor</td>
<td width="312">Microsoft.WebTools.Languages.Html.Editor</td>
</tr>
<tr>
<td width="312">Microsoft.VisualStudio.Html.Package</td>
<td width="312">Microsoft.WebTools.Languages.Html.VS</td>
</tr>
<tr>
<td width="312">Microsoft.JSON.Core</td>
<td width="312">Microsoft.WebTools.Languages.Json</td>
</tr>
<tr>
<td width="312">Microsoft.JSON.Editor</td>
<td width="312">Microsoft.WebTools.Languages.Json.Editor</td>
</tr>
<tr>
<td width="312">Microsoft.VisualStudio.JSON.Package</td>
<td width="312">Microsoft.WebTools.Languages.Json.VS</td>
</tr>
<tr>
<td width="312">Microsoft.VisualStudio.Web.Extensions</td>
<td width="312">Microsoft.WebTools.Languages.Extensions</td>
</tr>
<tr>
<td width="312">Microsoft.Web.Core</td>
<td width="312">Microsoft.WebTools.Languages.Shared</td>
</tr>
<tr>
<td width="312">Microsoft.Web.Editor</td>
<td width="312">Microsoft.WebTools.Languages.Shared.Editor</td>
</tr>
</tbody>
</table>
<p>To avoid potential parse issues, the JSON parse tree changed behavior. When you call JsonParserService.GetTreeAsync, you now get a snapshot of the JSON parse tree. As an extension developer, you can now request and maintain snapshots of the JSON parse tree.</p>
<div class="authorinfoarea">
<div><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/02/changes-to-the-web-and-json-editor-apis-in-visual-studio-2019.jpg" width="96" height="96" alt="Andrew B. Hall [MSFT]" class="avatar avatar-96 wp-user-avatar wp-user-avatar-96 alignnone photo" /></div>
</p></div>
</div>