Before you start to work on an existing issue, check if it is not assigned to anyone yet, and if it is, talk to that person. Even better, make them in the form of pull requests. Bug reports that include steps-to-reproduce (including code) are preferred. Questions, comments, bug reports, and pull requests are all welcome. Then add a reference to CodeCracker.dll from within the Analyzers node inside References, in Visual Studio. To install from Nuget, for the C# version: If you want to be able to configure which analyzers are being used in your project, and which ones you will ignore, and commit those changes to source control and share with your team, then you also want the Nuget package. The package is available on nuget ( C#, VB). If you want the analyzers to work during your build, and generate warnings and errors during the build, also on build servers, then you want to use the Nuget package. The way you want to use it depends on the scenario you are working on. You may use CodeCracker in two ways: as an analyzer library that you install with Nuget into your project or as a Visual Studio extension. No money shall be charged by this software, nor it will be. Everyone is invited to contribute, fork, share and use the code. This is a community project, free and open source. There you will find information on how to contribute, our task board, definition of done, definition of ready, etc. An analyzer library for C# and VB that uses Roslyn to produce refactorings, code analysis, and other niceties.Ĭheck the official project site on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |