Category: PackageAnalyzer
-
NetPackageAnalyzer and ContosoUniversity
I have analyzed https://github.com/jbogard/ContosoUniversityDotNetCore-Pages with https://nuget.org/packages/netpackageanalyzerconsole . If you open the solution,even if it is a single project,it is well organized,even if not maintained anymore ( no commits this year) Number projects : 2 (tests : 1,no tests : 1 ) Number packages : 304 (Outdated: 25,Deprecated: 1,Major version differs 9 ) Total Commits: 83…
-
NetPackageAnalyzer and Clean-Architecture-Manga
I have analyzed https://github.com/ivanpaulovich/clean-architecture-manga with https://nuget.org/packages/netpackageanalyzerconsole . It seems to be one simplistic,but better than a monolith Number projects : 9 (tests : 4,no tests : 5 ) Number packages : 213 (Outdated: 26,Deprecated: 4,Major version differs 29 ) Total Commits: 103 ( last commit : 2023) 5 Projects 103 commits Generated by https://www.nuget.org/packages/NetPackageAnalyzerConsole
-
NetPackageAnalyzer and Fitnet
I have analyzed https://github.com/evolutionary-architecture/evolutionary-architecture-by-example with https://nuget.org/packages/netpackageanalyzerconsole . It seems one of the good projects to be analyzed from an architecture summary. It shows how the architecture evolved from a monolith to microservcices. Chapter 1 summary Number projects : 4 (tests : 3,no tests : 1 ) Number packages : 175 (Outdated: 20,Deprecated: 0,Major version differs…
-
NetPackageAnalyzer and dotnet-starter-kit
I have analyzed https://github.com/fullstackhero/dotnet-starter-kit with https://nuget.org/packages/netpackageanalyzerconsole . It seems to be simplitic,even if it has the migrations for different database ( I do not have had this case ) Number projects : 11 (tests : 1,no tests : 10 ) Number packages : 346 (Outdated: 64,Deprecated: 5,Major version differs 5 ) Total Commits: 644 (…
-
NetPackageAnalyzer and eshop
I have analyzed https://github.com/dotnet/eShop with https://nuget.org/packages/netpackageanalyzerconsole . It seems one of the good projects to be analyzed from an architecture summary Number projects : 25 (tests : 5,no tests : 20 ) Number packages : 409 (Outdated: 24,Deprecated: 0,Major version differs 28 ) Total Commits: 193 ( last commit : this year,2024) 20 Projects 193…
-
NetPackageAnalyzer–part 6–Commits
Commit data for all time for the solution You can see the commits for all time for the solution. Commit data history for each project / folder You can see the commits for all time for the solution. And for each year since the beginning of the solution,you can see the commits. Commit data for…
-
NetPackageAnalyzer–part 5- packages
List of packages For the solution it generates list of packages from each project and also shows when are differences between the major versions of the packages. Example docFx For the solution docFx it generates the following: Number of packages : 154 Packages with more than 1 version: 30 ( 19 % from total packages)…
-
NetPackageAnalyzer–part 4–projects analysis
Projects data Graph for relations between projects in a solution For the solution it generates the project relations as in a mermaid graph. Examples For example,for the solution PackageAnalyzer it generates the following graph: For the project docFX it generates the following graph: Building blocks for the solution Also it generates the building blocks for…
-
NetPackageAnalyzer–part 3–installation
Install as local tool Go to where your sln is and enter this: dotnet new tool-manifest dotnet tool update netpackageanalyzerconsole Then you can run dotnet PackageAnalyzer generateFiles and see results at Analysis folder as a Docusaurus site . Just run npm i npm run start to see what is generated ( see https://ignatandrei.github.io/PackageAnalyzer/docs/category/solutions )
-
NetPackageAnalyzer–part 2- technical details
How it is made The project is made using the following technologies: – .NET Core local tool for the analysis – Docusaurus for the static site How the analysis of the solution is made Gathering data For getting the packages,it runs the following: Build the solution with dotnet build List packages from the solution with…