SourceBrowser alternatives and similar packages
Based on the "Documentation" category.
Alternatively, view SourceBrowser alternatives based on common mentions on social networks and blogs.
5.2 6.8 SourceBrowser VS F# FormattingF# tools for generating documentation (Markdown processor and F# code formatter)
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of SourceBrowser or a related project?
Create and host your own static HTML website to browse your C#/VB/MSBuild/TypeScript source code. Note that it does require an ASP.NET Core website for hosting (symbol index is kept server-side), so without ASP.NET Core the search function doesn't work.
Of course Source Browser allows you to browse its own source code: http://sourcebrowser.azurewebsites.net
Now also available on NuGet: https://www.nuget.org/packages/SourceBrowser
Instructions to Build (requires Visual Studio 2019):
- git clone https://github.com/KirillOsenkov/SourceBrowser
- cd SourceBrowser
Instructions to generate and run a test website
In Visual Studio 2019:
- Open SourceBrowser.sln.
- Set HtmlGenerator project as startup and hit F5 - it is preconfigured to generate a website for TestCode\TestSolution.sln.
- Pass a path to an .sln file or a .csproj file (or multiple paths separated by spaces) to create an index for them
- Pass /out: to HtmlGenerator.exe to configure where to generate the website to. This path will be used in step 6 as your "physicalPath".
- Pass /in: to pass a file with a list of full paths to projects and solutions to include in the index
- Pass /root: if you want to preserve relative .sln folders rather than merging all solutions. This folder must contain all specified .sln or .csproj paths.
- Set SourceIndexServer project as startup and run/debug the website.
Note: Visual Studio 2019 is required to build Source Browser.
At indexing time, C# and VB source code is analyzed using Roslyn and a lot of static hyperlinked HTML files are generated into the output directory. There is no database. The website is mostly static HTML where all the links, source code coloring etc. are precalculated at indexing time. All the hyperlinks are hardwired to be simple links bypassing the server.
The only component that runs on the webserver is a service that given a search query does the lookup and returns a list of matching types and members, which are hyperlinks into the static HTML. The webservice keeps a list of all declared types and members in memory, this list is also precalculated at indexing time. All services, such as Find All References, Project Explorer, etc. are all pre-rendered.
The generator is not incremental. You have to generate into an empty folder from scratch every time, and then replace the currently deployed folder with the new contents atomically (using e.g. Azure Deployments, robocopy /MIR to inetpub\wwwroot, etc). For smaller projects, deploying to Azure using Dropbox or Git would work just fine.
Limitations and known issues
- Indexing more than one project with the same assembly name is currently unsupported. Only the first project wins. This is due to a fundamental design decision to only reference an assembly by short name. Customizers should add a means to filter "victim" projects out in their forks to pick the best single project for inclusion in the index.
- The generated website can only be hosted in the root of the domain. Making it run from a subdirectory is non-trivial and unlikely to be supported.
- Solution Explorer - contents of projects merged into single tree on the left
- coloring for C#, VB, MSBuild, XAML and TypeScript
- Go To Definition (click on a reference)
- Find All Reference (click on a definition)
- Project Explorer - in any document click on the Project link at the bottom
- Namespace explorer - for a project view all types and members nested in namespace hierarchy
- Document Outline - for a document click on the button in top right to display types and members in the current file
- http://<URL>/i.txt for the entire solution and /AssemblyName/i.txt (for an assembly) displays source code stats, lines of code, etc
- http://<URL>/#EmptyArrayAllocation finds all allocations of empty arrays (this feature is one-off and hardcoded and not extensible)
- Clicking on the partial keyword will display a list of all files where this type is declared
- MSBuild files (.csproj etc) have hyperlinks
- TypeScript files (*.ts) are indexed if they're part of a C# project. Work underway to allow an arbitrary array of TypeScript files.
- Search for GUIDs in C#/VB string literals is supported
Project status and contributions
This is a reference implementation that showcases the concepts and Roslyn usage. It comes with no guarantees, use at your own risk. We will consider accepting high-quality pull requests that add non-trivial value, however we have no plans to do significant work on the application in its current form. Any significant rearchitecture, adding large features, big refactorings won't be accepted because of resource constraints. Feel free to use it to generate websites for your own code, integrate in your CI servers etc. Feel free to do whatever you want in your own forks. Bug reports are gratefully accepted.
For any questions, feel free to reach out to @KirillOsenkov on Twitter. Thanks to @v2_matveev for contributing TypeScript support! Thanks to numerous other contributors for various fixes and contributions!