SharpDevelop Community

Get your problems solved!
Welcome to SharpDevelop Community Sign in | Join | Help
in Search

Laputa

This is a mirror of http://laputa.sharpdevelop.net/, the core team's central news blog.

September 2008 - Posts

  • Code Analysis improvements in SharpDevelop 3.0

    In revision 3506, SharpDevelop 3.0 got improved support for code analysis using FxCop 1.36.

    There were some bugs fixed that were related to the suppress message command - it was working only with FxCop 1.35, but even there couldn't suppress messages for static constructors and explicitly implemented interface members.

    Using this command inserts a SuppressMessageAttribute in the code:

    A new feature is support for custom dictionaries for the FxCop spell checker. Instead of suppressing tons of spelling messages, you can simply add a new xml file to your project with content like this:

    <?xml version="1.0"?>
    <Dictionary>
      <Words>
        <Recognized>
         
    <!-- add words specific to your application here -->
         
    <Word>Uncollapse</Word>
        </Recognized>
        <Unrecognized>
         
    <!-- Disable Lineup as a single word - LineUp is the spelling used in WPF -->
          
    <Word>Lineup</Word>
        </Unrecognized>
        <Deprecated>
         
    <!-- Use this section to deprecate terms -->
         
    <Term PreferredAlternate="Best">Bestest</Term>
        </Deprecated>
      </Words>
      <Acronyms>
        <CasingExceptions>
         
    <!-- Use this section to tell FxCop the correct casing of acronyms. -->
         
    <Acronym>WiX</Acronym>
        </CasingExceptions>
     
    </Acronyms>
    </Dictionary>
    >

    And then set the file's build action to "CodeAnalysisDictionary" (this build action does not appear in the drop down, you'll have to type it in).

    Posted Sep 06 2008, 07:32 PM by Laputa
    Filed under:
  • XAML code completion

    More than one year ago, I added the XAML language binding to SharpDevelop 3.0, showing tooltips in .xaml files and enabling refactoring. ("XAML and WPF support in SharpDevelop 3.0")

    Now I finally added the missing part: code completion.

    You get completion when typing an element:

    For attributes:

    And for attribute values if the property expects an enum:

    Posted Sep 05 2008, 01:04 AM by Laputa
    Filed under:
  • First Mirador (SharpDevelop 4.0) Screenshot

    In case anyone gets a wrong idea, take a close look at the title bar - it has the word "experimental" in it:

    The reverse integration of the WPF branch is the first step in the direction of "more WPF" in SharpDevelop 4.0 (this screenshot shows the new WPF workbench and the new WPF start page).

    So what does this mean for the not-yet released version 3.0? As 3.0 is the last version built entirely on top of Windows Forms, it will be a long-term stable release series - meaning there are plans for at least 3.1 and 3.2. We know a lot of people are using our workbench, our text editor and various other parts in their applications - and we are definitely going to be supporting you in the future!

    Posted Sep 04 2008, 07:57 PM by Laputa
    Filed under:
  • Patch-Sized Contributions Without JCA

    Our Wiki has a guideline on joining the team which outlines the process of submitting code to the project. As part of this year's #develop developer days (#d^3) we decided on a change to the guideline:

    It is now possible to contribute "any-size" patches (be it a bug fix or feature enhancement) when those code pieces (your changes) are licensed under the BSD license.

    Why this change? We want to make it easier for the "accidential contributor" (ie someone who stumbled across a bug and dabbled with our code to fix it) to get her or his changes into our codebase without going through the "hassle" of having to sign & send the JCA. This should lower the barrier to contributing to our project.

    If you want to work on a larger feature, we still want you to send us a JCA - the simple reason being in it's name: it is a joint copyright assignment, making you and the project owners to the copyright, allowing you and the project to work with the code in any way desired. For more details on "Why the JCA" please see the guideline.

    Posted Sep 01 2008, 07:12 PM by Laputa
    Filed under:
Powered by Community Server (Commercial Edition), by Telligent Systems
Don't contact us via this (fleischfalle@alphasierrapapa.com) email address.