Databases
StackOverflow2013
Postsdbo
POHow to solve code analysis warning CA1506 : "Avoid excessive class coupling"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to solve code analysis warning CA1506 : "Avoid excessive class coupling"
    primarykey
    data
    text
    <p>I am facing CA1506 code analysis warning for following code</p> <pre><code>private void ShowProductStatistics(object obj) { this.currentProduct = obj as Products; Task.Factory.StartNew(() =&gt; { var topOrderQuery = (from orderDetail in new XPQuery&lt;OrderDetails&gt;(new Session()) where orderDetail.ProductID.ProductID == currentProduct.ProductID orderby (orderDetail.UnitPrice * orderDetail.Quantity) descending select new TopOrder { OrderId = orderDetail.OrderID.OrderID, TotalSales = orderDetail.UnitPrice * orderDetail.Quantity }).ToList().Take(10); DispatcherExt.CurrentDispatcher.BeginInvoke(new Action(() =&gt; { this.TopProduct = topOrderQuery; })); var orderPerYearQuery = (from order in new XPQuery&lt;OrderDetails&gt;(new Session()) where order.ProductID.ProductID == currentProduct.ProductID group order by new { order.OrderID.OrderDate.Year } into g select new OrderPYear { TotalOrder = g.Count(), OrderYear = g.Key.Year }).ToList(); DispatcherExt.CurrentDispatcher.BeginInvoke(new Action(() =&gt; { this.OrderPerYear = orderPerYearQuery; })); var salesPerYearQuery = (from order in new XPQuery&lt;OrderDetails&gt;(new Session()) where order.ProductID.ProductID == currentProduct.ProductID group order by new { order.OrderID.OrderDate.Year } into g select new SalesPYear { Sales = g.Sum(p =&gt; p.UnitPrice * p.Quantity), Year = g.Key.Year }).ToList(); DispatcherExt.CurrentDispatcher.BeginInvoke(new Action(() =&gt; { this.SalesPerYear = salesPerYearQuery; })); }); } </code></pre> <p>I tried to solve this warning by following suggestions given in the msdn but not succeeded. Can anybody help me to solve this warning ??</p> <p>Thanks &amp; regards, Rudresh </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USRudresh Bhatt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThere are a bunch of classes that you can't see, generated by the Linq query comprehensions. The code analyzer sees them but is noddy about it, just suppress the warning.
      singulars
      1. POHow to solve code analysis warning CA1506 : "Avoid excessive class coupling"
      1. USHans Passant
    2. COHello Hans,Thanks for your suggestion but I got the solution.
      singulars
      1. POHow to solve code analysis warning CA1506 : "Avoid excessive class coupling"
      1. USRudresh Bhatt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload