{"id":3374,"date":"2009-10-27T17:57:00","date_gmt":"2009-10-27T17:57:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2009\/10\/27\/new-silverlight-tooling-support-in-visual-studio-2010-beta-2\/"},"modified":"2009-10-27T17:57:00","modified_gmt":"2009-10-27T17:57:00","slug":"new-silverlight-tooling-support-in-visual-studio-2010-beta-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/new-silverlight-tooling-support-in-visual-studio-2010-beta-2\/","title":{"rendered":"New Silverlight Tooling Support in Visual Studio 2010 Beta 2"},"content":{"rendered":"<p>Visual Studio 2010 Beta 2 will bring full support for developing applications in Silverlight 3.&#160; There\u2019s a few things that have changed since VS2010 Beta 1, and we hope you enjoy the new beta release!<\/p>\n<h5>Silverlight 2 is no longer supported \u2013 long live Silverlight 3<\/h5>\n<p>Now that Silverlight 3 has released (including a GDR; the latest version is currently 3.0.40818), VS2010 has moved the minimum supported version to Silverlight 3.&#160; The new installation experience will include the latest Silverlight 3 developer runtime and Silverlight 3 GDR 2 SDK. <strong>If you already have the Silverlight 3 RTW version of the SDK installed, this component may fail during VS installation<\/strong>, but not to worry \u2013 it won\u2019t affect anything outside Silverlight.&#160; If this does occur, you can uninstall the RTW version of the Silverlight 3 SDK and then install the newer SDK manually (recommended).&#160; You can find the Silverlight 3 GDR 2 SDK at <a title=\"http:\/\/go.microsoft.com\/fwlink\/?LinkID=157102\" href=\"http:\/\/go.microsoft.com\/fwlink\/?LinkID=157102\">http:\/\/go.microsoft.com\/fwlink\/?LinkID=157102<\/a>.&#160; For more information about the setup error, see <a title=\"http:\/\/blogs.msdn.com\/amyd\/archive\/2009\/10\/21\/visual-studio-2010-and-silverlight-3-sdk.aspx\" href=\"http:\/\/blogs.msdn.com\/amyd\/archive\/2009\/10\/21\/visual-studio-2010-and-silverlight-3-sdk.aspx\">http:\/\/blogs.msdn.com\/amyd\/archive\/2009\/10\/21\/visual-studio-2010-and-silverlight-3-sdk.aspx<\/a>.<\/p>\n<p>The Silverlight 3 GDR 2 SDK has several bug fixes for VS2010 and Silverlight development in general.&#160; Some of the new features in VS2010 (such as IntelliSense improvements listed below) may not work without the updated SDK, but all VS2008 features will work correctly.<\/p>\n<h5>Silverlight designer is back \u2013 long live Silverlight designer<\/h5>\n<p>Back by popular demand is the XAML designer, removed from the Silverlight 3 Tools release for VS2008.&#160; This designer is better than ever, including for the first time an interactive design experience for Silverlight.&#160; Also new is support for the Properties tool window, to better allow you to customize your controls.<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/SL_designer_4.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"SL_designer\" border=\"0\" alt=\"SL_designer\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/SL_designer_thumb_1.jpg\" width=\"796\" height=\"595\" \/><\/a> <\/p>\n<h5>New option for OOB \u2013 long live Silverlight 3 Out-of-Browser<\/h5>\n<p>While almost all of our changes in VS2010 are under the hood, we\u2019ve added one additional option to the Silverlight Out-Of-Browser dialog.&#160; One setting not previously exposed was the option to hide the default installation context menu for your app (i.e. if you want to limit installation to actions inside your application).<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/sl_installMenu_4.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"sl_installMenu\" border=\"0\" alt=\"sl_installMenu\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/sl_installMenu_thumb_1.jpg\" width=\"520\" height=\"552\" \/><\/a> <\/p>\n<p>If you turn this off, users will no longer have the right-click install for OOB applications except where you provide it (i.e. via your own install button):<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/sl_installCM.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"sl_installCM\" border=\"0\" alt=\"sl_installCM\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/sl_installCM_thumb.jpg\" width=\"437\" height=\"65\" \/><\/a> <\/p>\n<p>(For reference, if you\u2019d like to turn this off in VS2008, you can modify the ShowInstallMenuItem attribute in OutOfBrowserSettings.xml under the project properties node.)<\/p>\n<h5>Improved Intellisense wire-up during development \u2013 Long live real-time IntelliSense<\/h5>\n<p>Something that has long been missing from Silverlight development is automatic and (near-)instant IntelliSense between XAML and code-behind.&#160; Now, once you\u2019ve created a control in markup, it should appear in IntelliSense immediately:<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/sl_intellisenseWireup.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"sl_intellisenseWireup\" border=\"0\" alt=\"sl_intellisenseWireup\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/sl_intellisenseWireup_thumb.jpg\" width=\"799\" height=\"574\" \/><\/a> <\/p>\n<p>This does require the Silverlight 3 GDR 2 SDK to work properly.&#160; See the note above regarding potential installation issues with the newer SDK.<\/p>\n<h5><\/h5>\n<h5>Note for Expression Blend users \u2013 warnings when opening VS2010 solutions\/projects<\/h5>\n<p>Unfortunately, Expression Blend 3 only supports .NET 3.5 and VS2008 project files and solutions, so VS2010 project files may present some difficulties.&#160; You may run into some of the following issues:<\/p>\n<ul>\n<li>There\u2019s a pop-up warning about opening the VS2010 solution.&#160; Blend will continue to work fine, so you can ignore this error.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/Blend_Dev10Solution.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"Blend_Dev10Solution\" border=\"0\" alt=\"Blend_Dev10Solution\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/Blend_Dev10Solution_thumb.jpg\" width=\"598\" height=\"155\" \/><\/a>&#160;<\/p>\n<ul>\n<li>Web Application projects targeting .NET 4.0 (VS2010 default) fail to load in Blend.&#160; It will also fail to build, which in turn will prevent you from running it from Blend.&#160; You can use VS2010\u2019s multi-targeting to re-target the web project to .NET 3.5 if you need it to open in Blend.&#160; <\/li>\n<\/ul>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/Blend_Dev10WAP.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"Blend_Dev10WAP\" border=\"0\" alt=\"Blend_Dev10WAP\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/Blend_Dev10WAP_thumb.jpg\" width=\"593\" height=\"168\" \/><\/a> <\/p>\n<ul>\n<li>VS2010 Website projects fail to build in Blend.&#160; This will also prevent it from running.&#160; This is caused by a change in VS2010 wherein the target framework version is stored in the web.config file:<\/li>\n<div id=\"codeSnippetWrapper\" class=\"csharpcode-wrapper\">\n<div id=\"codeSnippet\" class=\"csharpcode\">\n<div id=\"codeSnippetWrapper\">\n<div id=\"codeSnippet\">\n<pre><span style=\"color: #0000ff\">&lt;<\/span><span style=\"color: #800000\">compilation<\/span> <span style=\"color: #ff0000\">debug<\/span><span style=\"color: #0000ff\">=&quot;false&quot;<\/span> <span style=\"color: #ff0000\">targetFramework<\/span><span style=\"color: #0000ff\">=&quot;4.0&quot;<\/span> <span style=\"color: #0000ff\">\/&gt;<\/span> <\/pre>\n<p><!--CRLF--><\/div>\n<\/p><\/div>\n<p><!--CRLF--><\/div>\n<\/p><\/div>\n<\/ul>\n<blockquote>\n<p>If you remove this attribute, the website should work in Blend. <\/p>\n<\/blockquote>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/Blend_Dev10WSP.jpg\"><img decoding=\"async\" style=\"border-bottom: 0px;border-left: 0px;border-top: 0px;border-right: 0px\" title=\"Blend_Dev10WSP\" border=\"0\" alt=\"Blend_Dev10WSP\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2009\/10\/Blend_Dev10WSP_thumb.jpg\" width=\"671\" height=\"126\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Visual Studio 2010 Beta 2 will bring full support for developing applications in Silverlight 3.&#160; There\u2019s a few things that have changed since VS2010 Beta 1, and we hope you enjoy the new beta release! Silverlight 2 is no longer supported \u2013 long live Silverlight 3 Now that Silverlight 3 has released (including a GDR; [&hellip;]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[7349,7278,7323],"class_list":["post-3374","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-jamlew","tag-silverlight","tag-visual-studio-2010"],"acf":[],"blog_post_summary":"<p>Visual Studio 2010 Beta 2 will bring full support for developing applications in Silverlight 3.&#160; There\u2019s a few things that have changed since VS2010 Beta 1, and we hope you enjoy the new beta release! Silverlight 2 is no longer supported \u2013 long live Silverlight 3 Now that Silverlight 3 has released (including a GDR; [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/3374","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=3374"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/3374\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=3374"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=3374"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=3374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}