Devart LINQ Insight 3.7.16
Devart LINQ Insight 3.7.16
Execute LINQ Queries at Design-Time and Profile ORM Data Access with LINQ Insight! LINQ Insight is a Visual Studio add-in that provides a complete set of tools that make LINQ/ORM development faster and easier, and helps you to produce more efficient data access code. It allows executing LINQ queries at design-time directly from Visual Studio without starting a debug session, allowing you to test queries instantly after you write them. LINQ Insight also provides a powerful ORM profiler tool for profiling the data access layer of your projects and tracking all the ORM calls and database queries from the ORM.
LINQ Insight allows you to test LINQ queries at design-time. Unlike different LINQ debug visualizers, LINQ Insight does not require you to start debugging and step to the LINQ query execution for viewing returned data and generated SQL.
Benefits
Test your LINQ queries instantly after you write them
Estimate the query complexity analyzing the generated SQL
Check if the query returns correct data
LINQ Insight offers you LINQ Profiler - a powerful tool that allows you to profile your projects and track all the ORM calls and database queries from the ORM. It enables you to see the performance of the data access code and easily determine performance bottlenecks.
Benefits
Get insight into all the interaction with ORM and database
Measure performance of your data access code and analyze it easily
Supported LINQ Providers
LINQ to Entities (Entity Framework)
LINQ to NHibernate
LINQ to SQL
LinqConnect
LINQ to XML
LINQ to Objects
RavenDB
Debug LINQ with LINQ Insight - Execute Queries at Design-time!
LINQ Insight allows you to execute your queries at design-time. That means, you don't need to start debugging your application and navigate to the query to test it, just write your queries and execute them right from your code, then view SQL and data without leaving Visual Studio!
LINQ Insight supports both usual LINQ queries and queries through extension methods. It also supports anonymous queries, for example, with immediate ToList calls.
LINQ Insight is fully integrated into Visual Studio - you don't need to run external applications and enter your queries to them. It detects the connection string and the context used automatically.
With LINQ Insight there is no more need in tedious debugging to check LINQ queries.
Data
With LINQ Insight you can preview data, returned for LINQ queries. The returned data is displayed in a grid, where you can sort and group, and filter this data. LINQ Insight even allows you to edit data for LINQ to SQL, LINQ to Entities, and LinqConnect.
SQL
For LINQ to SQL, LINQ to Entities, LINQ to NHibernate, and LinqConnect, LINQ Insight displays the SQL generated for the query. You can also see the parameter values used if the SQL uses parameters.
Parameters
With LINQ Insight you don't need to replace variables in the query code with constants. LINQ Insight detects these variables and their types, and replaces them with parameters. You will be asked to enter values for them when you execute this query first time.
Connection String
In most cases LINQ Insight detects the connection string used by a query automatically, however you can always specify it manually in a convenient editor.
Grouping Data
To group the data by any column, drag the column header you want the data to be grouped by to the Group By Box panel.
Filtering Data
You can easily filter data by entering the filter string to the Filter box on the LINQ Interactive window toolbar. LINQ Interactive window will display only rows containing the entered string and highlight the occurrences of the string.
Viewing Related Data
LINQ Insight also offers you a convenient way to browse the related objects. You may either click the drop-down arrow in the cell with this property, to view its contents in a new grid without hiding the original data, or click the underlined object (or collection) property in the grid, and the grid will be filled with the contents of this property.
Editing Data
LINQ Insight allows you to edit data, returned by LINQ to SQL, LINQ to Entities, and LinqConnect queries. All the data updating operations are performed through the ORM. You can edit several objects and then apply changes or discard them.
True ORM Profiler
Applications, using ORMs to access data usually don't interact with database directly. Instead they interact with ORM run-time - query entities via LINQ, work with them, and then post modified entities via SaveChanges (or SubmitChanges). ORM runtime, in its turn, interacts with the database - opens connections, queries and updates data via SQL, etc.
Most profilers show just the interaction with the database - SQL statements execution, database connecting, etc. LINQ Insight offers true ORM profiler - it allows you to really profile the interaction between applications and ORM! With our LINQ Profiler tool you can see how much time LINQ statement or SubmitChanges call takes to execute as a whole even if it generated multiple SQL statements. You profile exactly the code you write and study the real performance of your LINQ code.
Moreover, there is no need to modify your project at all! Just open the LINQ Profiler window and click the Start profiler session button on its toolbar. Then run your project and get real-time data on ORM events in the LINQ Profiler window.
Multiple ORMs Supported
LINQ Insight supports the following ORMs:
Entity Framework
NHibernate
LinqConnect
LINQ to SQL
Profile ORM Calls
With our LINQ Profiler tool you can see the details of such ORM calls as context creating and destroying, LINQ queries, SaveChanges calls.
See Related Data Access Events
LINQ Profiler enables you to see which data access events are caused by any specific ORM call. This allows you, for example, to easily find LINQ data access antipatterns that generate a large number of SQL commands for a single query.
Data Access Events View
Study the generated SQL command performance, transactions, connection opening and closing with the Data Access Events view, similar to other ORM profilers. You can easily navigate between a data access event on this view and the corresponding ORM call on the ORM Events view.
Queries View with Summarized Information
Queries view allows you to easily find the situations when a query is used too often and it may be better to cache its results than to use it each time. It allows you to group the executed LINQ queries by query text, calling thread, or the context used and see the total number of queries in each group and total time these queries took to execute.
Object Tree
ORM calls can be easily filtered by the calling process or context with the Object Tree window. Just select the corresponding context or process node.
Call Tree
Call Tree window is a powerful tool for filtering the profiler information by the calling method. It displays the tree, created by merging all call stacks of ORM calls.
3.7.16 16-Mar-20
The bug with using namespaces for the collections being created when running LINQ to Objects queries is fixed
The bug with using namespaces for the collections being created when running LINQ to Objects queries is fixed
Only for V.I.P
Warning! You are not allowed to view this text.