Information in this table applies only to web tests that implement the classic approach. For more information, see Object Mapping. However, to make this possible, you need to specify the class name of your inherited control in the corresponding group of the project’s Object Mapping options. Note that TestComplete provides support for the listed controls as well as for their descendants. Refer to the previous section to fix the issue.Below is the full list of the Developer Express controls for which TestComplete provides extended support. This issue may occur if you have not disabled debugging optimization. The cursor is positioned on a code line that does not match the call stack To ignore native images compiled with Ngen.exe, you can use scripts listed in the following table: Refer to the following topic for more information on debugging optimization: JIT Optimization and Debugging. In the previous post, I announced our new AutoSuggest mode for both the DevExpress. As part of our ongoing commitment to engage the DevExpress developer community, we wanted to share our progress and give you the opportunity to test major new functionality before we wrap. JIT optimization may have a side effect that does not allow you to watch local variables. We are about two months away from our next major release (v19.2). Visual Studio may display the following message:Ĭannot obtain value of local or argument as it is not available at this instruction pointer, possibly because it has been optimized away. Troubleshooting I cannot inspect a local variable value Refer to the following topic for more information: Visual Studio debugger documentation. Press F11 to step into DevExpress components source code. Set a breakpoint anywhere in DevExpress code and run your application in the Debug configuration. Now, your environment is ready to debug DevExpress components. Refer to the following Microsoft article for more information: Specify symbol (.pdb) and source files in the Visual Studio debugger Add a source to the DevExpress Component sources. Specify a path with the DevExpress sources in your solution properties: right-click the solution and navigate to Properties | Common Properties | Debug Source Files. Navigate to Debug | Options and uncheck “Enable Just My Code”. When this option is enabled, the installer installs DevExpress components’ source and symbol files, and registers symbol files in Visual Studio for the current user: To install debug symbols, check the Source Code & Symbols option when you install DevExpress Components. NET Components referenced in your applications.įollow the steps below to prepare your environment for debugging DevExpress Components. NET Source Code with PDB SymbolsĭevExpress Universal or DXperience subscription includes debug symbols that allow you to debug DevExpress.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |