SharpDevelop

Daniel has created a NuGet package "of" ILSpy - the decompiler engine. It is based off of the 2.3 release, and we want your feedback before officially calling it done in the 2.4 release (and yes, there is no getting started sample, ILSpy doesn't ... [More] exactly count as that...). One important note: ILSpy builds against the source code versions of NRefactory and Cecil (the former needs customizations of the latter). The decompiler NuGet package is built against the official binaries of those two. That is just fine, because the customizations do not matter for the decompiler itself. Just wanted to make this clear because issue #573 refers to the initial problems we had with packaging it in a way so you can use NR and Decompiler both in the same project without versioning issues. [Less]

Daniel has created a NuGet package "of" ILSpy - the decompiler engine. It is based off of the 2.3 release, and we want your feedback before officially calling it done in the 2.4 release (and yes, there is no getting started sample, ILSpy doesn't ... [More] exactly count as that...). One important note: ILSpy builds against the source code versions of NRefactory and Cecil (the former needs customizations of the latter). The decompiler NuGet package is built against the official binaries of those two. That is just fine, because the customizations do not matter for the decompiler itself. Just wanted to make this clear because issue #573 refers to the initial problems we had with packaging it in a way so you can use NR and Decompiler both in the same project without versioning issues. [Less]

Even if NR6Pack already brings more than 150 C# analyzers and refactorings from NRefactory to Visual Studio: There are still many more, which haven't been ported to Roslyn yet. Therefore we invite developers to "adopt" unported code issues and help ... [More] us with extending NR6Pack with new cool features! What do you need to participate? Have a look at our list of unported code actions and issues. Especially interesting items are marked in bold. If possible, please prefer one of these. Check if somebody has already created a GitHub issue for porting your chosen item. If no GitHub issue exists, please add one (something like "Port of Issue to Roslyn") and assign it to yourself. If it already exists, but has no assignee, feel free to take it over. Start porting :-)Integration of analyzers has been described here. Unported code issues are already part of ICSharpCode.NRefactory6.CSharp.Refactoring project, but they still need to be linked into NR6Pack project additionally. Unported code issues always contain their old code (based on NRefactory 5) as comment. So porting means understanding that code and reimplementing it with Roslyn API. You can use other finished analyzers and refactorings as orientation. Don't forget to reactivate the appopriate unit test, too! Tests of inactive refactorings are currently marked as "Ignore". Unit tests are very helpful anyway for understanding how a refactoring should behave and for later testing of your work. Finally create a GitHub push request with your changes. We will review and merge it, if it's alright. We're looking forward to your collaboration! And if you have more questions, please ask them in our forum or on GitHub. [Less]

Even if NR6Pack already brings more than 150 C# analyzers and refactorings from NRefactory to Visual Studio: There are still many more, which haven't been ported to Roslyn yet. Therefore we invite developers to "adopt" unported code issues and help ... [More] us with extending NR6Pack with new cool features! What do you need to participate? Have a look at our list of unported code actions and issues. Especially interesting items are marked in bold. If possible, please prefer one of these. Check if somebody has already created a GitHub issue for porting your chosen item. If no GitHub issue exists, please add one (something like "Port of <XYZ>Issue to Roslyn") and assign it to yourself. If it already exists, but has no assignee, feel free to take it over. Start porting :-)Integration of analyzers has been described here. Unported code issues are already part of ICSharpCode.NRefactory6.CSharp.Refactoring project, but they still need to be linked into NR6Pack project additionally. Unported code issues always contain their old code (based on NRefactory 5) as comment. So porting means understanding that code and reimplementing it with Roslyn API. You can use other finished analyzers and refactorings as orientation. Don't forget to reactivate the appopriate unit test, too! Tests of inactive refactorings are currently marked as "Ignore". Unit tests are very helpful anyway for understanding how a refactoring should behave and for later testing of your work. Finally create a GitHub push request with your changes. We will review and merge it, if it's alright. We're looking forward to your collaboration! And if you have more questions, please ask them in our forum or on GitHub. [Less]

Even if NR6Pack already brings more than 150 C# analyzers and refactorings from NRefactory to Visual Studio: There are still many more, which haven't been ported to Roslyn yet. Therefore we invite developers to "adopt" unported code issues and help ... [More] us with extending NR6Pack with new cool features! What do you need to participate? Have a look at our list of unported code actions and issues. Especially interesting items are marked in bold. If possible, please prefer one of these. Check if somebody has already created a GitHub issue for porting your chosen item. If no GitHub issue exists, please add one (something like "Port of Issue to Roslyn") and assign it to yourself. If it already exists, but has no assignee, feel free to take it over. Start porting :-)Integration of analyzers has been described here. Unported code issues are already part of ICSharpCode.NRefactory6.CSharp.Refactoring project, but they still need to be linked into NR6Pack project additionally. Unported code issues always contain their old code (based on NRefactory 5) as comment. So porting means understanding that code and reimplementing it with Roslyn API. You can use other finished analyzers and refactorings as orientation. Don't forget to reactivate the appopriate unit test, too! Tests of inactive refactorings are currently marked as "Ignore". Unit tests are very helpful anyway for understanding how a refactoring should behave and for later testing of your work. Finally create a GitHub push request with your changes. We will review and merge it, if it's alright. We're looking forward to your collaboration! And if you have more questions, please ask them in our forum or on GitHub. [Less]

UPDATE 2015-04-29:The extension described here has been removed. For more details please see this post.   As a little helpful supplement to my last post we have released the new extension "NRefactory Issue & Action Templates for Developers" on ... [More] Visual Studio Gallery: It's purpose: Allowing developers to quickly start with their own code refactoring or analyzer for NRefactory or NR6Pack. The templates include all the basic glue code for you, so you just need to continue with your logic. After installing the extension (available for Visual Studio 2013 and 2015), you will see a new directory "NRefactory" in your C# templates, when opening the "Add New Item" dialog:   The template uses the chosen class name as basis for your action/issue:   Please note that these templates are only intended for analyzer implementation based on NRefactory 6! [Less]

UPDATE 2015-04-29:The extension described here has been removed. For more details please see this post.   As a little helpful supplement to my last post we have released the new extension "NRefactory Issue & Action Templates for Developers" on ... [More] Visual Studio Gallery: It's purpose: Allowing developers to quickly start with their own code refactoring or analyzer for NRefactory or NR6Pack. The templates include all the basic glue code for you, so you just need to continue with your logic. After installing the extension (available for Visual Studio 2013 and 2015), you will see a new directory "NRefactory" in your C# templates, when opening the "Add New Item" dialog:   The template uses the chosen class name as basis for your action/issue:   Please note that these templates are only intended for analyzer implementation based on NRefactory 6! [Less]

UPDATE 2015-04-29:The extension described here has been removed. For more details please see this post.   As a little helpful supplement to my last post we have released the new extension "NRefactory Issue & Action Templates for Developers" on ... [More] Visual Studio Gallery: It's purpose: Allowing developers to quickly start with their own code refactoring or analyzer for NRefactory or NR6Pack. The templates include all the basic glue code for you, so you just need to continue with your logic. After installing the extension (available for Visual Studio 2013 and 2015), you will see a new directory "NRefactory" in your C# templates, when opening the "Add New Item" dialog:   The template uses the chosen class name as basis for your action/issue:   Please note that these templates are only intended for analyzer implementation based on NRefactory 6! [Less]

As a little helpful supplement to my last post we have released the new extension "NRefactory Issue & Action Templates for Developers" on Visual Studio Gallery: It's purpose: Allowing developers to quickly start with their own code refactoring ... [More] or analyzer for NRefactory or NR6Pack. The templates include all the basic glue code for you, so you just need to continue with your logic. After installing the extension (available for Visual Studio 2013 and 2015), you will see a new directory "NRefactory" in your C# templates, when opening the "Add New Item" dialog:   The template uses the chosen class name as basis for your action/issue:   Please note that these templates are only intended for analyzer implementation based on NRefactory 6! [Less]

UPDATE 2015-04-29:The extension described here has been removed. For more details please see this post.   As a little helpful supplement to my last post we have released the new extension "NRefactory Issue & Action Templates for Developers" on ... [More] Visual Studio Gallery: It's purpose: Allowing developers to quickly start with their own code refactoring or analyzer for NRefactory or NR6Pack. The templates include all the basic glue code for you, so you just need to continue with your logic. After installing the extension (available for Visual Studio 2013 and 2015), you will see a new directory "NRefactory" in your C# templates, when opening the "Add New Item" dialog:   The template uses the chosen class name as basis for your action/issue:   Please note that these templates are only intended for analyzer implementation based on NRefactory 6! [Less]