Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Duncan Mackenzie Duncanma "yeah that's awful close, but that's not why I'm so hard done by"
  • Reason for Colors

    TommyCarlier said:
    Duncanma said:
    *snip*

    while (true) ;
    While True Do End While

    You can do it like this: [ code language="vb" ] ... [ / code ]

    language options: CSHARP (C#), HTML, SQL, VB (for VB, VB.NET, etc...), JS (JavaScript), PSH  (Powershell)

  • Syntax coloring, woohoo!

    Duncanma said:
    Sven Groot said:
    *snip*
    strange...  I'll look into that, perhaps I've accidentally done the code *after* the smilely replacement... the smiley code is supposed to ignore anything within

    <pre> ... </pre>
    

    language options: CSHARP (C#), HTML, SQL, VB (for VB, VB.NET, etc...), JS (JavaScript), PSH  (Powershell)

  • Syntax coloring, woohoo!

    Sven Groot said:
    TommyCarlier said:
    *snip*
    Now it should just disable smilies inside those blocks.


    public void Foo()
    {
    // Let's see if contextual keywords work
    var x = from x in someThing
    where x < 10
    select x;
    }


    And they don't, as I expected. Smiley
    strange...  I'll look into that, perhaps I've accidentally done the code *after* the smilely replacement... the smiley code is supposed to ignore anything within

    <pre> ... </pre>
    

  • Reason for Colors

    jh71283 said:
    Duncanma said:
    *snip*
    Kewl..... when go live?
    bool isCodeFormattingLive = true;
    

  • Keyword filtering

    blowdart said:
    HumanCompiler said:
    *snip*
    Indeed. Why is also why a "Mark all as read" on an index page would be good Smiley
    Erik brings this up on a regular basis (the desire for marking threads as unread/read) so I'm sure we won't forget about it Smiley

  • Full screen button, on Silverlight 2.0 player, not working.

    I believe this is a known issue if you have installed Silverlight 2.0 over 1.0 ... let me track down the details

    "If the user has installed SL2 over SL1 than there is an extra file that can be deleted as a workaround.  The file is called npctrl.1.0.30401.0.dll, and must be in the addins directory for Firefox.  It should be in the same directory as npctrl.dll which is the one that needs to stay."

  • Reason for Colors

    Checked in some source code coloring today... a few quick shots are on this blog entry here: http://duncanmackenzie.net/blog/chatting-today-amongst-the-evnet-team/default.aspx




  • Can't play SilverLight content on Channel 9

    Hey Mooch, sorry to hear that isn't working for you... we haven't tested on XP, but we have tested with Silverlight 1.0 and not run into any problems. Can you let me know what browser you are running, and if our videos worked before at any point?

    Thanks!

  • Unable to login

    C9 Logins Messd said:
    stevo_ said:
    *snip*
    I do though!

    the fact that you are getting that message at all sounds like you are hitting C9 with a different Live ID than before, could that be the case?

  • Why won't C9 validate?

    HumanCompiler said:
    mVPstar said:
    *snip*
    That's pretty much what I would've said.  We care, but it's low priority.

    Try looking at other major web sites out there.  We're doing better than a lot of them.
    We did spend time on this issue, by the way... but I only see two real errors that we can control ... one is that we have a <div> inside a <a> ... which does cause problems on Opera, so we render it differently for them... but our styling is dependent on the <div> at the moment so we leave it alone on other browsers. The other issues is that we have <img> elements with no source. That is an interesting one (at least to me) ... we need the <img> element there to put images into as you page through the site... so we started out with <img src="" /> (which validates) but running traces we noticed that syntax was causing FireFox to load the entire page (whatever page the <img> element was on) in as the image and therefore causing the user to retrieve twice as much data as was necessary. So we overrode the default asp.net image control to omit the src parameter if it was blank. That solved the double-retrieve issue, but added the validation error you are seeing.

    From what I can see, the editor is causing the rest of the validation errors. We could bug Telerik about it, but it is a low priority for us so we probably won't worry about it for right now. They release frequent updates though, so some future update may end up resolving these issues.