SequenceViz : This add-in draws sequence diagrams.ĪutoDiagrammer : This add-in draws class diagrams. DownloadĪssemblyListEx:Register a file type association for predefined lists of assemblies to load into Reflector. RuleSetEditor: Editor for Windows Workflow Foundation rules. DownloadĭependencyStructureMatrix : Allows you to create and browser dependency structure matrices.ĬodeSearch: This add-in allows searching for strings and regular expressions in disassembled code. ![]() Please read the install instructions here.īizTalkDisassembler: Allows you to list all BizTalk artifacts contained in an assembly and extract them. Graph: This add-in draws assembly dependency graphs and IL graphs. NET assemblies stored in SQL Server 2005 databases.įileGenerator : This add-in can be used to dump the disassembler output to files for any Reflector supported language.ĭeblector : This add-in allows to debug processes from within Reflector.ĭoubler : A code generator for unit tests, stubs and wrappers. SQL2005Browser : This add-in allows to browse. DownloadĬomLoader: Lists COM components for browsing and converts them into managed interop assemblies. SilverlightBrowser: Loads and shows the files associated with a Silverlight website. Reflexil : Allows to manipulate the IL of a loaded assembly, or inject VB.net/C# code, then write the changes to disk.īamlViewer: Load BAML resources (WPF) and render in XAML format. ![]() DownloadįileDisassembler : This add-in can be used to dump the disassembler output to files for any Reflector supported language. SilverlightLoader: Allows browsing the structure of a website and loading Silverlight assemblies. Snippy: Snippy is a light weight snippet compiler integrated into. Pex: Use the Pex Wizard directly from Reflector (requires. Downloadĭiff : This add-in shows differences between two versions of the same assembly. Review: Allows editing and managing annotations during code reviews. NET Reflector Desktop - a standalone application to explore and navigate decompiled code NET Reflector Standard - Basic decompilation NET Reflector is available in 2 editions: NET Reflector to look into the black box of missing or undocumented source code and start coding with confidence. This gets even worse with a legacy code base. Documentation is often missing or incomplete, and debugging has to stop where your own code stops. But the problem with using code you didn't write is that you're dependent on the documentation, and it's hard to debug. Development is increasingly dependent on third-party technologies – using available frameworks and libraries is a great way to get stuff done fast without re-inventing the wheel. NET Reflector saves time and simplifies development by letting you see and debug into the source of all the. NET Reflector you can look inside their assemblies and see how they work and which APIs you can call. ![]() SharePoint and other third-party platforms - Like many third-party platforms, SharePoint APIs and libraries aren't always well-documented.NET Reflector to understand how the code runs and avoid bugs. Understand how applications work - Inherited applications with little or no documentation or comments are hard to develop.Debugging your application - Follow bugs through your application to see where your problems lie – whether it's in your own code, third-party libraries, or components used by your application.NET code, even if you don't have the source NET Reflector you can decompile, understand, and fix any. VSPro edition includes the standalone application, and the Reflector Object Browser in Visual Studio, to navigate decompiled code. Step into decompiled code (F11), run it with the Visual Studio debugger and Go To Definition (F12) for any code. NET languages and frameworks are implemented, and learn how to use them.NET Reflector VSPro provides the following functionality: Dynamic decompilation inside Visual Studio, set breakpoints in code (F9), even if you don’t have the source. Find unexposed and undocumented functionality and get more out of the APIs and technologies you’re using. Replace poor or missing documentation by seeing how the code works in context. Track down the exact location of bugs in your own code or third-party libraries and find dependencies, diff assemblies, and understand how code works. See how data flows through a library or component, and watch locals change as you debug. You can see third-party code in Visual Studio, and debug into it just like your own. Follow bugs through your own code, third-party components, and any compiled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |