SharpDevelop

tl;dr get it here Remember the 5.0 release blog post for SharpDevelop? We promised to do interesting things in our ecosystem, and now the first deliverable has landed - a Visual Studio extension for ILSpy. Now, this is a v1. This means we provided ... [More] functionality that is simple, yet useful: Open in ILSpy for referenced assemblies. This might not seem huge, but hey, did you have to install ILSpy for getting decompilation support? No. It was shipped in the box (vsix). And this way we will keep it updated in the future when additional features for the extension ship. And here's the challenge for our community: what features would you like to see? What priority would you give that feature (or is it only nice to have)? Bonus points for including the scenario why this is important to you! [Less]

tl;dr get it here Remember the 5.0 release blog post for SharpDevelop? We promised to do interesting things in our ecosystem, and now the first deliverable has landed - a Visual Studio extension for ILSpy. Now, this is a v1. This means we provided ... [More] functionality that is simple, yet useful: Open in ILSpy for referenced assemblies. This might not seem huge, but hey, did you have to install ILSpy for getting decompilation support? No. It was shipped in the box (vsix). And this way we will keep it updated in the future when additional features for the extension ship. And here's the challenge for our community: what features would you like to see? What priority would you give that feature (or is it only nice to have)? Bonus points for including the scenario why this is important to you! [Less]

tl;dr get it here Remember the 5.0 release blog post for SharpDevelop? We promised to do interesting things in our ecosystem, and now the first deliverable has landed - a Visual Studio extension for ILSpy. Now, this is a v1. This means we provided ... [More] functionality that is simple, yet useful: Open in ILSpy for referenced assemblies. This might not seem huge, but hey, did you have to install ILSpy for getting decompilation support? No. It was shipped in the box (vsix). And this way we will keep it updated in the future when additional features for the extension ship. And here's the challenge for our community: what features would you like to see? What priority would you give that feature (or is it only nice to have)? Bonus points for including the scenario why this is important to you! [Less]

After five Betas and one RC we are finally hitting release for SharpDevelop 5.0. Here is a recap of some of the most important features and changes from the various development stages (in short): SD5 only supports C#. If you need VB.NET (or IP and ... [More] IR respectively), please stick with version 4.4. The rewrite of NRefactory was the big-ticket item of this release, and supporting one language was huge already. SD5 is licensed under MIT, instead of LGPL. SD5 has ILSpy debugging integrated into the IDE. Loads of "smaller" improvements. Please see my posts in the what's new series, search grouping, go to definition improvements, a new addin manager and how to publish your own addin, class browser goodies, the new resource editor, member hierarchy navigation and many, many more. Item #1 in this list definitely begs the question "What about VB.NET?" I'd like to extend this question to "What's in the future of SharpDevelop?" We have componentized SharpDevelop intentionally for what is coming now - the as-of-today core team moving to specific areas of our ecosystem. Think ILSpy. Think AvalonEdit. Yes, this means that the IDE iself is going to take a back seat. There are a couple of reasons for this decision, ranging from something as simple as time constraints (we are after all a spare-time post-day-job operation - some people call this "life"), to uptake of the various projects (ILSpy is very popular, even when competing against "free as in beer" offerings - can't exactly say that for SharpDevelop) as well as next-to-non-existent influx of new development talent (writing tooling is way uncooler than writing libraries, take a look around). Long story short - SharpDevelop is far from "done" (we'd never claim that), but we (the current core team) are realigning our efforts for visibility in the near term. This does not mean SharpDevelop is on "life support" or "dead". It means that bug fixing, small improvements and minor features have priority. Big shiny new things are up to contributions which we are more than happy to accept and help with, simply ping us on the developer mailing list to get started. Like the post title says: 5.0 final, and not the final version of SharpDevelop. But we wanted to be open and up front about what level of development pace you as our valued customers can expect. [Less]

After five Betas and one RC we are finally hitting release for SharpDevelop 5.0. Here is a recap of some of the most important features and changes from the various development stages (in short): SD5 only supports C#. If you need VB.NET (or IP and ... [More] IR respectively), please stick with version 4.4. The rewrite of NRefactory was the big-ticket item of this release, and supporting one language was huge already. SD5 is licensed under MIT, instead of LGPL. SD5 has ILSpy debugging integrated into the IDE. Loads of "smaller" improvements. Please see my posts in the what's new series, search grouping, go to definition improvements, a new addin manager and how to publish your own addin, class browser goodies, the new resource editor, member hierarchy navigation and many, many more. Item #1 in this list definitely begs the question "What about VB.NET?" I'd like to extend this question to "What's in the future of SharpDevelop?" We have componentized SharpDevelop intentionally for what is coming now - the as-of-today core team moving to specific areas of our ecosystem. Think ILSpy. Think AvalonEdit. Yes, this means that the IDE iself is going to take a back seat. There are a couple of reasons for this decision, ranging from something as simple as time constraints (we are after all a spare-time post-day-job operation - some people call this "life"), to uptake of the various projects (ILSpy is very popular, even when competing against "free as in beer" offerings - can't exactly say that for SharpDevelop) as well as next-to-non-existent influx of new development talent (writing tooling is way uncooler than writing libraries, take a look around). Long story short - SharpDevelop is far from "done" (we'd never claim that), but we (the current core team) are realigning our efforts for visibility in the near term. This does not mean SharpDevelop is on "life support" or "dead". It means that bug fixing, small improvements and minor features have priority. Big shiny new things are up to contributions which we are more than happy to accept and help with, simply ping us on the developer mailing list to get started. Like the post title says: 5.0 final, and not the final version of SharpDevelop. But we wanted to be open and up front about what level of development pace you as our valued customers can expect. [Less]

After five Betas and one RC we are finally hitting release for SharpDevelop 5.0. Here is a recap of some of the most important features and changes from the various development stages (in short): SD5 only supports C#. If you need VB.NET (or IP and ... [More] IR respectively), please stick with version 4.4. The rewrite of NRefactory was the big-ticket item of this release, and supporting one language was huge already. SD5 is licensed under MIT, instead of LGPL. SD5 has ILSpy debugging integrated into the IDE. Loads of "smaller" improvements. Please see my posts in the what's new series, search grouping, go to definition improvements, a new addin manager and how to publish your own addin, class browser goodies, the new resource editor, member hierarchy navigation and many, many more. Item #1 in this list definitely begs the question "What about VB.NET?" I'd like to extend this question to "What's in the future of SharpDevelop?" We have componentized SharpDevelop intentionally for what is coming now - the as-of-today core team moving to specific areas of our ecosystem. Think ILSpy. Think AvalonEdit. Yes, this means that the IDE iself is going to take a back seat. There are a couple of reasons for this decision, ranging from something as simple as time constraints (we are after all a spare-time post-day-job operation - some people call this "life"), to uptake of the various projects (ILSpy is very popular, even when competing against "free as in beer" offerings - can't exactly say that for SharpDevelop) as well as next-to-non-existent influx of new development talent (writing tooling is way uncooler than writing libraries, take a look around). Long story short - SharpDevelop is far from "done" (we'd never claim that), but we (the current core team) are realigning our efforts for visibility in the near term. This does not mean SharpDevelop is on "life support" or "dead". It means that bug fixing, small improvements and minor features have priority. Big shiny new things are up to contributions which we are more than happy to accept and help with, simply ping us on the developer mailing list to get started. Like the post title says: 5.0 final, and not the final version of SharpDevelop. But we wanted to be open and up front about what level of development pace you as our valued customers can expect. [Less]

Since SharpDevelop 4 you should already be familiar with the key shortcut F6 or the context menu entry "Find derived symbols" on members and types: When called on a type, it shows a popup with all types deriving from it (or for interfaces: ... [More] implementing that interface) and allows to navigate to them. When called on a virtual or interface member, a popup with overriding or implementing members will appear:   With the new SharpDevelop 5 RC the same is possible in the opposite direction: "Find base symbols" (previously "Find base classes") is now working on class members, too: Called on a virtual/override member it will show base members:   The same is possible for interface members, that have been implemented by selected member:   The new shortcut Ctrl+F6 can be used as well. This feature should make it much easier to navigate in your project. [Less]

Since SharpDevelop 4 you should already be familiar with the key shortcut F6 or the context menu entry "Find derived symbols" on members and types: When called on a type, it shows a popup with all types deriving from it (or for interfaces: ... [More] implementing that interface) and allows to navigate to them. When called on a virtual or interface member, a popup with overriding or implementing members will appear:   With the new SharpDevelop 5 RC the same is possible in the opposite direction: "Find base symbols" (previously "Find base classes") is now working on class members, too: Called on a virtual/override member it will show base members:   The same is possible for interface members, that have been implemented by selected member:   The new shortcut Ctrl+F6 can be used as well. This feature should make it much easier to navigate in your project. [Less]

Since SharpDevelop 4 you should already be familiar with the key shortcut F6 or the context menu entry "Find derived symbols" on members and types: When called on a type, it shows a popup with all types deriving from it (or for interfaces: ... [More] implementing that interface) and allows to navigate to them. When called on a virtual or interface member, a popup with overriding or implementing members will appear:   With the new SharpDevelop 5 RC the same is possible in the opposite direction: "Find base symbols" (previously "Find base classes") is now working on class members, too: Called on a virtual/override member it will show base members:   The same is possible for interface members, that have been implemented by selected member:   The new shortcut Ctrl+F6 can be used as well. This feature should make it much easier to navigate in your project. [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]