Freigeben über

WinForms, WPF and Working for Microsoft

  • Artikel

I had an interview candidate ask me recently what I loved most about working for Microsoft. Oddly enough the answer is you! I love the amazing community of developers Microsoft is fortunate enough to have. I love it that you let us know when things aren’t work the way they should and I really, really love it when we can fix those things right away.

Mike talked about one of those things in his recent post on shipping the WPF-WinForms interop technology in Vista\WinFX. Having been somewhat involved in making that decision, I can tell you that feedback from YOU played a key role in making the change... So please, by all means, keep the feedback coming and thank you!

Comments

  • Anonymous
    March 02, 2006
    The comment has been removed
  • Anonymous
    March 02, 2006
    How about forcing the Avalon team to fix the countless serious FxCop violations in the latest CTP to prevent them from making the same mistakes as the WinForms teams...
  • Anonymous
    March 02, 2006
    Thanks for the feedback... Keep it coming..
    What are the specific FxCop violations that bug you?  Hearing your feedback on specifics helps us prioritize fixes..
  • Anonymous
    March 03, 2006
    I'd like to see some visual performance improvement.
    Currently WinForms windows paint quite slowly if they have a few controls than usual.
    Maybe a two phase initialization of the controls might help, that is, first initialize all UI/visual properties to be able to show up the control and form as early as possible and then the other, non visual, properties (hopefully asynch). In this way the UI pains faster even that it's not complete and responsive.

  • Anonymous
    March 03, 2006
    Please add a decent color picker control. The current is a poor excuse.
  • Anonymous
    March 03, 2006
    Just to name a few in WindowsBase and PresentationCore:

    Just Plain bugs:

    -> Instantiate argument exceptions correctly
    -> Mark ISerializable types with serializable
    -> Validate arguments of public methods
    -> PInvoke declarations should be portable

    Design Issues:

    -> Avoid out parameters (TileBrush.GetContentBounds(out Rect contentBounds):Void);
    -> Collection properties should be read only
    -> Rethrow to preserve stack details
    -> Do not raise reserved exception types (there are nearly 50 internal methods are that are throwing Exception or SystemException)
    -> Implement IDisposable correctly (public types such as DocumentPage, GestureRecognizer, etc)


    Naming & Spelling:

    -> Only FlagsAttribute enums should have plural names
    -> Long acronyms should be pascal-cased (URI instead of Uri)
    -> Compound words should be cased correctly
    -> Short acronyms should be uppercase
    -> Use preferred terms
    -> Resource strings should be spelled correctly

    Looks like Framework Design Guidelines should be required reading....
  • Anonymous
    March 03, 2006
    Wow, thanks for this feedback ...
    Please use any forum that works for you to get feedback over to us at WinForms, we do take these suggestion seriously in our feature planning.

    Also if you would like to track your bug reports/feature requests and have people vote to support your want, LadyBug is the best way of getting to the product teams.

    To Log a Winforms Bug -

    Go to the main Ladybug page [http://lab.msdn.microsoft.com/productfeedback/Default.aspx].
    Log in using your MSN Passport credentials (@hotmail or @msn email)
    Under Product/Technology, select Windows Forms
    Investigate whether or not your bug and/or suggestion has already been logged by another user.
    (Very often it might turn out to be an issue we are already lookign at and you can add your vote to bug so we know another customer cares for the scenario as well)
    Fill in the form.

    Keep the feedback comming.
  • Anonymous
    March 03, 2006
    Laura thx for your suggestion on visual performance improvement, we shall be looking at performance improvements for our next major realease.

    Milena  our Performance Developer has an article out in MSDN magazine you might be interested in.
    http://msdn.microsoft.com/msdnmag/issues/06/03/WindowsFormsPerformance/
  • Anonymous
    March 04, 2006
    I just watched your piece about WinFx on MSDN TV.  I have a question/comment regarding that.  One of the selling points of .net initially was that,  an application developed on .net would be portable.  With WinFx, it seems like .net is tightly coupled with the Windows operating system there by losing "portablility".   I'd like to hear your thoughts on this.  
  • Anonymous
    March 04, 2006
    As you likely know we have standardized a subset of the .NET Framework that allows anyone to build a base level implementation.   And of course we have the .NET Compact Framework as well which runs on many devices  

    A broad range of OSs and devices are as important as ever if not more so...

    Does that help?
  • Anonymous
    March 08, 2006
    Anonymous Coward-
    We'll look through those violations and post a reply soon.  Some are clearly by design...and we'll explain why.  But let us go look at that list first.
    Thanks, Rob
    WPF, PM
  • Anonymous
    June 16, 2009
    PingBack from http://fixmycrediteasily.info/story.php?id=11023