Although Visual Studio was born as a native C++ application, with each release more and more of its code became managed (.NET). The first scenario is to decompile Visual Studio assemblies. NET Framework and you can even debug its assemblies, but it hasn't done the same with Visual Studio assemblies. Microsoft has released the source code of the. I mean: you may have the source code of a Visual Studio assembly with some complex logic, and it is difficult to guess which branches are actually executed for certain cases. To guess which code path inside a method is actually used at run-time.To understand how Visual Studio does some kind of things, because you need to do the same or similar ones in your own extension. In this guest post I will explain why.ĭeveloping a somewhat complex Visual Studio extension, there are two scenarios where you may desire to have the Visual Studio source code and even to debug its assemblies: NET Reflector to understand the internals of Visual Studio assemblies since many years ago, and I consider it an invaluable tool for developers of Visual Studio extensions (add-ins, packages, etc.). NET Reflector to understand and debug Visual Studio assembliesĪs a developer of Visual Studio add-ins, I have been using. We liked it, and asked him to tell us a bit more… Using. NET Reflector to understand and debug Visual Studio assembliesīy Roger Hart and Carlos Quintero, October 30th, 2012Ĭarlos Quintero (MVP, and developer of MZ-Tools) recently wrote a blog post on debugging into Visual Studio's assemblies. NET Reflector To Understand And Debug Visual Studio Assemblies Skip to content
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |