Parsing Visual Studio Files with Powershell
Most companies have some pretty complicated legacy code bases with a multitude of applications and shared libraries. It can be quite difficult to see how the solutions and projects fit together. With the push towards devops and microservices it’s nice if we can carry some of the legacy applications along too. I’ve found PowerShell a useful way to try to reason about a code base...
In the first instance, a simple command gets you started...
With a list of solutions we can now select one to view the projects using some regex hackery...
Now we want to see what the project file is referencing. This is where it gets interesting, because invariably legacy projects have dlls checked into source control. As a result the projects will be referencing a hard coded location on disk, rather than Nuget...
This time round we are parsing the XML directly and returning a custom PowerShell object which includes the data we need. In the results below, we can see some references to a _dependency folder, presumably these are checked into source control. We can also see the packages folder referenced as well as a single blank Path – this is a .NET framework library:
This final script is useful to see which solutions have a particular project referenced.
The write-host commands are useful if the code base is quite large, because the search will take a long time and its good to see whats being processed.
There is a complete script on github with the code above wrapped in functions. Happy searching :)
In the first instance, a simple command gets you started...
With a list of solutions we can now select one to view the projects using some regex hackery...
Now we want to see what the project file is referencing. This is where it gets interesting, because invariably legacy projects have dlls checked into source control. As a result the projects will be referencing a hard coded location on disk, rather than Nuget...
This time round we are parsing the XML directly and returning a custom PowerShell object which includes the data we need. In the results below, we can see some references to a _dependency folder, presumably these are checked into source control. We can also see the packages folder referenced as well as a single blank Path – this is a .NET framework library:
This final script is useful to see which solutions have a particular project referenced.
The write-host commands are useful if the code base is quite large, because the search will take a long time and its good to see whats being processed.
There is a complete script on github with the code above wrapped in functions. Happy searching :)
