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

y2k4life

y2k4life y2k4life

Niner since 2006

  • LINQ to SQL and the O/R Designer in VS 2008

    Nice How-To vidoes, but now I know how it feels when the VB.net programmers see thing for C# only.

    Where is the:

    “How Do I” Videos — C#

    Are these videos available for C#? I looked under that section on the MSDN but found nothing related to LINQ to SQL or pretty web page like that for VB.Net.

  • Visual Studio Orcas Express: Building "Hello World" using Windows Presentation Foundation

    Thank you,

    That was all that is needed and expected during beta are q&a. what I don't like are a bunch of Q's or no Q's at all, and to not get any A's after one posts a Q. Then to get a final release with something missing.

    Yes I understand the goo you all are in I work in the same place. Cool

    Interesting enough also by asking the question and reviewing the response I'm learning more on the new ways of producing the code from the editor "fallback feature" (I like how you add *feature* Wink it is not just a fallback it is a fallback feature). If I'm in the code no need to switch to the form editor to double click on a control or an event in a event list to generate code.



    chadr wrote:
    
    No harm in asking about a feature you care about, just try not to use Beta 1 to jump to conclusions about the final product or how we prioritize language support.  We're still working



    ".snoitseuq diputs on era ereht" syas rehcaet ym sA


    I'm not trying to guess or jump to conclusions, but with out anything to go by is one to assume that what is not there will be in the final release or even beta2? Then take the stance as the other post says and as you elude to, and that is don't ask questions, just report bugs? Then wait for the final release then ask? That is where the goo gets sticky, with other projects one might publish to the web what is being worked on, completed, etc... So how am I to know if a feature is is in the final release or not unless I ask. If a feature list with status was posted some where then I would see in beta 1 it is not available but will be in either beta 2 or an RTM or final and I would not need to ask a question. And if this list does exist then someone one could have posted that and I would be on my way, hoping not to ask a questions in the future.
     

    - gb.

  • Visual Studio Orcas Express: Building "Hello World" using Windows Presentation Foundation


    CPrest wrote:
    
    Its in beta right now.  you know what beta means correct ?


    Yes, I do. The question is do You?

    Obviously not, unless the involvment of the community during beta has change. If that means we just take it as is and don't voice our opinions to figure out what is in the Beta and what is going into the RTM.

    The point of Beta is to bring up issues like this. To figure out if this feature (or lack of) is beta or is this going to be in the RTM (or not).

    If I took your train of thought I would not be asking these questions. Then when RTM comes out and I find out that they made this change, then ask the question, it is too late. Again why we ask questions during Beta.

    So, what I'm waiting for is "Ya, in the Beta for C# it is not there and will be there in the RTM" or "It is not there period this is the change and will be in RTM this way".

    If you look at my first post I was asking why we don't have C# features. Becuase I was more concerned with it being over looked and is VB more important and will we see features first in VB before C# or is it the other way around. Why am I see something in VB beta but not C# beta and if it is not there is this only during Beta.

    I understand that there might be features in one that is ready where the other might not be. Is there a feature list of what works or not in beta? That is what would eliminate quesitons.

    There do you understand Beta now?

    Ask questions now before it is too late?Wink




  • Visual Studio Orcas Express: Building "Hello World" using Windows Presentation Foundation


    chadr wrote:
    
    The reason I chose VB here is because VB's language allows for the "Handles" declarator, and the language service generates handlers from those object/event dropdowns in the editor.  It just made the example more streamlined -- didn't mean to imply that C# didn't work, it just works differently.


    Why not have that in the C# verison like in VS2005? I thought the idea was to add feature not take them away? That is something I do when I release bug fixes. I fix the bug, but break the code some where else. So, is it going to be the old way or the new way, write code?

    Why make VB *streamlined* and not C#.
  • Visual Studio Orcas Express: Building "Hello World" using Windows Presentation Foundation


    chadr wrote:
    
    I could have shown C#'s equivalent scenario by going into the Window1 ctor and typing "button1.click +=..." and then C# would have gen'd a handler stub for me and completed the delegate add.  Download the Beta and give that a try Smiley



    One better show us how it is done in C# if it is not done like VB Orcas or even the old VS 2005. Are you now saying that I'm not going to have a property list of Events and be able to doulbe click one to have the Orcas wire up the event and I focus on the handling the event.

    Now in Orcas with C# you are saying we have to do both? Go to ctor then type in the event we want to wire up. Then go and build the method declaration that was done for you in VS 2005. Then you get to write your code? So, in VS 2005 I would find the event double click and write my code? Now I got to write more code relating to the declaraction of code and not the logic itself?

    I'm going to try because I do see where you say the code is gen, if I type button1.click = new EeventHandler(foo). That it will build foo for me. It is just a lot easiery to *find* an event in the list and double click, ok I can use intellisense when I hit the period button1.c
  • Visual Studio Orcas Express: Building "Hello World" using Windows Presentation Foundation

    Things like this lead to a "Where is the C# version sample?"

    Ahh the event hanlders, funny I'm watching the video as I type.

    But then WTH, is MS is picking features for VB over C# in beta? What is the preferred language VB or C#? I guess with a multi language platform this can lead to an argaument that Java Platform does not. hehehe Wink



  • Scott Field: How secure is Vista, really? - Part II

    Bas wrote:
    
    y2k4life wrote: 

    Does buying Vista come with free training and education on all thes terms like UAC, MalWare, Prompts, etc... or Or is the user just left on there own.



    The UAC dialogs clearly say "This program is trying to run. If you started this program, please continue." or even "The source and purpose of this program are unknown. Don't run the program unless you used it before or know where it's from.", followed by "Cancel: I don't know where this program is from or what it is for."

    If the user doesn't understand that message, or worse, doesn't -read- that message, then yes, it's the user's fault.

    It's not an ideal system, but in my opinion, it's the best compromise between usability and security.


    Yes, but would your agree that by doing X and knowing I'm doing X I could answer the dialog box. But at some point would you agree that by doing X that not only X is being done but also Y and Z?  If the user gets a dialog box for Z do they know for sure that they started Z or is it a rogue? Do they know what Z is? No, So, answer No, and now X does not work? So the user is back to answering Yes to all because if not then X will not work?

    Fore example while doing an install the average user is asked to continue to run this program (installer). They would say yes. But then half way through the process they get a message Y.exe is trying to access the z.exe do you want to continue (was that the install or a rogue program)? Well they did not start Y.exe or Z.exe (the installer did which they gave access to).

    Funny thing was when I did an install it did not work. I had to actually create a boot start bat file. And elevate security.(http://blogs.conchango.com/pauloreichert/archive/2006/11/21/Windows-Installer-MSI-packages-error-code-2869-on-Windows-Vista.aspx.

    IMHO I think this is good and going in the right direction but should we cut off our nose to spite our face. We need to keep the average user in the loop as we go after the security issue. I think put technical systems in place to tackly the issues but the more and more dangerouse it becuase the more education is needed. I can't drive a car (even knowing how simple it is) with out education (legaly). Maybe we need license to use a computer (i'm not talking EULA)? Also as I pointed out Smokey says only you can prevent forest fires. How does he help, educates the campers. MS where is your Smokey The Bear "Only you can prevent hack attacks"? Where is your UAC commercial telling the average users for free what the hell that means?

    Obviously if we would live in a platonic world there would be no security issues Malware, hacker, or the likes. The average user would use the computer like it was intended and would not need twenty dialog/prompts asking if they want to open an email. But if it is going to be this difficult than educate them. And I don't mean by giving them text in a dialog box in hopes that they will understand and answer the question with clearity.

    I'm going to start up a survay in my local communtiy to see how many average users know what UAC means let allone what User Access Control is?



  • Scott Field: How secure is Vista, really? - Part II

    HellSnoopy wrote:
    ...everything, user stupidity is to blame most of the time.


    Ya, but if a user who is a brain surgen stupid because he does not know about a dialog box asking him to "xyz.pdq", when not knowing what it is going on?

    I know I won't be doing any brain surgery, and I know that brain surgury is not for the average person, *user*. Am I considered stupid because I can't do brain surgery from there point of view. But should a computer require a Computer Degeree to use just as much as it would take a PHD to operate on a human.

    I know that is apples and oranges but the point is that it should not be. Is the user is considered to have *user stupidity* because they can't operate a computre or a genesis becuase they can operate on the brain.
     
    The real issue here is the hacker. Second is educating the user and how and at what cost if not free. And third would be the one who should supporting the complete package (from selling to educating) and not jsut providing a platform for chaos.

    Don't forget the third party the malware creator who IMHO is the realy stupid person in this picture and not microsoft or the *average* user even if you think of them as doing something stupid.

    Does buying Vista come with free training and education on all thes terms like UAC, MalWare, Prompts, etc... or Or is the user just left on there own.

    Buyer beware!!! There are hackers out there that no one can stop but you and if you don't then don't blame the OS manufacturer or the hacker just blame yourself.

    Sounds like smokey the bear "Only you can prevent Forest Fires."


  • Scott Field: How secure is Vista, really? - Part II

    Well the uneducated user or the average user who just uses the computer. When they get a pop-up or prompt, and don't know what it means, 99.9% will say 'yes'. It goes back to things like a firewall (Zone Alarm, Norton, McAfee) showing a pop-up asking if the user if they wants to do 'xyz' on 'pdq'? Well more than likely, not knowing what a 'pdq' is let allone what it means to 'xyz' for 'pdq'. Then to be asked if they want to continue or not?

    Then if they get sick of the prompts or impatiant (like other programs) the user finds ways to turn off or disabling 'ABC' or should I say "UAC". They don't really read it or take patiants to look at, instead they just answer it. It is a tangent.

    I think the big point here is that the *average* user does not speak geek.

    So, they answer 'Yes' to the 'xyz,pdq' questions. Or they turn off 'ABC' regardless of the software trying to protect them. Or if enough FUD is applied the 'end-user'  answers 'No'. Could you image all the things that can't be done if you answer 'no' to all UAC prompts. So,  it is back to not reading and just answering 'yes' to all or disabling.



    - guy
    "Have a great day! You just unlocked the pick slip virus!."