"drop in distribution" is perhaps slightly off ? #86
                  
                    
                      Danielovich
                    
                  
                
                  started this conversation in
                General
              
            Replies: 1 comment
-
| 
         Hi @Danielovich, Usually on our projects we use the https://github.com/atc-net/atc-coding-rules-updater with a configurable json file, and a script, so we can get newest coding-rules and update analyzers aswell. See this sample: https://github.com/atc-net/atc-coding-rules-updater/tree/main/sample  | 
  
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
These rules are next to none, but I came across the documentation and that seems a bit off ?
"Take a copy of the distribution folder and drop it into the root of a project."
Before I contribute to the readme I wanted to make sure what exactly it takes for a user who wish to use the rules in their existing codebase.
Personally I take the
global.json
BuildProps
editorconfig
From the possible version scheme (.net X | project type) in the distribution folder.
And place them in the root (where .sln is) folder. Then the magic happens.
Is this not the inteded use for existing codebases which might not follow the src, test pattern ?
All the best,
Daniel
Beta Was this translation helpful? Give feedback.
All reactions