Subscribe: BradleyB's WebLog
Added By: Feedage Forager Feedage Grade B rated
Language: English
beta visual  beta  build  silverlight tools  silverlight  studio beta  studio  tools beta  tools  visual studio  visual  web 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: BradleyB's WebLog

BradleyB's WebLog


New Elastic Cloud Services on IIS

Tue, 12 Apr 2011 04:41:00 GMT

I’ve just posted a new article on some recent innovations for cloud services on IIS.  Check out

Fixing Setup Errors Installing Silverlight Tools Beta 2

Wed, 18 Jun 2008 22:17:00 GMT

What's the problem?

There are two predominate issues that are preventing a successful installation of Silverlight Tools Beta 2.

  1. Silverlight_chainer.exe fails attempting to uninstall KB949325
  2. Mismatched binaries when both Visual Studio 2008 SP1 Beta  and Silverlight Tools Beta 2 are installed.

These two problems account for the vast majority of installation problems developers are running into.

What's the solution?

To help address these two specific problems I've created a .vbs script that attempts to detects and repairs both of these issues.

Download "" attached to this post.

Unzip "Silverlight_Tools_Fixup.vbs" from

Run the following:

  1. Silverlight_Tools_Fixup.vbs
  2. Silverlight_chainer.exe

So what happened?

When run Silverlight_Tools_Fixup.vbs will:

  1. Detect and uninstall KB949325
  2. Detect all advertised features in VS and repair them. (Advertised features result in mismatched binaries.)

    *Vista non-admin scenarios will require running the script from command prompt that was started using "Run as administrator".
    *You may also be prompted for original media when uninstalling KB949325.

Getting Help?

Be sure to check out the Silverlight 2 Beta 2 readme for known issues.

You can also get additional help from the "Installation and Setup" forum here:

Upgrading to Silverlight Tools Beta 2 and Visual Studio 2008 SP1 Beta

Mon, 09 Jun 2008 12:38:37 GMT

Silverlight 2 Beta 2 has just been released! Checkout  Silverlight Tools Beta 2 for Visual Studio 2008 now includes support for both: Visual Studio 2008 RTM (get a free 90 day trial version here) Visual Studio 2008 SP1 Beta Upgrading "the Easy way" [update]  Please read Fixing Setup Errors Installing Silverlight Tools Beta 2 Installing Microsoft Silverlight Tools Beta 2 is quick and easy following the steps below. Visual Studio 2008 RTM w/Silverlight Tools Beta 1 to Beta 2 If you simply want to upgrade your current Silverlight Tools Beta 1 installation: Install "Microsoft Silverlight Tools Beta 2 for Visual Studio 2008" Install "Expression Blend 2.5 Preview" note: if you later install Visual Studio 2008 SP1 Beta, you'll need to reinstall Silverlight Tools Beta 2 Visual Studio 2008 SP1 Beta to Silverlight Tools Beta 2 If you've already got Visual Studio 2008 SP1 Beta and now want to install Silverlight Tools Beta2: Install "Microsoft Silverlight Tools Beta 2 for Visual Studio 2008" Install "Expression Blend 2.5 Preview" Visual Studio 2008 RTM w/ Silverlight Tools Beta 1 to Visual Studio 2008 SP1 Beta & Silverlight Tools Beta 2 The recommended way to upgrade to both Silverlight Tools Beta 2 and Visual Studio 2008 SP1 Beta is: Uninstall "Microsoft Silverlight Tools Beta 1 for Visual Studio 2008" Uninstall KB949325 (in Add/Remove Programs select "view installed updates") Install "Microsoft Visual Studio 2008 Service Pack 1 Beta" Install "Microsoft Silverlight Tools Beta 2 for Visual Studio 2008" Install "Expression Blend 2.5 Preview" Following the above steps will ensure a smooth upgrade to both Visual Studio 2008 SP1 Beta and Silverlight Tools Beta 2. Start Building Awesome Silverlight 2 Applications. That's it, you're ready to start building incredible applications. Checkout this getting started video Quick Starts samples for Beta 2 are here You can review the breaking changes between Beta1 and Beta2 here For an Silverlight Tools update checkout What’s new with Silverlight Tools Beta 2 And of course be sure to check out ScottGu's post Silverlight 2 Beta2 Released Installation Errors? The rest of the post is dedicated to the variety of errors and workarounds when not following the above sequences.   The length of this post should be incentive enough to stick to the script above. If you've already run into problems, fear not.  The rest of this post is dedicated to getting you up and running with Silverlight 2 Beta 2 and Visual Studio 2008 SP1 Beta. Installer Contents The "Microsoft Silverlight Tools Beta 2 for Visual Studio 2008" installer "silverlight_chainer.exe" contains the following installers: Silverlight.2.0_Developer.exe Silverlight 2 Beta 2 silverlight_sdk.msi Silverlight 2 Beta 2 SDK VS90-KB950630.msp KB950630 for Visual Studio 2008 RTM VS90SP1-KB950632.msp KB950632 for Visual Studio 2008 SP1 Beta VS_SilverlightTools_Beta2_Setup.exe Silverlight Tools Beta 2 for Visual Studio 2008 You can extract the individual components using this command: silverlight_chainer.exe /extract The first thing you'll notice is that there are two KBs, KB950630 and KB950632.  KB950630 is a patch for Visual Studio 2008 RTM KB950632 is a patch for Visual Studio 2008 SP1 Beta The installer will apply the patch matching the installation of Visual Studio that you have.  This is why you need to rerun the Silverlight Tools Beta 2 installer if installing Visual Studio 2008 SP1 Beta after installing Silverlight Tools Beta 2. note: These KBs are ENU specific.  The localized release of Silverlight To[...]

VS Live Orlando "Introduction to Silverlight programming"

Thu, 15 May 2008 19:56:00 GMT

I just got back from VS Live in Orlando where I was pinch hitting for Jesse Liberty and presented a talk titled "Introduction to Silverlight programming". I wasn't familiar with Jesse's talk so I threw something together base on a new hands-on-Lab from Sascha Corti at Microsoft Switzerland.  It's a great walk-through leveraging several of the new Silverlight 2 controls to build a working Silverlight application. This hands-on-Lab was originally developed using Expression Blend 2.5 to build the Silverlight UI.  Since this was a VS Live presentation I thought it would be fun to create a VS track through this lab using the great XAML intellisense in VS. During the talk we covered: Creating Silverlight projects in VS Editing Silverlight pages in Expression Blend Layout using Grid and StackPanel TextBlock vs TextBox WatermarkTextBox DatePicker Slider How to create a DropDownList from a user control Asynchronous WCF service calls DataGrid Homework left for the audience: Add the picture gallery using a ListBox and data binding using {Binding } syntax Using type converters to create a Image URL Add the pop-up with car details using storyboard animations Add improved styling for the DataGrid and Slide Attached to this post is the slide deck along with my script for the VS Track through the hands-on-lab.  A great place to start is to simply download the lab and start working your way though it.  Sascha has done a great job of documenting each step along way. Tools used in lab: Microsoft Silverlight Tools Beta 1 for Silverlight 2 Expression Blend 2.5 Preview MSDN Tech Talk and Hands-on-Lab "Silverlight 2" References Jesse Liberty's Slides and Code from VS Live San Francisco[...]

Error installing Visual Studio 2008 SP1 Beta and Silverlight Tools Beta 1

Mon, 12 May 2008 15:32:02 GMT

Microsoft Visual Studio 2008 SP1 Beta was released this morning.  There are known incompatibilities between it and Silverlight Tools Beta 1. 

To install VS08 SP1 Beta you must uninstall Silverlight Tools Beta 1 and KB949325. 

Complete details can be found on the Visual Web Developer Team blog at:

Silverlight Tools Beta 2 will be release in the coming weeks and has full support for VS08 SP1 Beta.

Silverlight Game Tutorial by Mike Snow

Mon, 31 Mar 2008 16:09:47 GMT

Mike Snow has started a great blog series on game programming with Silverlight.  Check it out

Installation Tips for Silverlight Tools Beta 1 for Visual Studio 2008

Thu, 06 Mar 2008 06:52:00 GMT

  As many of you know Silverlight 2 Beta 1 was release today at MIX08.  What an awesome day.  The new applications under development based on Silverlight 2 are truly incredible!  Check out To get started with Silverlight 2 you can download "Silverlight Tools Beta 1 for Visual Studio 2008" here. The Silverlight Tools installer will install everything needed to start working with Silverlight 2 in Visual Studio 2008. It installs the following: Silverlight 2 Beta 1 Silverlight 2 SDK Beta 1 KB949325 for Visual Studio 2008 Silverlight Tools Beta 1 for Visual Studio 2008 Even if you've previously installed Silverlight 1.0 or Silverlight 2 Beta 1 the installer will proceed and install the additional components. That's it!  You're now ready to start creating rich Internet applications with Silverlight 2 and Visual Studio 2008. While the installation is that simple in most cases, there have been some installation issues reported.  I've listed below the issues and solutions I've run into so far.  I'll update this post if new issues are reported. Installation Error If you do run into an installation error, it's most like due to a previous installation of Silverlight 1.1 Alpha or any of the Silverlight SDKs, including the Silverlight 2 Beta 1 SDK.  You must uninstall all these components before installing Silverlight Tools Beta1 for VS08.  If you don't uninstall these products first you'll get this error dialog from the installer. If you see this dialog, be sure to uninstall all the dependent components and restart the installer. Can't Find KB949325 to Uninstall? If you ever need to uninstall KB949325, you can do this through Add and Remove Programs.  However it does not show up by default in Add and Remove Programs.  Instead you need to select "View Installed Updates" Now you'll see all the updates and patches installed to applications on your computers.  Scroll down and you'll find KB949325.  It will be listed as: It should not come as a surprise that if you uninstall KB949325, you will not be able to use Silverlight projects in Visual Studio.  Only uninstall KB949325 if you're planning on returning VS08 to its RTM condition or if you're attempting to reinstall Silverlight Tools. Prompt for installation source media In some cases you may get a prompted for the installation CD-ROM for Visual Studio 2008. Heath Stewart has an excellent blog post on some of the issues users are encountering when installing patches for Visual Studio 2008. You can read his entire post here.  Heath has a new post specific to this prompt when installing Silverlight Tools here. One of the scenarios causing this to happen with the Silverlight Tools installer is when Visual C++ is not installed.   The other component that will cause this to happen is if you don't have the "Microsoft Visual Studio Web Authoring Component". You can manually get around this.  First you'll need to extract the individual installers from the Silverlight Tools Beta 1 for VS08 chained installer.  To do this download and save the Silverlight Tools chained installer from here and save it locally. To extract the individual installers run this command:  silverlight_chainer.exe /extract This will extract the following installers, along with other support files. Silverlight.2.0.exe VS90-KB949325.msp silverlight_sdk.msi VS_SilverlightTools_Beta1_Setup.exe It critical that you install these components in the order listed above.  (Silverlight 2, KB949325, SDK, Tools)  To install KB949325 w/o being prompted for media run this command: msiexec /p VS90-KB949325.msp /L*vx VS90-KB949325.log REINSTALL=ALL Note: this command will require administrative rights and it does n[...]

Developing Web Applications on Windows Vista with Visual Studio 2005

Mon, 18 Sep 2006 22:12:00 GMT

Bradley Millington just made a great blog post about using IIS7 RC1 with VS2005.


How to set scriptmaps in a Web Setup Project

Mon, 11 Sep 2006 18:21:00 GMT

Van Kichline has started a series of blog posts documenting how to extend web setup projects.  His first post documents how to set the ASP.NET 2.0 scriptmaps

Hope this helps,

ASP.Net WebProfile Generator

Tue, 09 May 2006 03:02:00 GMT

Tim McBride has published a cool sample that will generate a WebProfile class for accessing the ASP.NET profile object from within the code behind files of a Web Application Project.

Because Web Application Projects compile the code behind files in advance of ASP.NET they do not have access to dynamically generated types like the Profile object.  This sample provided an add-in into VS that will generate a WebProfile proxy class that will fetch profile information from the real ASP.NET profile object at runtime.

Hope it helps,

Web Application Projects Officially released!

Tue, 09 May 2006 00:21:00 GMT

Web Application Projects has been released!  It live at:


New since RC1:


  • Team Build Support with VSTS
  • Strongly-typed access to resources defined in App_GlobalResources
  • Edit and Continue Support (To Enabled check Project Properties Web Tab)
  • Numerous bug fixes…. 

Web Application Projects now provided a similar development style and compilation model as was used in Visual Studio 2003, but with full ASP.NET 2.0 support!


Hope this helps,

How to share dynamic URLs across multiple Web Application Projects

Thu, 04 May 2006 19:24:00 GMT

I was recently asked how to configure a Dynamic URL so that it could be updated in machine.config and affect all Web Application Projects calling that Web Reference on that machine.  This is fairly straight forward in VS03 and in VS05 Web Site projects. In both VS03 and in VS05 Web Site projects the Web Reference proxies are generated to lookup the dynamic url form the section of web.config Web.config          Proxy Generated:           ///         public WebService()            string urlSetting = System.Configuration.ConfigurationManager.AppSettings["localhost.WebService"];                  if ((urlSetting != null)) {                this.Url = urlSetting;            }            else {                this.Url = "http://localhost/test/WebService.asmx";            }        }     Since the section rolls up from machine.config it's easy to put this setting in machine.config remove the entry from  web.config and you're all set. However, in VS05 WinForm projects and Web Applicaiton Project the proxy is generated to use the   section.   Web.config                          
                                                    http://localhost/test/WebService.asmx                            Proxy Generated:           ///         public WebService() {            this.Url = global::MainWeb.Properties.Settings.Default.MainWeb_localhost_WebService;            if ((this.IsLocalFileSystemWebService(this.Url) == true)) {                this.UseDefaultCredentials = true;                this.useDefaultCredentialsSetExplicitly = false;            }            else {                this.useDefaultCredentialsSetExplicitly = true;            }        } As you can see the proxy generated is very different depending on the type of project you’re using.  If you want to specify a dynamic URL in machine.config that can be overridden in web.config.  It turns out that was ver[...]

How to open a website in Visual Studio 2005 from the command line

Fri, 09 Dec 2005 22:54:00 GMT

I’ve seen several queries asking how to launch Visual Studio 2005 opening a specific folder as a website from the command line.  Unfortunately Visual Studio 2005 does not support this by default but you can enable the scenario by writing a macro.   To do this, create a new macro either in an existing module or in a new module.  For this example I’m going to add a module call Website to the MyMacros project.   If you’re new to macros in Visual Studio 2005, select menu Tools/Macros/Macros IDE, then select the MyMacros project and add a module.   Before you can use the new Website extensibility objects within VS you’ll need to add a reference to VsWebSite.Interop.dll.    Once added you can add the following code:   Public Module Website     Sub OpenWebsite(Optional ByVal path As String = "")         If (String.Compare(path, String.Empty) = 0) Then             MsgBox("Must supply a folder path to the OpenWebsite macro", MsgBoxStyle.OkOnly)         Else             Dim webPkg As VsWebSite.VSWebPackage             webPkg = DTE.GetObject("WebPackage")             webPkg.OpenWebSite(path, VsWebSite.OpenWebsiteOptions.OpenWebsiteOption_None, False)         End If     End Sub End Module     After this code is added you’ll be able to run the macro.  You can test it out in the command window.   From the Command Window in VS:   >Macros.MyMacros.Website.OpenWebsite C:\MyProjects\MyCompany\CompanySite   From the Command Line:   devenv /command "Macros.MyMacros.Website.OpenWebsite C:\MyProjects\MyCompany\CompanySite"   After its working you can register a shell command enabling an “Open as Visual Studio Website” command on any folder in windows explorer.   To do this copy the following into a OpenWebsite.reg file and run it.   Windows Registry Editor Version 5.00   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\OpenVSWeb] @="Open as Visual Studio Website"   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\OpenVSWeb\command] @="devenv.exe /command \\\"Macros.MyMacros.Website.OpenWebsite %1\\\""     Now you should be able to right click on a folder in Windows Explorer and select “Open as Website”.   Hope this helps, Brad.[...]

Tips to optimize design-time build performance for Web Sites in Visual Studio 2005

Tue, 06 Dec 2005 06:03:00 GMT

There have been a number of posts with tips to improve build performance within Visual Studio 2005.  I've consolidate these posts and other tips into a single post of techniques for common problems. Do not disable batch compilation Make sure web.config does not have The default is “true” so unless it’s explicitly set to “false” you’re ok. Some post have recommended disabling batch compilation to address a migration issue with circular references.  Unfortunately this dramatically impacts build performance.  You're much better off addressing the circular references than to disabling batch compilation. Leverage Server-side CompilationVisual Studio 2005 is leveraging ASP.Net 2.0 server-side compilation.  The IDE is primarily validating that the site will compile.  For most edit/run iterations it's not really necessary to validate/build the entire site on every F5 or solution build.Change Build options for the web site project:  (Property pages F4 -> Build)    “Start Action (F5)” should be either "build page" or "no build".  -  Improves F5 performance    “Build Solution Action” uncheck “Build Web as part of solution.”  -  Makes b very fast. While this does improve build performance because ASP.Net is only compiling the files needed for the request on F5, it doesn't help the developer identify all the compilation issues within the IDE before running.  There are a couple of techniques you an use to help with this. Move App_Code files into a separate class library project and reference it form the web site project.  This will improve build performance and provide all compilation errors for these class files within the IDE. Add a Web Deployment Project to the solution.  Configure the Web Deployment project so that it only builds for the release configuration.  This will allow you to completely validate the site before deployment without compromising the performance of the edit/run iterations under the debug configuration. Move App_Code files into a separate class library project I'm repeating this tip because even if you don't change the default build options you can improve build performance by moving the files from App_Code into a separate class library project. Check for conflicting dependencies If you do have conflicting dependencies, the web site project will do a full clean rebuild on every build even if only a page changes.  The problem is when you add a file based references that have a common dependency but to different versions of that dependency.   A file based references have a .dll.refresh file in the bin folder.  The .refresh file has the path to the original assembly.  These paths are checked on every build.In this example we have two assemblies, A.dll and B.dll both dependent on Foo.dll.    A.dll -> dependent on Foo.dll     B.dll -> dependent on Foo.dll When A.dll is refreshed the project system will discover the dependency on Foo.dll and copy it into bin. Likewise when B.dll is refreshed Foo.dll will be copied if different than the one already in bin. The problem is that when a class library is built by a class library project in VS it caches the dependencies. So as you can see here Class Libraries A and B both have a private copy of Foo. ClassLibraryA     A\bin\debug\A.dll     A\bin\debug\Foo.dll ClassLibraryB     B\bin\debug\B.dll     B\bin\debug\Foo.dll ClassLibraryFoo     Foo\bin\debug\Foo.dll If ClassLibraryFoo is updated and only ClassLi[...]

How to auto-increment assembly version using a custom MSBuild task

Fri, 02 Dec 2005 17:31:00 GMT

The assembly version string has the format “”, such as 2.0.50727.42.  Here is a sample on how to create a custom MSBuild task for Web Deployment Projects  to auto-increment the build and revision portion of your version strings with each build.   Web Deployment Projects provide a way to pre-compile a Visual Studio 2005 Web Site project into a single assembly.  It also allows you to specify the AssemblyFileVersion and AssemblyVersion for this assembly.   These values can be set in the Project Properties dialog of the Web Deployment Project.  Once set the following will be added to the Web Deployment Project file.                 true         The Microsoft.WebDeployment.targets file includes a target named GenerateAssemblyInfo that will use the @(AssemblyAttributes) item collection defined above to dynamically create an AssemblyInof.cs file.  This file is compiled into an assembly and passed to aspnet_merge.exe using its –copyattrs argument.   This is great if you want to fix the version to a specific value, but what if you want to generate a new build number with every build.  After all the format of version string is “”.   To do this we’ll need to dynamically generate the AssemblyAttributes item collection at build time instead of statically declaring their values in the Web Deployment Project file.   First create a custom MSBuild task.  MSBuild tasks are classes derived from Microsoft.Build.Utilities.Task that override the Execute() method.  You can learn more about writing MSBuild tasks from How To: Write a Task   Here is a sample MSBuild task that will increment build and revision numbers.    Contents of file IncrementBuildNumber.cs:   using System; using System.IO; using Microsoft.Build.Utilities; using Microsoft.Build.Framework;   namespace MyTasks {     public class IncrementBuildNumber : Task     {         string m_fileName;      // Text file containing previous build number         long m_buildNumber;     // Build number based on current date. 12/2/2005 would be 51202         long m_revisionNumber;  // Revision number, increments within a day with each new day starting at 0           ///         /// MSBuild entry point into this task.         ///         public override bool Execute()         {             bool bSuccess = true;             try             {                 IncrementNumbers();              &nbs[...]