The #develop teamblog
#  Saturday, September 06, 2008

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).

Categories: Daniel
Saturday, September 06, 2008 6:32:29 PM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Friday, September 05, 2008

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:

Categories: Daniel
Friday, September 05, 2008 12:04:00 AM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Thursday, September 04, 2008

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!

Categories: Chris
Thursday, September 04, 2008 6:57:06 PM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Monday, September 01, 2008

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.

Categories: Chris
Monday, September 01, 2008 6:12:32 PM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Friday, August 22, 2008

This addin integrates Microsoft StyleCop into SharpDevelop. StyleCop only supports C#, and this addin has been tested against StyleCop 4.3, earlier versions won't work.

Features

  • Line highlighting of the warnings found
  • Change StyleCop settings on a per-project basis, copying from a master file you can also configure
  • Run as part of the normal build process or on-demand from the project menu

So how do you run StyleCop? Simply from the context menu of the current C# project:

This will result in an error (given that you haven't installed StyleCop yet):

Therefore please download the latest version of StyleCop and install it. Note that you must install the MSBuild integration:

Once installed, you have to tell SharpDevelop where to find it. This is done in the Tools / Options dialog:

Click on "Find StyleCop path" and go to the MSBuild directory:

Now SharpDevelop knows how to find StyleCop, all you have to do is re-run the StyleCop inspection of your project. In my sample project this results in quite a few warnings:

As you might not go d'accord with the default style checks, you can manipulate the StyleCop settings right from your current C# project:

Those rules are documented in StyleCop.

Categories: Chris
Friday, August 22, 2008 8:03:13 AM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Wednesday, August 20, 2008

Because the question keeps coming up repeatedly in the forum, I want to repeat the most important pieces of advice from the last thread in this blog post. Firstly and most importantly:

If you use SharpDevelop 2.x, you must use TortoiseSVN 1.4.x.
If you use SharpDevelop 3.x, you must use TortoiseSVN 1.5.x.

So why is this important? Well, Subversion 1.5 does change the working copy format, therefore older clients cannot read the working copy anymore. And why is this important to SharpDevelop? Daniel continues to explain:

SharpDevelop uses its own copy of the Subversion library for marking files as added/removed/etc. This can upgrade the working copy to the 1.5 format.

However, SharpDevelop does not have it's own commit dialog - we simply start TortoiseSVN.

So there are two Subversion libraries used by SharpDevelop: the one we ship for local operations, and the one shipped with TortoiseSVN for commit etc. Because the Subversion 1.4 library cannot read working copies touched by the 1.5 library, you run into this kind of problem when either TortoiseSVN or SharpDevelop is too old.

To sum up: SharpDevelop 2.x ships with libraries that are compatible with Subversion 1.4 and requires TortoiseSVN 1.4 for UI. Whereas version 3.0 of SharpDevelop ships with (different) libraries that are compatible with Subversion 1.5 and requires TortoiseSVN 1.5 for UI.

So will there be an upgrade for SharpDevelop 2.x to support Subversion 1.5? This was a hotly debated issue, however, in the end it boiled down to the following question: do we want to ship two almost identical versions of SharpDevelop 2.2 that only differ in the version of the included Subversion library (because we would have to support both camps)? As that would create quite a bit of confusion, we decided to leave 2.2 as is and support Subversion 1.5 only in SharpDevelop 3.0.

Categories: Chris
Wednesday, August 20, 2008 8:01:00 PM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Tuesday, August 19, 2008

If you receive the following error message

but have TortoiseSVN installed, then you have run into the following snag: SharpDevelop 3.0 is explicity marked as 32 Bit application, thus it cannot use the x64 version of TortoiseSVN.

Solution: install TortoiseSVN 32 Bit. It can be used in parallel with the x64 version.

Categories: Chris
Tuesday, August 19, 2008 9:00:39 PM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Saturday, August 16, 2008

Running SharpDevelop on USB thumb drives has been possible for a long time. What is new in version 3.0 though is that the settings that usually go into the user's profile can live directly on the memory stick - allowing you to take your settings with you at all times. Here is the procedure:

Download SharpDevelop 3.0 and perform a standard installation on Windows. By default the installation location (on an x64 machine) will be the following:

Simply copy the 3.0 directory to your memory stick, and then open the \bin directory there:

There, you have to open SharpDevelop.exe.config - and search for the appSettings section which by default looks like this:

 <appSettings>
  <!-- Use this configuration setting to store settings in a directory relative to the location
       of SharpDevelop.exe instead of the user's profile directory. -->
  <!-- <add key="settingsPath" value="..\Settings" /> -->
  
  <!-- Use this setting to specify a different path for the code completion cache.
        The cache contains information about referenced assemblies to speed up loading
        the information on future SharpDevelop starts. -->
  <!-- <add key="domPersistencePath" value="..\DomCache" /> -->
  
  <!-- Use this setting to disable the code completion cache. Code completion will still be
       available, but take longer to load and use more RAM. -->
  <!-- <add key="domPersistencePath" value="none" /> -->
 </appSettings>

The comments tell you what to do, basically uncomment settingsPath and domPersistencePath:

<add key="settingsPath" value="..\Settings" />
<add key="domPersistencePath" value="..\DomCache" />

Save the file and you, SharpDevelop and your settings are ready to go. Note that once started the two directories show up in the directory tree:

Categories: Chris
Saturday, August 16, 2008 4:18:14 PM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Tuesday, April 01, 2008

Starting with version 3.0.0.3010, the C# code completion in SharpDevelop has support for implicitly typed lambda expressions.

Given a variable "IEnumerable<MyClass> items" and the "Select" extension method from LINQ, typing "items.Select(i => i." now shows the members of MyClass. And if the result of the Select call is assigned to an implicitly typed variable, SharpDevelop is now able to infer that the variable has the type IEnumerable<return type of the lambda expression>.

Unlike all other expressions in C#, the type of a lambda expression cannot be inferred just from by at the expression itself (and the variables used by the expression). To resolve lambda type parameters, we also need to look at the context where the lambda is used. Currently, not all contexts are supported by code-completion, you can find the list of known problems in our bugtracker (Component: DOM / Resolver). Should you find anything where code-completion does not work correctly which is not in that list, please file a bug report in our forum.

The most commonly used context for lambda expressions is method calls, and this is also the most difficult thing to support. It's easy when the method has a clear signature like "void M(Func<int, string> f)", since then SharpDevelop can infer the lambda parameter types directly from the delegate type. But most of the time, things aren't that easy. For example, the signature of the Select method is "IEnumerable<R> Select<T, R>(this IEnumerable<T> input, Func<T, R> f)". Here, SharpDevelop needs to first infer what T is, then it can know what the lambda parameter types are, and only after that it can resolve the lambda expression to infer what R is.

But when the method has multiple overloads, things can get even more messy:
When a method has to overloads "void M(Func<string, int> f)" and "void M(Func<int, int> f)", it is valid to call them like this: "F(i=>i.Length)", "F(i=>i+i)". In the first call, i is a string; in the second, it is int. What SharpDevelop needs to do here is to infer the lambda parameter types for each overload separately, infer the lambda's return type; and then check that against the delegate's signature to see which overload was the correct one.

i=>i.Length is a resolve error if i would be int, but returns the expected int if i is string; so i must resolve to string.
i=>i+i returns a string if i would be string, but returns the expected int if i is int; so i must resolve to int.

Note that because there's no way to tell the type of i before the lambda expression is completed, you cannot expect that SharpDevelop gives you correct code completion for it. "Length" will not be included in the code-completion list for i when you type ".", because at that point, the method call is "F(i=>i)", and i is thus an int. But after the expression is written, SharpDevelop will show a tooltip for "Length", and features like "Go to definiton" and "Find references" will work.

Categories: Daniel
Tuesday, April 01, 2008 8:13:48 AM (GMT Daylight Time, UTC+01:00)  #    Comments [0]

 



#  Tuesday, March 04, 2008

In addition to our presence on SourceForge (project page) we now also set up shop at CodePlex (project page). The motivation for this step is to increase awareness about SharpDevelop, and how parts of SharpDevelop can be reused in other applications / scenarios.

Categories: Chris
Tuesday, March 04, 2008 11:42:29 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]

 



© Copyright 2014 SharpDevelop Core Team

Subscribe to this weblog's RSS feed with SharpReader, Radio Userland, NewsGator or any other aggregator listening on port 5335 by clicking this button.   RSS 2.0|Atom 1.0  Send mail to the author(s)

 

Copyright ©2000-2009 IC#Code. All rights reserved. Projects sponsored by AlphaSierraPapa.