将 IL 代码编译为本机代码时不存在 PDB 文件。

你好,小黄同学 2016-04-26 09:35:15
vs2015, debug下运行没有问题,release就出现 “将 IL 代码编译为本机代码时不存在 PDB 文件。” 而且只是在输出中显示,并没有报错, 导致注册的后台任务没有运行效果,
...全文
1533 1 打赏 收藏 转发到动态 举报
写回复
用AI写文章
1 条回复
切换为时间正序
请发表友善的回复…
发表回复
  • 打赏
  • 举报
回复
Red-Gate Reflector 7.6.0.233 VS Pro Edition Pre-cracked by HF-Death / InFiNiTy-Team Debug any .NET assembly in Visual Studio : Enable debugging for 3rd party assemblies Quickly select assemblies to debug within Visual Studio. .NET Reflector generates PDB files for decompiled assemblies, so you can debug them as easily as your own code. Debug decompiled assemblies using the Visual Studio debugger Now you can step through debugging of any decompiled assemblies as if they were your own. Set breakpoints, watch variables, set next statements, modify variable values, or use any of your other regular debugging techniques. Decompile and explore assemblies on the fly: Dynamic decompilation With Reflector VSPro, assemblies decompile seamlessly in Visual Studio. So source code is always available for your libraries, and you can go straight to the definition of any code, either from the context menu, or by hitting F12 Browse decompiled assemblies .NET Reflector VSPro adds the Reflector Object Browser into Visual Studio. Use the simple tree view to navigate through all types and members, and click to see the decompiled code. A 2-Minute Demo of .NET Reflector VSPro Debug any .NET assembly in Visual Studio: Enable debugging for 3rd party assemblies Quickly select assemblies to debug within Visual Studio. .NET Reflector generates PDB files for decompiled assemblies, so you can debug them as easily as your own code. Select assemblies to decompile and debugSelect assemblies to debug The PDB files are saved for future use, so you only need to enable debugging onc for each assembly. Debug decompiled assemblies using the Visual Studio debugger Now you can step through debugging of any decompiled assemblies as if they were your own. Set breakpoints, watch variables, set next statements, modify variable values, or use any of your other regular debugging techniques. Debug decompiled assemblies using the Visual Studio debuggerDebug decompiled assemblies using the Visual Studio debugger Decompile and explore assemblies on the fly: Dynamic decompilation With Reflector VSPro, assemblies decompile seamlessly in Visual Studio. So source code is always available for your libraries, and you can go straight to the definition of any code, either from the context menu, or by hitting F12 Decompile any referenced assemblyDecompile any referenced assembly Browse decompiled assemblies .NET Reflector VSPro adds the Reflector Object Browser into Visual Studio. Use the simple tree view to navigate through all types and members, and click to see the decompiled code. Browse decompiled assembliesBrowse decompiled assemblies Back to top The world’s most advanced .NET decompiler: .NET Reflector VS can decompile any .NET assembly to C#, VB.NET or IL. .NET Reflector VS will decompile to high level C# features such as Iterator blocks, Lambda expressions, and LINQ queries. .NET Reflector also supports the C# 4 dynamic type. DotNET Reflector 7.5 Changes: * Many string changes to make things easier to understand * Assorted design changes to dialogs and screens * Improvements to the installation experience of the package * Improved the speed of type by type decompilation * Improved handling of the case where the add-in is superseded by the package (we remove the old menu items) * Error reporting experience is more fine-tuned. Users have options to be notified of work-arounds and fixes * Hide menu items such as “enable debugging”, instead of just disabling them * Make “enable debugging” work on all items of the tree, rather than just the top level assembly item * "Go to decompiled definition" more commonly enabled. * Setting a break point causes the necessary PDB file to be automatically generated * Decompiled code can now be stepped-into like any other code * Attempting to step into inaccessible code triggers instructions on how to debug it correctly * Multiple PDBs can now be generated in parallel o PDB generation can currently take a little time, especially if you’re generating several or the assemblies are particularly large * The trial dialog screen has been updated to be more informative and clear * Re-introduced “Go to Decompiled Definition” right-click menu item * Improved support for ‘Go to Definition’(F12) in code without source * A number of simple usability enhancements * A number of licensing and installation bug fixes * Added support for ‘Go to Definition’(F12) in code without source * Improved path to decompiled code * Improved path to pdb generation for code you want to debug * Completed move to a VS Package * Started transition from a VS Add-in to a VS Package * Added support for VS11 * Turned on SmartAssembly feature usage reporting on by default for all EA builds * Added loaded project references to the Reflector Object Browser (ROB) * Double click on any type in the ‘ROB’ to decompile in a new VS editor pane * Added a Reflector ‘Go to Definition’ context menu item to navigate through code without source * Added a new ‘Reflector Object Browser’(ROB) into Visual Studio (will eventually offer decompilation by type inside VS) * Changed the way Reflector shows the version number to display the correct build number * Bug fixes: o “Open in Reflector” context menu not working. o XAML Source Code is wrong delimited. o Missing end tag in XAML Translation. o Code generation for different versions of the same assembly o ‘Flatten Namespaces’ dialog o Various decompilation and assembly-loading problems have been fixed – drop us a note if you’d like to know more. DotNET Reflector 7.6.0.233 VS Pro Edition Cracked HF-Death / InFiNiTy-Team

7,655

社区成员

发帖
与我相关
我的任务
社区描述
Windows Phone是微软发布的一款手机操作系统,它将微软旗下的Xbox LIVE游戏、Zune音乐与独特的视频体验整合至手机中。
社区管理员
  • Windows客户端开发社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧