This is a low priority issue, if you want to work on it please read the comments
CodeCracker is bringing together tens of different analyzers and refactorings and very soon it will gather hundreds. Not everyone will want to use all of them. This issue focuses on allowing the user to choose whatever combination of analyzers and refactorings they want and generate a custom package. A plus would be to publish that to nuget so they can use that directly on their project without the need to download, and if a combination already exists point them to an existing package.
We could build something like the Jquery UI download builder.
We don't have any idea on how to do that yet, so we need to discuss it. We could probably work with csc or msbuild directly to build an exact package combination. We would also need to work on the isolation of the analyzers and refactorings, so they can be used without depending on each others. And this all needs to be testable.
This issue is made harder by the fact that we do not yet have a build server.
Ideas are welcome and needed. This issue is first an invitation to discussion, and, after we decide on a strategy, it will become the actual implementation of the chosen strategy. So, please, brainstorm!
This is a low priority issue, if you want to work on it please read the comments
CodeCracker is bringing together tens of different analyzers and refactorings and very soon it will gather hundreds. Not everyone will want to use all of them. This issue focuses on allowing the user to choose whatever combination of analyzers and refactorings they want and generate a custom package. A plus would be to publish that to nuget so they can use that directly on their project without the need to download, and if a combination already exists point them to an existing package.
We could build something like the Jquery UI download builder.
We don't have any idea on how to do that yet, so we need to discuss it. We could probably work with
cscormsbuilddirectly to build an exact package combination. We would also need to work on the isolation of the analyzers and refactorings, so they can be used without depending on each others. And this all needs to be testable.This issue is made harder by the fact that we do not yet have a build server.
Ideas are welcome and needed. This issue is first an invitation to discussion, and, after we decide on a strategy, it will become the actual implementation of the chosen strategy. So, please, brainstorm!