SharpDevelop

Google Summer of Code 2010 has been officaily announced and SharpDevelop intends to participate again. Google Summer of Code is an opportunity for students to earn 4500 USD over the summer by working on an open-source project. We have created a ... [More] list of ideas, but you can work on anything you want as long as it is related to SharpDevelop.  You can find the list of ideas and any further information on the SharpDevelop wiki page for the Google Summer of Code.  The application deadline is 19:00 UTC on April 9th.  In the meantime, you can start coding and talking to us on the forums, via email or on the IRC (#SharpDevelop at irc.freenode.net). Please spread the word and tell your friends about the Summer of Code as well. If you have any project ideas for the students, feel free to mention them in the comments below the post. [Less]

With the release of RC1, the code converter site has been upgraded too (from NRefactory 3.2.0.5362 to 3.2.0.5506). Relevant checkins: ... [More] http://fisheye2.atlassian.com/changelog/sharpdevelop/?cs=5432http://fisheye2.atlassian.com/changelog/sharpdevelop/?cs=5448 Supported languages (via Web interface as well as Web Service): C#, VB.NET, Boo, IronPython, IronRuby. [Less]

SharpDevelop execute many tasks that require progress reporting. Most also can be cancelled by the user. Examples are: Loading a solution (parsing files for code completion and class browser) Building Searching In SharpDevelop 4.0.0.5483 ... [More] , I've rewritten the IProgressMonitor interface used for these operations. The main difference in comparison with the old interface is that it is now possible to create nested progress monitors, allowing the composition of large progress-reporting operations from many smaller operations. Also, creating nested progress monitors now allows to safely report progress from parallel computations. Every thread can create its own nested progress monitor for reporting its progress. Now what happens with these progress reports? They will be collected by the ProgressCollector class. The ProgressCollector takes care of summing up the progress from all nested progress monitors. It also handles the multi-threading issues. The output of a ProgressCollector is a simple set of properties describing the current progress of the operation, plus a "PropertyChanged" event which will be fired only on the GUI thread. This allows using WPF data binding to display the total progress in a progress bar. Another difference is that the cancellation support has been simplified by making use of the .NET 4 cancellation framework. The above changes don't have any visible effect for the end-user. However, while working on this, I had an idea: similar to the progress bar in Windows Explorer in Vista and Windows 7, the progress bar should turn red when there are errors. This gives immediate visual feedback that the build failed, making it a lot less likely that you miss the error messages in the "Errors" pad and wonder why your binary didn't change.   A related change in SharpDevelop 4.0.0.5490 is that the progress is now shown on the Windows 7 task bar: So the progress of long-running builds is always visible; even if you minimize SharpDevelop and do something else while the compiler is working. [Less]

This blog post announces two major changes for SharpDevelop 3.2: a setup size reduction from 21.1MB down to 14.6MB (a clean 30% less than before), and an upgrade of Sandcastle Help File Builder support to version 1.8.0.3. So how did we shrink the ... [More] setup? Let's look at some sizes first: Revision 5493 is before the upgrade of SHFB support (happened in 5499), and 5500 is the latest setup build - with additional tweaks. So what are the tweaks? Basically, we had a look at feature usage. Like "How many people actually know that we are shipping the WiX *.chm documentation with SharpDevelop?" or "How many people actually generate documentation chm files from XML comments?". Turns out that the answer is "not too many". The delta of 5499 to 5500 shows the effect of the WiX help documentation. And 5493 to 5499 the delta of the old release of SHFB. Which brings me to the upgraded functionality: we had a 1.7 release in the box, and 1.8.0.3 uses a different project file format. We had to upgrade that for "Build documentation..." (project context menu) to work properly with the new release. If you don't have SHFB on your computer (which is now the default after installing SharpDevelop), you will see the following dialog: This dialog is now standardized (we haven't installed TortoiseSVN in the past either). Simply follow the link, install the latest version, and you are good to go (even without restarting SharpDevelop, we perform the "SHFB installed?" check on the fly): Note that we produce a valid .shfbproj file with a reference to the project you just had open. So why are we shipping some stuff in the box and some not? That mostly depends on how deeply integrated a feature is in the IDE (well, after all that is short for integrated development environment). We have to have control over certain tools and the version being used. In some cases we can leave it up to the user to install it if needed, like F# support, Subversion support, FxCop or StyleCop support, or now documentation generation. Lean & mean is the new green. [Less]

SharpDevelop wraps F# Interactive (fsi.exe) in a pad of its own. For SharpDevelop 3.2, it looks like this: You type the code you want to evaluate in a single-line textbox on top of the fsi.exe output. With revision 5498 (part of SharpDevelop ... [More] 4.0), Daniel reused Siegfried's approach for the debugger console to make F# Interactive a lot more compelling: You type right inside REPL. Way more useful! Boot note: In revision 5494, we ported the F# backend binding from F# (yes, the F# binding was written in F#) to C#. The main reason was that requiring F# - which is not part of the basic .NET installation - caused us problems (again) with the automated build. [Less]

For those of you that haven't followed the development of SDR in the past, a quick introduction on how to get started. There is a Wiki dedicated to SDR: http://sharpdevelopreports.net/ (please note that it hasn't been updated yet for the fact that ... [More] SDR is now back in the fold with SharpDevelop) It contains a feature tour (with screenshots) to give you an idea how to get up and running quickly. I'd also recommend reading the what's new blog post from the SDR beta, as it contains information on the newly added functionality (such as expression support). Speaking of support: there is a dedicated forum for SDR on our community site, please let me know about problems, ideas, fixes et al there! [Less]

As of today, SharpDevelop Reports (SDR) is once again an integral part of SharpDevelop! It will be shipped with SharpDevelop 3.2 (~spring 2010), but it is already available on the build server as part of the SharpDevelop integration builds. Please ... [More] note that the standalone designer build is no longer available on the build server. Sample reports can be found in the source download of SharpDevelop in the folder Samples\SharpDevelopReports. Upcoming changes before the CTP of SharpDevelop 3.2: iTextSharp will be updated to version 5.0, and we no longer include the source code for it in the repository (only as a zip in the vendor directory, which is not part of the source download). Next tasks: more samples, more documentation, bug fixing. [Less]

Support for IronRuby in SharpDevelop has moved on since the last alpha release of the IronRuby addin. This addin now ships with SharpDevelop 3.2 which is available to download from the build server. The main new features are ... [More] support for IronRuby 1.0 RC 1 and the ability to debug IronRuby applications. New Features Windows Forms designer support now complete Converting entire C# and VB.NET projects to IronRuby. Debugger support for IronRuby applications. Smart indenting for IronRuby code. IronRuby 1.0 RC 1 support. Currently there is no support for IronRuby code completion. Now we will take a look at some of the new features in more depth. Running an IronRuby Application After you create an IronRuby application you can run it immediately without having to edit the project options as you did previously. The project templates have been updated so that everything is ready to go straight away. Simply select Run from the Debug menu to run your application with the IronRuby console. Debugging an IronRuby Application In order to get the debugger to work well when debugging an IronRuby application you should change the debugger options. To open the debugger options select Options from the Tools menu, then select the Debugging category. Only the 'Just My Code' feature should be selected and everything else should be unselected, as shown in the screenshot below. You can set your breakpoints in the normal way either by clicking in the left hand margin of the text editor or by selecting Toggle Breakpoint from the Debug menu. Selecting Run from the Debug menu will run your IronRuby application under the debugger. Alternatively you can select Run from the Ruby menu which will run the code currently active text editor window. Selecting either of these will run the IronRuby console in debug mode with SharpDevelop's debugger. Converting a C# or VB.NET Project to IronRuby To convert a VB.NET or C# project to IronRuby open the project and then select Convert from C# to Ruby or Convert from VB.NET to Ruby from the Project menu. Extra Ruby Libraries The IronRuby 1.0 RC 1 download from codeplex includes extra Ruby libraries that are not shipping with SharpDevelop. If you want to use these libraries then download the IronRuby zip file and copy the lib folder to the IronRuby addin folder: C:\Program Files\SharpDevelop\3.0\AddIns\AddIns\BackendBindings\RubyBinding The IronRuby console (ir.exe) is configured to look in the lib subfolder by information in the ir.exe.config file: <options> <set language='Ruby' option='LibraryPaths' value='lib\IronRuby;lib\Ruby\site_ruby\1.8;lib\Ruby\site_ruby;lib\Ruby\1.8'/> </options> If you want to put these Ruby libraries somewhere else then the ir.exe.config file should be modified. IronRuby Downloads IronRuby 1.0 RC 1 from Codeplex [Less]

Features: The Designer is using the infrastructure from Windows.Forms.Designer Run Expressions inside a Report; based on the work of  Irony and Simpleexpressionevaluator UnitTests for many  (increasing number) of Classes The Designer in ... [More] Action:  TextEditor, useful to enter some text and/or expressions: A very simple report in List layout with PageNumber in the PageFooter section and Aggregate function count() in ReportFooter: Some more functions:Line 1 (middle):   nothing to evaluate – (right) concat two fieldsLine2 (middle and right):  UserfunctionsLine 3 (middle and right) : GlobalfunctionsLine 4 :     show parameters inside report, useful for queriesLine 5:     simple calculationLine 6:     etc, some more functions  The Result: [Less]

Support for IronRuby 0.9.1 is now available for SharpDevelop 3.1. The IronRuby addin is an early alpha preview release/proof of concept and is not an official part of SharpDevelop 3.1 so it is available as a separate download ... [More] at the end of this post. Features Code folding Syntax highlighting File and project templates for Console and Windows Forms applications Windows Forms designer (limited) C# and VB.NET code conversion to Ruby (limited) Please note that the forms designer and code conversion need a lot more work. Creating a Windows Application Open up the new project dialog by selecting New then Solution from the File menu. Selecting the Ruby category will show two project templates. One will create a Windows console application and the other will create a Windows Forms application. To run your application ensure the Program.rb file is in the active text editor window then select Run from the Ruby menu. This will run your code with the IronRuby console (ir.exe). Alternatively you can run the application by selecting Run from the Debug menu but you will first need to configure the project options. Select Project Options from the Project menu to open up the Debug project options. You will need to add ${ProjectDir} to the command line arguments and working directory as shown above. The -19 command line argument is used to enable Ruby 1.9 support otherwise the IronRuby console will not be able to load any UTF-8 source code files. Currently you cannot debug your code even if the -D command line argument is specified. If you are running a windows app and nothing seems to happen then open a command line window and run it from there. This way you should see any errors reported from the IronRuby console. Designing Windows Forms The Windows Forms designer is still in its early stages so please be warned that it may break the form's code or worse. The designer code generation is a lot more complete than the designer loader so the designer will most likely fail to load all controls into the designer. The designer can be opened in the usual way by opening the form in the text editor and selecting the Design tab at the bottom of the text editor. Once open in the designer you can add controls to the form in the usual way from the Tools window. In the screenshot below a label, text box and a button have been added. Click the Source tab to view the generated code in the InitializeComponents method. Make sure you do this before trying to save the code. Code Folding Code folding allows you to collapse regions of a class. Code Conversion To convert VB.NET or C# to Ruby open the file you want to convert and then select Convert code to Ruby from the Tools menu. The code conversion is limited to classes so it will not convert an arbitary piece of code that is not inside a class. A C# class being converted to Ruby is shown below. The code conversion is still at an early stage of development so it will fail on complicated classes. Class View Classes in the open solution will be displayed in the Class browser (Select Classes from the View menu). From there you can double click a class or method and the text editor will display the corresponding code. Installing the IronRuby AddIn Rename the IronRubyAddIn-0.1.zip file to IronRubyAddIn-0.1.sdaddin. From the Tools menu select AddIn Manager . Click the Install AddIn button. In the Open File Dialog browse to the IronRubyAddIn-0.1.sdaddin file and click the Open button. Click the Close button. Restart SharpDevelop. Ruby Links Some of the Ruby tutorials and links used whilst creating the IronRuby addin. Ruby documentation. Book of Ruby by Huw Collingbourne. IronRuby homepage. Downloads IronRubyAddIn0.1.zip IronRubyAddIn0.1-src.zip [Less]