Net reflector для windows

Made In Tula
[SoftoRooMTeaM]

Группа: Администраторы
Сообщений: 23.250
Регистрация: 22.02.2004
Пользователь №: 7

Респектов: 5232

описание (ru) .NET Reflector утилита для Microsoft .NET, комбинирующая браузер классов, статический анализатор и декомпилятор
NET
Программа NET Reflector может использоваться для навигации, поиска и анализа содержимого .NET-компонентов, а также сборок и переводить двоичные данные в форму, пригодную для чтения человеком. Reflector позволяет производить декомпиляцию .NET-сборок на языки C#, Visual Basic .NET и MSIL. Reflector также включает дерево вызовов (англ. Call Tree), которое может использоваться для навигации вглубь IL-методов с целью определения, какие методы они вызывают. Программа отображает метаданные, ресурсы и XML-документацию. .NET Reflector может быть использован .NET-разработчиками для понимания внутренней работы библиотек кода, для наглядного отображения различий между двумя версиями сборки, и того, как различные части .NET-приложения взаимодействуют друг с другом.

.NETReflector может использоваться для нахождения мест, имеющих проблемы с производительностью и поиска багов. Он также может быть использован для поиска зависимостей сборки. Программа может быть использована для эффективной конвертации кода между C# и VB.NET.

description (en) .NET Reflector is a class browser, decompiler and static analyzer for software created with .NET Framework, originally written by Lutz Roeder. MSDN Magazine named it as one of the Ten Must-Have utilities for developers, and Scott Hanselman listed it as part of his «Big Ten Life and Work-Changing Utilities».
.NET Reflector was the first CLI assembly browser. It can be used to inspect, navigate, search, analyze, and browse the contents of a CLI component such as an assembly and translates the binary information to a human-readable form. By default Reflector allows decompilation of CLI assemblies into C#, Visual Basic .NET, C++/CLI and Common Intermediate Language and F# (alpha version). Reflector also includes a «Call Tree» that can be used to drill down into intermediate language methods to see what other methods they call. It will show the metadata, resources and XML documentation. .NET Reflector can be used by .NET developers to understand the inner workings of code libraries, to show the differences between two versions of the same assembly, and how the various parts of a CLI application interact with each other. There are a large number of add-ins for Reflector.

.NET Reflector keygen can be used to track down performance problems and bugs, browse classes, and maintain or help become familiar with code bases. It can also be used to find assembly dependencies, and even windows DLL dependencies, by using the Analyzer option. There is a call tree and inheritance-browser. It will pick up the same documentation or comments that are stored in xml files alongside their associated assemblies that are used to drive IntelliSense inside Visual Studio. It is even possible to cross-navigate related documentation (xmldoc), searching for specific types, members and references. It can be used to effectively convert source code between C# and Visual Basic.

Find and fix bugs fast

Decompile, understand, and fix any .NET code, even if you don’t have the source

Introduction to .NET Reflector

Look inside any .NET code

Debug your application

Follow bugs through your application to see where the problem is – your own code, third-party libraries, or components used by your application.

Understand how applications work

Inherited an application with no documentation and no comments? Use .NET Reflector to understand how the code runs and avoid bugs.

Look inside APIs, SharePoint, and other third-party platforms

Third-party platforms aren’t always well-documented. Use .NET Reflector to look inside their assemblies, and see how they work and which APIs you can call.

Try it now, choose your version later.

Standard

A standalone application to explore and navigate decompiled code

Perpetual license without support and upgrades

VSPro

Debug 3rd party code

Dynamic decompilation inside Visual Studio

Includes the standalone application, and the Reflector Object Browser

Perpetual license without support and upgrades

Standard

A standalone application to explore and navigate decompiled code

Perpetual license without support and upgrades

VSPro

Debug 3rd party code

Dynamic decompilation inside Visual Studio

Includes the standalone application, and the Reflector Object Browser

Perpetual license without support and upgrades

Standard

A standalone application to explore and navigate decompiled code

Perpetual license without support and upgrades

VSPro

Debug 3rd party code

Dynamic decompilation inside Visual Studio

Includes the standalone application, and the Reflector Object Browser

Perpetual license without support and upgrades

For 20 or more users,
contact us for a personalized quote.

.NET Reflector features

Standard edition features

Decompilation

Decompile, browse, and analyze any .NET assembly to C#, VB.NET, or IL.

Desktop application

Use the standalone application to explore and navigate decompiled code.

Search filtering

Get results as you type and find what you’re looking for easily.

Debug and decompile inside Visual Studio (VSPro edition)

Use the Visual Studio debugger

Use your regular debugging techniques on any decompiled assemblies as if they were your own, using the Visual Studio debugger.

Debug third-party assemblies

Generate .pdb files for decompiled assemblies and save them so you only need to enable debugging once for each assembly.

Dynamic decompilation

Assemblies decompile seamlessly in Visual Studio so source code is always available for your libraries.

Use VS shortcuts

Use F12 to “Go To Definition”, F9 to “Set Breakpoints”, and F11 to “Step Into” any decompiled code.

C#7 decompilation

.NET Reflector supports C#7, .NET 4.7.2, and .NET Core and Standard.

Browse assemblies

.NET Reflector VSPro adds the Reflector Object Browser into Visual Studio. Use the tree view to navigate through code.

What our customers are saying

The ability to step into third–party code, including Microsoft SharePoint Server assemblies, opens up new possibilities and lets you understand what Microsoft’s APIs are doing.

You can step right into their code and see what is happening, all from Visual Studio. This knowledge lets you build better applications and provides insight into undocumented APIs.”

3 ways .NET Reflector will make your life easier

Follow data

See how data flows through a library or component, and watch locals change as you debug.

Find bugs

Track down the exact location of bugs in your own code or third-party libraries.

Get insight

Find dependencies, diff assemblies, and understand how code works.

Debug third-party code fast

Using third-party technologies is a great way to get stuff done fast without re-inventing the wheel. But it’s hard to debug libraries, components, and frameworks you didn’t write.

.NET Reflector saves time and simplifies development by letting you see and debug into the source of all the .NET code you work with.

Follow bugs through your own code, third-party components, and any compiled .NET code you work with. You can see third-party code in Visual Studio, and debug into it just like your own.

See how people are using .NET Reflector to debug third-party code

Better docs

Replace poor or missing documentation by seeing how the code works in context.

Discover methods

Find unexposed and undocumented functionality and get more out of the APIs and technologies you’re using.

Learn tech

Drill into how .NET languages and frameworks are implemented, and learn how to use them.

Work easily with any code

Languages and libraries aren’t always well-documented. Legacy code isn’t always well-commented. Understand how APIs, components, frameworks, and all the critical code you use really works by decompiling and seeing inside.

Having the source code available means you’re no longer blocked by poor or missing documentation. You can see how code runs, avoid bugs, and develop easily with third-party technologies.

See how developers are solving their problems with .NET Reflector

Look inside

Create better controls, WebParts, and features by seeing how they work, and how the code runs.

Fix bugs

Track down the source of errors in your own code or the SharePoint libraries.

Get insight

Find out what methods to call and how they work, without relying on documentation.

Simplify SharePoint development

SharePoint APIs and libraries aren’t always well-documented, or exposed in the way you need. But that doesn’t have to be a problem.

With .NET Reflector you can look inside the SharePoint assemblies and understand exactly how they work.

How developers are solving their problems with .NET Reflector

.NET Reflector add-ins

NET Reflector has a comprehensive add-in model, with an API that lets you extend the tool to suit your exact needs.

The API also lets other tools take advantage of .NET Reflector’s unparalleled decompilation and disassembly abilities to complement their own functionality. The best thing is, building your own add-in is painless.

Below are some great add-ins and tools which we recommend you try out, and there are more you can download.

We’ve done our best to find some of the best add-ins around, but you can still recommend other add-ins which you think we should feature. Or better still, why not write your own?

We have links to some great tutorials to get you started

Our favorite add-ins

SmokeTest

SmokeTest lets you invoke any member of a class interactively. An indispensable tool for anyone involved in developing, testing, and managing Windows .NET projects.

Reflexil

Created by Sebastien Lebreton

Reflexil is an advanced assembly editor, able to manipulate IL code and save the modified assemblies to disk. Reflexil also supports ‘on the fly’ C# and VB.NET code injection.

Snippy

Snippy is a lightweight snippet compiler originally created by Jon Skeet for his book C# in Depth: What you need to master C# 2 and 3, and later turned it into a Reflector add-in by Jason Haley.

Further information and support

Discounts apply for multi-user purchases

If you’d like any help, or have any questions about our tools and purchasing options, please get in touch.

Get started with .NET Reflector

Download a 14-day trial of the world’s most downloaded .NET developer tool.

Save with our .NET Developer Bundle

Get all our essential .NET developer tools at a 35% discount with the .NET Developer Bundle.

Get the latest news and training with the monthly Redgate Update Sign up

.NET Reflector 10.3.1

утилит для NET Framework browser, decompiler, analyzer

PRYANIK, 6.11.2018 — 7:20

описание (ru) .NET Reflector утилита для Microsoft .NET, комбинирующая браузер классов, статический анализатор и декомпилятор
NET
Программа NET Reflector может использоваться для навигации, поиска и анализа содержимого .NET-компонентов, а также сборок и переводить двоичные данные в форму, пригодную для чтения человеком. Reflector позволяет производить декомпиляцию .NET-сборок на языки C#, Visual Basic .NET и MSIL. Reflector также включает дерево вызовов (англ. Call Tree), которое может использоваться для навигации вглубь IL-методов с целью определения, какие методы они вызывают. Программа отображает метаданные, ресурсы и XML-документацию. .NET Reflector может быть использован .NET-разработчиками для понимания внутренней работы библиотек кода, для наглядного отображения различий между двумя версиями сборки, и того, как различные части .NET-приложения взаимодействуют друг с другом.

.NETReflector может использоваться для нахождения мест, имеющих проблемы с производительностью и поиска багов. Он также может быть использован для поиска зависимостей сборки. Программа может быть использована для эффективной конвертации кода между C# и VB.NET.

description (en) .NET Reflector is a class browser, decompiler and static analyzer for software created with .NET Framework, originally written by Lutz Roeder. MSDN Magazine named it as one of the Ten Must-Have utilities for developers, and Scott Hanselman listed it as part of his «Big Ten Life and Work-Changing Utilities».
.NET Reflector was the first CLI assembly browser. It can be used to inspect, navigate, search, analyze, and browse the contents of a CLI component such as an assembly and translates the binary information to a human-readable form. By default Reflector allows decompilation of CLI assemblies into C#, Visual Basic .NET, C++/CLI and Common Intermediate Language and F# (alpha version). Reflector also includes a «Call Tree» that can be used to drill down into intermediate language methods to see what other methods they call. It will show the metadata, resources and XML documentation. .NET Reflector can be used by .NET developers to understand the inner workings of code libraries, to show the differences between two versions of the same assembly, and how the various parts of a CLI application interact with each other. There are a large number of add-ins for Reflector.

.NET Reflector keygen can be used to track down performance problems and bugs, browse classes, and maintain or help become familiar with code bases. It can also be used to find assembly dependencies, and even windows DLL dependencies, by using the Analyzer option. There is a call tree and inheritance-browser. It will pick up the same documentation or comments that are stored in xml files alongside their associated assemblies that are used to drive IntelliSense inside Visual Studio. It is even possible to cross-navigate related documentation (xmldoc), searching for specific types, members and references. It can be used to effectively convert source code between C# and Visual Basic.

.NET Reflector crack has been designed to host add-ins to extend its functionality, many of which are open source. Some of these add-ins provide other languages that can be disassembled too, such as PowerShell, Delphi and MC++. Others analyze assemblies in different ways, providing quality metrics, sequence diagrams, class diagrams, dependency structure matrices or dependency graphs. It is possible to use add-ins to search text, save disassembled code to disk, export an assembly to XMI/UML, compare different versions, or to search code. Other add-ins allow debugging processes. Some add-ins are designed to facilitate testing by creating stubs and wrappers.

Interface languages: En
OS: Windows 10/8/7 (32bit-64bit)
Homepage: www.red-gate.com
скачать бесплатно / free download .NET Reflector 10.3.1 + crack (license gen)

remon, 29.05.2019 — 19:08

.NET Reflector VSPro v10.1.1419 (Portable+Add-ins)
File Size : 12.85

.NET Reflector is an assembly browser for the Microsoft .NET platform that can be used to explore, analyse, decompile, and debug the contents of any .NET assembly — even if you don’t have the source. .NET Reflector combines class browsing, static analysis and high-level decompilation to help .NET developers understand how a library works or how it interacts with other parts of a .NET application. .NET Reflector will decompile to high level C#, VB, IL and some F# features.

Standalone Windows application
Browse, analyse and decompile any .NET code
Decompile any .NET assembly to C#, VB.net or IL
Tabbed decompilation, search and analyse panes

Visual Studio Integration
Open any assembly in Reflector straight from Visual Studio
Decompile assemblies without source seamlessly from inside Visual Studio
Browse objects using the Reflector Object Browser inside Visual Studio

Debug assemblies without source code
Step-through debugging of any decompiled assembly in Visual Studio
Set breakpoints anywhere in the decompiled code
Watch variables, set next statements, modify variable values, and dynamic expression evaluation.

xmi4dotnet :
Convert your .NET assemblies into XMI for easy import into UML tools like Poseidon for UML. This code has been designed to work with Reflector for .NET 5, and .NET 2.0 assemblies.​

Reflexil.Reflector.AIO
Reflexil is an assembly editor and runs as a plug-in for Red Gate’s Reflector, ILSpy and Telerik’s JustDecompile. Reflexil is using Mono.Cecil, written by Jb Evain and is able to manipulate IL code and save the modified assemblies to disk. Reflexil also supports C#/VB.NET code injection.​

Collapse All Assemblies
There is now a command to Collapse All Assemblies in the File menu. Since we don’t have a root node in the assembly browser (like a solution in Visual Studio has) this doesn’t make sense in a context menu, so it’s in the File menu for now. As Jason Haley put it when he originally wrote the Power Commands add-in: «This exposes the underlying tree view’s CollapseAll method functionality – which means it will collapse all expanded nodes that are currently open.» It’s great for when you have a ton of assemblies and you need to go back to the default state before you expanded them all.

Copy As
When viewing code for a class, type, property or field, you can now use the right-click context menu in the code window to copy all the code to the clipboard in a format of your choice. Note that for a class this will expand all the methods automatically, so in the picture above selecting «Text» will copy the entire ConcurrentBag class to the clipboard.

Hopefully this will fix some of the issues where you need to quickly reproduce the code generated by Reflector, but were having problems with those pesky code hyperlinks. The original copy function is still there if you still want to copy a selection as well, and becomes available when you highlight a section of code.

Import/Export Assembly List
We’re still looking at ways to improve our assembly list management functionality, but for now there’s a way to save your assembly list setup by using the Export Assembly List command, and then load it back using Import. Perhaps you might want to do this as part of backing up your Reflector configuration, or to move between different computers with the same setup. Exporting opens another dialog where you can choose which assemblies from the lists to export, and save this as an XML file for later importing.

It’s not immediately clear that importing won’t make changes to the assemblies which are currently loaded into Reflector, only the assembly lists. So once you’ve imported your assembly lists you will still need to Open Assembly List and select the list you want to load into Reflector.

Open File Location
This opens an explorer window at the location on disk where the assembly can be found. Useful for when you quickly need to get to the DLL or EXE so you can manipulate the file outside of Reflector.

Open With
At several levels in the assembly browser there’s an option to open the selected item with an application of your choice. Separate commands for common applications formed a large proportion of the original Power Commands add-in, so we’ve distilled these into default applications for one larger Open With command.

This means slightly different functionality for different levels in the tree. Notably, code snippets are written to a temporary file (using the Copy As function described earlier, but writing to a file instead of the clipboard) so they can be opened, and resources are extracted before they open normally. Resource tables are opened in Visual Studio as .RESX files so they can be viewed more easily. And assemblies open as expected.

Selecting Choose Application will bring up a dialog where you can add your own applications. Adding an application to the list will save it so that next time you select Choose Application you will be able to select the desired application faster.

Open Zip
Did you know you can drag a .ZIP archive into Reflector and it will decompile the compressed assemblies without you having to extract them yourself? This was originally a Power Command, but while looking for ways to merge the code I discovered native functionality in Reflector for opening Silverlight applications (XAP files) which could be easily extended to handle .ZIP archives as well. You can also select .ZIP archives now from the drop down menu in the Open Assembly dialog, and open them through the menu.

Referenced By
The analyzer now contains the functionality to show which of the assemblies loaded into Reflector depend on the selected assembly or module. This means you can now check dependencies both ways: from the assembly browser for references of the current assembly, and from the analyzer for assemblies referencing the current assembly.

At the moment the analyzer will only show the list of assemblies. But if it’s useful, it might be an exciting possible improvement for the future to attempt to show the code which calls into the current assembly by making the analyzer tree expandable to show the classes and methods which do this! That way you will be able to see not only where your assembly is being used, but also how it is being used by other assemblies.​