Support configuration specific output folders in a Silverlight project

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...(read more) ...