SharpDevelop

Since we have recently changed management of resources in SharpDevelop project, our good old WinForms-based ResourceEditor needed a review. So we chose rewriting its UI in WPF to implement a better architecture and solve some focusing issues:   ... [More] Basically our editor for *.resx files works in the same manner as before: You can add new string resources or load image resources from external files through context menu. Cut/Copy/Paste resource items, even between two open resource files. Edit contents of a resource item by selecting it and using the view area below the list. Edit comments for resource items (through context menu) But there is one new helpful feature: Now you are able to filter the list using the text field at the top:   After pressing Enter key or clicking the "Update" button the filter text is applied to list. When pressing Escape key in the text field, current filter is reset. Now it should be much easier to work with big resource files. [Less]

Since we have recently changed management of resources in SharpDevelop project, our good old WinForms-based ResourceEditor needed a review. So we chose rewriting its UI in WPF to implement a better architecture and solve some focusing issues:   ... [More] Basically our editor for *.resx files works in the same manner as before: You can add new string resources or load image resources from external files through context menu. Cut/Copy/Paste resource items, even between two open resource files. Edit contents of a resource item by selecting it and using the view area below the list. Edit comments for resource items (through context menu) But there is one new helpful feature: Now you are able to filter the list using the text field at the top:   After pressing Enter key or clicking the "Update" button the filter text is applied to list. When pressing Escape key in the text field, current filter is reset. Now it should be much easier to work with big resource files. [Less]

Debugging exceptions in async methods can be quite difficult as exceptions are automatically caught and rethrown once the Task finishes executing. This leads to the problem that you end up with a stack trace missing important information about where ... [More] and why the exception was thrown. A possible solution to this is to simply let the debugger break on any exception that is thrown in your code, even if it's handled later on. Now, that's nothing new. The "Pause on handled exceptions" feature was introduced in SharpDevelop 4. The news is that you can choose which exceptions you want to break on and which you want to ignore: You can add any exception you either want to break on or want to ignore. The example shown above simply means: Break on any exception derived from System.Exception, that is, every exception except System.OperationCanceledException (and any exceptions derived from OperationCanceledException). But, if you don't want to enter all the exceptions manually, you can ignore them while debugging a program: Just uncheck the box and click continue. The debugger will never break on a handled exception of that type again. Of course, you can re-enable ignored exceptions by editing the list at any time. [Less]

Debugging exceptions in async methods can be quite difficult as exceptions are automatically caught and rethrown once the Task finishes executing. This leads to the problem that you end up with a stack trace missing important information about where ... [More] and why the exception was thrown. A possible solution to this is to simply let the debugger break on any exception that is thrown in your code, even if it's handled later on. Now, that's nothing new. The "Pause on handled exceptions" feature was introduced in SharpDevelop 4. The news is that you can choose which exceptions you want to break on and which you want to ignore: You can add any exception you either want to break on or want to ignore. The example shown above simply means: Break on any exception derived from System.Exception, that is, every exception except System.OperationCanceledException (and any exceptions derived from OperationCanceledException). But, if you don't want to enter all the exceptions manually, you can ignore them while debugging a program: Just uncheck the box and click continue. The debugger will never break on a handled exception of that type again. Of course, you can re-enable ignored exceptions by editing the list at any time. [Less]

Debugging exceptions in async methods can be quite difficult as exceptions are automatically caught and rethrown once the Task finishes executing. This leads to the problem that you end up with a stack trace missing important information about where ... [More] and why the exception was thrown. A possible solution to this is to simply let the debugger break on any exception that is thrown in your code, even if it's handled later on. Now, that's nothing new. The "Pause on handled exceptions" feature was introduced in SharpDevelop 4. The news is that you can choose which exceptions you want to break on and which you want to ignore: You can add any exception you either want to break on or want to ignore. The example shown above simply means: Break on any exception derived from System.Exception, that is, every exception except System.OperationCanceledException (and any exceptions derived from OperationCanceledException). But, if you don't want to enter all the exceptions manually, you can ignore them while debugging a program: Just uncheck the box and click continue. The debugger will never break on a handled exception of that type again. Of course, you can re-enable ignored exceptions by editing the list at any time. [Less]

With the new translation portal launched, we are now actively looking for additional translators to existing languages (to start with). We have the following languages in the system currently: The figure to the right is the # of missing ... [More] translations - the total number of resource strings is a tad over 5000 for SharpDevelop, so you can see that these languages are all at least half-done. If you want to volunteer your free time to making SharpDevelop fully translated in your language, please send me an email at christoph.wille @ gmail.com (remove the spaces around the @ sign) with your language of choice. Thank you for making SharpDevelop a global IDE! [Less]

With the new translation portal launched, we are now actively looking for additional translators to existing languages (to start with). We have the following languages in the system currently: The figure to the right is the # of missing ... [More] translations - the total number of resource strings is a tad over 5000 for SharpDevelop, so you can see that these languages are all at least half-done. If you want to volunteer your free time to making SharpDevelop fully translated in your language, please send me an email at christoph.wille @ gmail.com (remove the spaces around the @ sign) with your language of choice. Thank you for making SharpDevelop a global IDE! [Less]

With the new translation portal launched, we are now actively looking for additional translators to existing languages (to start with). We have the following languages in the system currently: The figure to the right is the # of missing ... [More] translations - the total number of resource strings is a tad over 5000 for SharpDevelop, so you can see that these languages are all at least half-done. If you want to volunteer your free time to making SharpDevelop fully translated in your language, please send me an email at christoph.wille @ gmail.com (remove the spaces around the @ sign) with your language of choice. Thank you for making SharpDevelop a global IDE! [Less]

We have added a new open-source project to our portfolio - the Resource-First Translations (RFT) application, which provides translators of SharpDevelop with a modern and fast experience for helping us by translating SharpDevelop into a language they ... [More] speak. This new application has a couple of goals (taken from the RFT GH readme): Code-First Developers live in the IDE and work directly with resource files. Source control is the source of truth for resources. Multi-Branch Translations come and go with features being added, modified or removed. Translators should never duplicate work. Multi-File Complex software doesn't ship with a single resource file only. Slice your application into modules and still get the benefits of translating only once. Sync Automatically get the latest resource file checkins to the translators, and the finished translations to the developers or the build servers. Developers work in the environment they are used to - including branching and merging - and translators get a great effortless experience for translating as well as testing translations. If you want to see that for yourself, either Check out the Youtube videos for translators and administrators ...and/or log in to the demo installation we provide (see RFT readme) The demo installation is actually quite interesting as it runs on Azure Websites (SQL Azure, with Web Jobs and SendGrid for email), whereas in contrast our production installation for SharpDevelop runs on a dedicated box at a hosting facility (SQL Server 2012, with standard scheduled tasks and standard SMTP). If you like what you see, feel free to grab a copy and use it for your own purposes! All you basically need is ASP.NET and a SQL Server database to get going. As for grabbing the translated resource files in a real-world project, check out the ResGet integration in SharpDevelop (we don't do build integration). Bootnote: we talked about replacing the old ASP-based application for way too long (a solution I'd never open source simply for being way too ashamed of the code quality). But at least it provided us with a list of things we must have to have a great experience going forward. [Less]

We have added a new open-source project to our portfolio - the Resource-First Translations (RFT) application, which provides translators of SharpDevelop with a modern and fast experience for helping us by translating SharpDevelop into a language they ... [More] speak. This new application has a couple of goals (taken from the RFT GH readme): Code-First Developers live in the IDE and work directly with resource files. Source control is the source of truth for resources. Multi-Branch Translations come and go with features being added, modified or removed. Translators should never duplicate work. Multi-File Complex software doesn't ship with a single resource file only. Slice your application into modules and still get the benefits of translating only once. Sync Automatically get the latest resource file checkins to the translators, and the finished translations to the developers or the build servers. Developers work in the environment they are used to - including branching and merging - and translators get a great effortless experience for translating as well as testing translations. If you want to see that for yourself, either Check out the Youtube videos for translators and administrators ...and/or log in to the demo installation we provide (see RFT readme) The demo installation is actually quite interesting as it runs on Azure Websites (SQL Azure, with Web Jobs and SendGrid for email), whereas in contrast our production installation for SharpDevelop runs on a dedicated box at a hosting facility (SQL Server 2012, with standard scheduled tasks and standard SMTP). If you like what you see, feel free to grab a copy and use it for your own purposes! All you basically need is ASP.NET and a SQL Server database to get going. As for grabbing the translated resource files in a real-world project, check out the ResGet integration in SharpDevelop (we don't do build integration). Bootnote: we talked about replacing the old ASP-based application for way too long (a solution I'd never open source simply for being way too ashamed of the code quality). But at least it provided us with a list of things we must have to have a great experience going forward. [Less]