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


cheong cheong Recent Cheevo unlocked: You got cookied!
  • hi there

    *yawn* So?

    Read the fine text. Hard hat required.

  • visual studio 2013 supported html5 but Internet Explorer not supported? why?

    I think the Textbox control is not Input control. If you want to use Input control, use Input control instead.

    Actually, I actively avoid using WebControls in order to avoid inconsistency between browsers (this, IMO, defects the major purpose of using WebControls) Those controls also lacks the ability to set inline styles to them.

  • Mil-spec Lumia for ASW?

    Right. That is "Adaptive Support-Weight - Computer Vision domain".

    There is even paper that discuss it.

  • ASP.NET session switch provider at runtime?

    @figuerres: In many production servers that I've seen, they use permanent session database to store sessions and use the same mirroring mechanism to provide fault tolerance. Afterall if the SQL server all fails, their website would be non-functional.

    I think for normal website, a onerror redirection on SqlException when cannot connection to SQL server to static page is normal.

  • SpamSpamSpam


    Embedded Credit Card Ad. in his reply..

  • Microsoft's answer to every problem...

    , vesuvius wrote

    If you want detailed and technical assistance, file a bug on connect, and the person that wrote the code can investigate this bug. Support departments function on both fixes and workarounds, you clearly object to workarounds, so connect is the best way to achieve a detailed response

    In my experience, writing to MS Connect is only effective for IE team. For other teams you have to bless your luck on the first reply, as if the issue is not taken on the first reply, most probably it'll just set there a year and then closed as "Won't fix". The more helpful ones will just redirect you to paid support where you could go into the same frustration again.

    I think non-Microsoft staff people here more or less have experienced this.

    Regarding the plan to reinstall Office, they don't understand that most of us who works as servicing company cannot just uninstall Office because when reporting "reinstall" to the IT department of client, it's the same as "non-resolved". It's the same as wasting one paid support for case that can't be paid-back. So don't blame us for keep pressing when this kind of answer is given. If no other solution is given we'd have no choice but ask for refund of paid support token(s).

  • ASP.NET session switch provider at runtime?

    I think failback to local SQLExpress would be easier and better supported.


  • Most epic method you've seen?

    @androidi: Last time, I read that you shouldn't throw exception when it's not necessary. The Blah.TryParse() series of methods are there for you to evade the need to throw exceptions when it can be avoided.

    So no, I don't want to throw Exception in validation methods at all. Exceptions are reserved for data layer where that's the proper way to receive error message.

  • No more need for developers (that means you)

    , elmer wrote


    Claims of how tool-X will eliminate the need for "experts", consistently underestimate the required IQ to use tool-X, and how much of the population is eliminated if you need an IQ of just 115.

    Well, I won't say it's related to IQ, but those who need these tools often are those people who lacks the fundamental knowledge to use it properly.

    For example, try asking people without web authoring experience about what's the difference between CSS display and visibility style. I'd be surprised if more than 1 out of 10 can answer it correctly. And I'm not even going into the more chaotic realm like browser compatibility cases.

    People who have little/no CSS experience often have no idea on how to properly set up CSS selectors as well, this will generally lead to clumsy / nearly-impossible-to-maintain page code. To add insult to the injury, unlike at the time of FrontPage, you can't just have "smart CSS collector" to consolidate CSS style to remove redundant ones because you could also remove CSS classes related to logic as well (jquery and the sort of libraries).

  • Most epic method you've seen?

    , androidi wrote


    That's certainly true in the typical scenario, what's not seen in the above is that in this case it's a case of "all this really belongs here".

    I suspect that C# code will soon see a lot of the above, thanks to if(x.TryDat(out var derp)) { if(derp.TryDerp(out var doh)) { ... } }

    This could be avoided by modifying the IDE to auto-infer and generate the derp & doh definitions with optional in-line editing of the type and default value.

    That would avoid the same issue I have with async keyword. ie. when you are writing some new code, suddenly it's not valid unless you go back a few lines and add a new code there and then you have to go back to what you were previously writing. And when relying on IntelliSense instead of memorizing every TryApi, you can't reliably plan ahead, so you just have to type the !TryBlah(out thistypehere) to get a hint of the "thistypehere", which then needs to go on some line earlier.

    The only problem with this auto-generation is where would it be generated. I say just generate it on the line previous to the if(!x.TryBlah(out ...)) return Oops; - as I can move it later if need be.

    Not necessarily. Our company use TryBlah() a lot. We put them in ValidateData() method that'll return false and queue error message to a StringBuilder object that keeps the error messages. In this way parameter validation can be better parallelized in future.