The #develop teamblog
#  Monday, 27 September 2004
  • SD-209 "Folding inconsistency"
  • SD-241 "Code generation doesn't work for own classes"
  • SD-218 "Undo form designer operations in code"
  • SD-244 "Code completion is not working inside ELSE clause"

In other change news: Daniel improved the VS.NET project exporter (more properties are exported, project references and assembly references are exported) as well as the importer (treat warnings as errors is now imported correctly, .csproj & .vbproj types are now shown in the import dialog)

Monday, 27 September 2004 06:45:32 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


#  Friday, 24 September 2004
  • SD-243 "Code completion overload insight window scroll arrows not working"
  • SD-229 "Horizontal scroll bar too sensitive"
  • SD-186 "Permission problem in VS.NET importer"
  • SD-239 "Auto code generation exception"
  • SD-242 "Switching File Mode to VS-C# from C#, quotes will "vanish""
Categories: Chris
Friday, 24 September 2004 06:52:13 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


#  Thursday, 23 September 2004

Quite some lively discussion of this question is going on at Contributions cover the entire range from pro to contra, and astonishingly, very few posts are flame bait. Worth reading, whatever your attitude towards the topic may be.

And another topic related to Open Source is the change of licensing recently undergone by SpamAssassin. This was a long and painful process - more than 100 developers and contributors needed to be contacted and convinced to assign copyright to the project before the licensing change was made. We here at #develop ask for a Joint Copyright Assignment from all contributors since inception of the project. This episode now shows that our doing so provides other benefits besides those outlined in our wiki. Note to all out there who consider an Open Source project: think of copyright and attribution issues even before you start your project. Later modifications *are painful*.

Categories: Bernd
Thursday, 23 September 2004 10:29:51 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


  • SD-224 "Destructors can't be folded"
  • SD-232 "Toolbox Scrollbars"
  • SD-236 "Code generation list has duplicate entries"
Categories: Chris
Thursday, 23 September 2004 06:33:17 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


#  Wednesday, 22 September 2004
  • SD-238 "WinForms template namespace issue"
  • SD-231 "Save / Save All commands context sensitive"
  • SD-225 "Endless loop: folding invalid nested classed"
  • SD-184 "Update Tracker to Gemini 1.7"
Categories: Chris
Wednesday, 22 September 2004 08:46:37 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


Currently I'm working with Andrea on NRefactory (name may change) which is a merge of #Refactory and VBRefactory. No longer do we need to maintain two different abstract syntax trees or different parser related code. In the past maintenance was an error prone process because each bugfix or enhancement needed to be ported to the other parser layer. Now we're merging VB and C# parsing and have only one representation for the source code. That will prevent many bugs. NRefactory will have a good unit test suite which will ensure that we're not going to break much during code refactoring and future maintenance.
Categories: Mike
Wednesday, 22 September 2004 07:34:03 (GMT Daylight Time, UTC+01:00)  #    Comments [1]


#  Tuesday, 21 September 2004

Our bug tracker is now updated to Gemini v1.7.1. In the course of this update I also put the user documentation of Gemini online - if you are interested, read the PDF document.

Categories: Chris
Tuesday, 21 September 2004 20:02:36 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


Part of my job as Senior Project Wrangler encompasses "evangelizing" team members on certain aspects of development / project management. One area that we try hard to get right is the user interface; not that this would be easy (or popular in the team) as can be read in the article Why Free Software usability tends to suck.

Categories: Chris
Tuesday, 21 September 2004 19:07:55 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


#  Friday, 17 September 2004

I'm currently working on an addin that integrates a shell window into SharpDevelop. Basically it's a port of the "Console" project  ( to ManagedC++ with some modifcations.

It's not polished for release yet, still somewhat buggy and unstable. Expect a sneak peek within the next few weeks.

A screenshot showing the addin in action:

Categories: Markus
Friday, 17 September 2004 23:54:48 (GMT Daylight Time, UTC+01:00)  #    Comments [0]


#  Wednesday, 15 September 2004

In revision 1554, the src\3rdParty directory was deleted. It was added when we experimentally integrated the Dr. C# addin, but had to remove it later on because it wasn't maintained. What stayed around till that revision was the directory where it lived.

Last week, I had a discussion about repopulating that directory with a third party addin. Various good reasons why to add that specific addin to the distribution exist, but in the course of the discussion (which really forced me to rethink that third party source directory "feature") I found out that having tightly integrated third party addins in our codebase / distribution is no good idea:

  • The need to sync the codebase in our src\3rdParty directory with the repository of the actual addin project (which might be developed on a different schedule). This also means that the burden of integration testing is upon us.
  • Support issues. If you have an addin that almost perfectly blends into the #develop user experience so it looks like a stock feature, users will report bugs to us automatically. Or post feature requests to us. Users don't see where an addin is loaded from, they don't care.
  • Linked to support issues is code quality. We don't intend to review someone else's code if it meets certain standards, less to speak if it hypothetically contains exploitable or even malicious code. A liability issue that we do not want to get into.
  • Maintainance. Programmers don't necessarily maintain their addin forever, it might get abandoned. We are then faced with two options - take ownership or remove the feature. Both options are not feasible - for one, we might not know the inner workings at all which makes it extremely time consuming, or secondly, having to explain to users why a feature they (potentially) loved was kicked out.

For these reasons, we decided to remove that directory and continue to stick with our policy: our repository contains only our code (exceptions: non-addin libraries and build tools), and our distribution of #develop only contains addins that are maintained by us. This way we avoid those sticky issues.

Categories: Chris
Wednesday, 15 September 2004 18:34:16 (GMT Daylight Time, UTC+01:00)  #    Comments [2]


© Copyright 2016 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.