Your official information source from the .NET Web Development and Tools group at Microsoft.
In Beta1, VS Silverlight tools doesn’t allow users to maintain separate build output folder for different build configuration, and this causes once you switch from “Debug” to “Release” build configuration, under ClientBin folder the existing debug assemblies will be overwritten by the release version. Unless you switch back to “Debug” configuration, you can’t get the debug version back. This also impacts the .xap files copied to the ClientBin folder at the hosting web project.
In Beta2, we have made several changes to improve the experiences
1. At Silverlight project side, we don’t use the “ClientBin” folder anymore; rather, we bring back the old one of “Bin” coming with regular client projects
2. Underneath it, each build configuration will have its own subfolder called “Debug”, “Release”, etc.
3. At a web project’s side, underneath the “ClientBin” folder, there is a subfolder created for a specific build configuration. The .xap file gets copied to there
4. You can feel free to switch among different build configurations. VS build will pick up the current active configuration and builds the project and copies to the hosting web project. If you use msbuild, you can pass in the preferred configuration through the command line.
Several UI elements were also adjusted accordingly
1. In the “Add Silverlight Application” wizard, you have a checkbox to enable this. If you turn it off, you will get beta1 behavior
2. If you have already added a Silverlight application into a web project, you will have UI option in the property page dialog to enable this (click the “Change…” button)
3. Now you are having a VS project which is configuration folder aware.
PingBack from http://www.basketballs-sports.info/basketball-chat/?p=1646
Sapete a cosa serve questo checkbox ? Lo trovate nel wizard di creazione di un nuovo progetto creato
My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. Sara Ford's Tip of the Day #233 covers increasing Visual Studio environment fonts for presentations . US ISV Developer Evangelism
I had a SL app and I changed it to use config folders via the Project Properties as you have advised in 2. I do get the web site project to now have ClientBin/Debug/*.xap but the SL project does not get the bin folder but still retains the ClientBin folder. Am I missing something?
Rupak, take a look at "6. Linking a Web Site to a Silverlight Application." at
You want to modify the destination folder (currently, you have it set to ClientBin).