Litee SolutionCop issues

Litee / SolutionCop

Tool for static analysis of Visual Studio solutions

Apache License 2.0

23 stars 3 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

TreatStyleCopWarningsAsErrors

#45 skurdiukov closed 6 years ago
2
Fixed rule that check StyleCop.MSBuild.targets in project

#44 skurdiukov closed 6 years ago
0
Make addin for Cake

#43 sm-g opened 7 years ago
0
Ignoring development dependency since they are mostly not referenced

#42 skurdiukov closed 7 years ago
0
SameNugetPackages rule ignores Analyzers

#41 imanushin opened 7 years ago
0
Configure AppVeyor to publish NuGet packages

#40 Litee opened 7 years ago
0
Add new rule: all property group should contain

#39 imanushin opened 7 years ago
2
Support $(SolutionDir) variable in project pathes resolving

#38 imanushin opened 7 years ago
0
Configure CI for this project

#37 imanushin closed 7 years ago
1
--build-server-no-success-messages is ignored

#36 imanushin opened 7 years ago
3
Reference xsd schema from generated xml file

#35 imanushin closed 7 years ago
0
Mandatory package rule

#34 imanushin opened 7 years ago
2
Support nuspec file check

#33 imanushin closed 7 years ago
2
Support run on multiple solutions

#32 imanushin opened 7 years ago
2
Check, that nuspec and packages.config has the same versions

#31 imanushin closed 7 years ago
0
Support requiring same version for different packages

#30 imanushin opened 7 years ago
1
Create VSTS marketplace extension

#29 superarchi opened 7 years ago
1
Check referenced assemly versions

#28 imanushin opened 8 years ago
1
Fixed unhandled exception in SameNameForAssemblyAndRootNamespaceRule

#27 skurdiukov closed 8 years ago
1
Validation failed whe assemblyname missing

#26 skurdiukov closed 8 years ago
0
Added sample XSD schema into solution

#25 skurdiukov closed 8 years ago
0
Added Xsd

#24 skurdiukov closed 8 years ago
0
Threat each rule as a separate test for TeamCity

#23 skurdiukov closed 8 years ago
0
FilesIncludedIntoProject wrong file path in output

#22 sm-g closed 8 years ago
4
'Warning level 0 is lower than required' false error

#21 sm-g closed 8 years ago
4
Add artifacts to releases

#20 AlenPelin closed 7 years ago
4
Readme file updated

#19 asizikov closed 8 years ago
0
Check, that all references from the packages folder exists in packages.config file

#18 imanushin closed 8 years ago
1
Support parallel projects check

#17 imanushin closed 8 years ago
3
remove success status

#16 imanushin closed 8 years ago
2
Exclude TeamCity success status

#15 imanushin opened 8 years ago
2
Add assembly exception for ReferenceNuGetPackagesOnly

#14 JakeGinnivan closed 9 years ago
0
FilesIncludedIntoProject rule should not be case-sensitive

#13 Litee closed 9 years ago
0
Support custom rules located in another folder

#12 Litee opened 9 years ago
0
Any demand for checking VS solution version?

#11 Litee opened 9 years ago
0
Check that assembly and root namespace have same name

#10 Litee closed 9 years ago
0
Check that all references to binaries in NuGet package have record in packages.config file

#9 Litee closed 9 years ago
0
Add MSBuild integration support

#8 Litee closed 8 years ago
2
Check for missing build configurations

#7 Litee opened 9 years ago
0
Check for unapproved build configurations

#6 Litee opened 9 years ago
0
Forbid pre-release versions for specific packages

#5 Litee closed 9 years ago
0
Provide NuGet commands in log for upgrading to the lowest version

#4 Litee opened 9 years ago
0
Support build configurations as exception

#3 Litee opened 9 years ago
0
File path is required in the list of "lost" files

#2 Litee closed 9 years ago
0
File names encoding is not respected

#1 Litee closed 9 years ago
0