StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Previously, I started starting the silverlight app directly via the VS2010 environment... but then decided to get more deployment compliant (again).</p> <p><a href="http://msdn.microsoft.com/en-us/library/cc838267(VS.95).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/cc838267(VS.95).aspx</a></p> <p>Down the bottom they mention repairing from control panel / VS2010. Did that. Waited for ages, made coffee, did something else. Finally complete. Problem sill there. Included this step just-in-case the fix is cumulative (you get superstitious after a while with these things).</p> <p>I then deleted zap files, switched startup page from html to the aspx one. Wired aspx to the xap (it wasn't pointing to the /debug/ folder). [note: looks like you can remove the debug via Silverlight Project / build / Output path: Replace Bin\Debug\ with Bin. With Silverlight I <em>feel</em> that the relative Uri path should match up to your html / aspx files no matter what -- wheather you are in Debug or Release. </p> <blockquote> <p>project properties / Web / Specific Page</p> </blockquote> <p> debugging works again! </p> <p>Did .html stop debugging? Casual inspection reveals the same javascript stuff firing up Silverlight. On the surface it looks the same. hmmm. I guess it isn't.</p> <p>... here are a few extra things to look at for those who still have issues (I may as well list them while they are fresh in my mind).</p> <ol> <li><p>project / properties / Web / Debuggers: I now only have Silverlight checked. ASP.Net is not checked any more. (Not sure if this influences my result at this stage)</p></li> <li><p>make sure your web project points to the silverlight project in project / properties / Silverlight Applications. This ensures that the silverlight project's binary "xap" is copied to a folder within the Web Site / Web App. Note: hitting the add button reveals a destination folder (should be ClientBin). </p></li> </ol> <p>Your build configuration will add an additional sub foler e.g. debug.<br> Make sure your .aspx or .html files have the right path. For me, I just included the .ClientBin/debug/ folder. I don't think this is deploy friendly, so I will search for a better way later. </p> <ol> <li>IE9 settings. </li> </ol> <p>[X] Disable script debugging.</p> <p>[X] Disable script debugging (Other)</p> <p>[ ] Display notification about a script error</p> <p>[ ] Show friendly HTTP error message</p> <p>Again, unsure if these later setting have an impact.</p> <p>Lastly, there's something that I forget about sometimes. Be sure to check Debug VS2010 / Exceptions / Common language Runtime. This ups the ability to catch exceptions.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload