(solved) Silverlight Page in sub folder causes two clientbin directories to be created when web site built

04-06-2008 5:34 PM |

Solution 

I found the solution to the problem.  If you remove the default .aspx page that hosts the Silverlight control AND you create sub folders and host your controls in those sub folders, you can prevent the root client bin directory from showing if you right click on the web site, select the Silverlight Links tab, select the link in the root folder " / " and press Remove.  Now, Visual Studio will only build the actualy clientbin directory that your Silverlight application is in.

I have posted the problem and solution with images and full explanation on my blog at : http://karlshifflett.wordpress.com/2008/04/06/unwanted-multiple-clientbin-sub-folders-in-web-site-with-links-to-silverlight-application/

Original Problem

I have a super simple web site that has a sub folder.

I have placed the aspx page that hosts my Silverlight control in this sub folder.

When I build the web site, two clientbin folders are created.  On in the root of the web, the other in the sub folder.

 I have tried changing the .aspx page to reference the .xap in the rool clientbin and deleting both clientbins, but they both come back on rebuild.

1.  Is this normal?  Should there be two clientbin directories?

2.  If so, why?

3.  Anything I need to know about having two of these directories other than securing both?

Cheers,

Karl

Re: (solved) Silverlight Page in sub folder causes two clientbin directories to be created when web site built

04-10-2008 4:29 PM |

 I believe this was a known issue with SL2 Beta1 version of VS tools. I have also seen excessive empty ClientBin directory being created inside normal ClientBin directory containing built files. But with most recent internal build of VS tools the problem is gone, so I believe it was fixed sometime after Beta1 went public.

Re: (solved) Silverlight Page in sub folder causes two clientbin directories to be created when web site built

04-10-2008 4:34 PM |

Thank you for the information.  Glad it's getting sorted out.