So, I’d just merged some code into my test build to prepare a deployment to staging when I got a compilation error on a page stating that a “}” was expected and referencing a line in a temp file from the GAC that included a line like this:
[System.Diagnostics.DebuggerNonUserCodeAttribute()]
I’m scratching my head…wtf? I searched for the above and found a reference in the strings resource I had for the site. But, there weren’t any problems with the code…in fact, the site compiled just fine! More scratching…then I searched online. Found this. Different error but the same or rather a similar stack trace.
Then I thought about it. Missing closing bracket…well, we’d just modified some code recently that involved what I’m sure Microsoft would rather we didn’t do…in the front-end aspx file we did something like this:
<% if (something == true) { %>
<myfancyhtml></myfancyhtml>
<% }//end if %>
And, lo and behold, the recent merge managed to include two copies of the opening line with a single closing line. Lovely.
Anyhow, in case you run into this wonderfully obscure error, check your <% %> tags if the code behinds still compile successfully…probably have something in there that’s causing you problems…no need to reboot and all that crap.
kn
Just a quick nibble…I’ve always loved Pixar‘s work (and, yes, I wished I had some skillset that would’ve allowed me to work there but alas…) and followed it. I hated the idea of them being acquired by Disney even though it made some measure of sense. John Lasseter‘s been heading up the creative side of Disney since the acquisition which, I think, is the reason Disney isn’t still going down in flames. I might be wrong but I think Bolt was the first animated film produced while Lassiter was “in office” so to speak (though not put together by Pixar) and it wasn’t too bad. Not the same as a Pixar movie but not the complete crap Disney used to put out. You can see some of the creativity you’d expect in a Pixar movie in Bolt (the pigeons and their movements). It’s that sophisticated attention to detail and ability to find humor in that detail which is a Pixar trademark.
Now, Pixar’s first film post-Disney Acquisition, Up is coming. And, honestly, I don’t feel the same sort of anticipation I used to feel about their previous movies. I saw the trailer and it was like…meh. Even though I knew it was a Pixar movie, I couldn’t find any excitement in it. Not sure why 100% but I think one part of it is the switch to “plain old” humans. The only Pixar movie with humans as the main characters was the Incredibles–but they were superheroes.
I guess we’ll see if the movie does well enough to put it up on Pixar’s award shelf…thing is, in general, each Pixar movie’s done better than the previous one…something tells me this one won’t do BETTER but it’ll do okay. At least Iger’s standing by them…
kn
Ugh…chalk this up to one of those relatively obscure problems where you’ve got this crazy idea (using XSLT to generate the HTML for a page based on an XML file) so you don’t have to code up a full blown server-side page that has to hand build the page (correction: you’ve got to hand build it).
Anyway, I wanted to pass HTML through from the XML element to the final output. Of course, as we’re in the uber-strict world of XML, that will either: a) cause issues or b) get escaped and output to the user as HTML. I had the latter.
Off I went to find a solution (the usual time sink that it was) and found a couple ideas:
1) CDATA the content and use the xml:output‘s cdata-section-elements tag to have the template ignore it. Didn’t work.
2) Use the xml:value-of and xml:text elements’ disable-output-escaping. Worked for IE but failed miserably in FF3.
So, I bang my head on my keyboard as I’m prone to do and I then search for why FF hates me so when I do #2 above.
Turns out…it has something to do with the way FF processes the XML so they don’t support the attribute. Doh! But wait…what’s this just a few search results below the top? Switch xml:value-of to xml:copy-of and lo and behold that sucker starts outputting your element’s contents verbatim!
Ahhh…now I can go back the the tedious task of converting my basic form (not HTML) data into XML to use my newly minted solution!!!
kn
