When will hlsl compilation be supported in C# projects

Hi,

I notice that Visual Studio 2013 still doesn't recognize hlsl files inside a C# project, so the situation remains that I have to include a C++ project in all of my solutions to compile the hlsl shader files.

When will this be fixed ?

When will hlsl compilation be supported in C# projects

Hi Gavin,

I have no experience on hlsl file and don’t know when repair will. But do not be disappointed. We could use UserVoice to post your requirement. Please refer to the following link. http://visualstudio.uservoice.com/forums/121579-visual-studio/category/31481-net.

Regards,

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

Click HERE to participate the survey.

SQL Query Totals Grouping Subtotals

Group by requires aggregate function (AVG, SUM, ...) and chances are you didn't use any aggregate function that's why you're getting an error.

SELECT columnName, aggregateFunction(columnName)

FROM tableName

WHERE columnName ...

GROUP BY columnName;

SQL Query Totals Grouping Subtotals

A couple ideas:

SELECT  [SystemNum]
      ,[PurchaseDescription]
      ,[ModelNumber]
      ,[Brand]
      ,SUM([Quantity]) as Quantity
      ,SUM([Cost]) as Cost
      ,SUM(Quantity*Cost) AS 'Amount'

FROM [Equipment].[dbo].[SystemsComponents]
group by [SystemNum]
      ,[PurchaseDescription]
      ,[ModelNumber]
      ,[Brand]


SELECT [ID]
      ,[SystemNum]
      ,[PurchaseDescription]
      ,[ModelNumber]
      ,[Brand]
      ,[Quantity]
      ,[Cost]
      ,SUM(Quantity*Cost) 
         OVER (Partition by [SystemNum]) AS 'Amount'

FROM [Equipment].[dbo].[SystemsComponents]

Depends upon what you want to display on each row.

---

Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

SQL Query Totals Grouping Subtotals

I've been trying to use Sum() with GROUP BY but I get errors regarding the other fields that I'm not summing or grouping.

SELECT [ID]
      ,[SystemNum]
      ,[PurchaseDescription]
      ,[ModelNumber]
      ,[Brand]
          ,[Quantity]
      ,[Cost]
          ,Quantity*Cost AS 'Amount'
          ,SUM(Quantity*Cost) AS 'Total'
  FROM [Equipment].[dbo].[SystemsComponents]
  GROUP BY 
      [SystemNum]

Msg 8120, Level 16, State 1, Line 2

Column 'Equipment.dbo.SystemsComponents.ID' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.

---

why767

T-SQL: Performance Issues with View; runs slow

Two tips:

1. Lose the DISTINCT keyword. For a query like this - depending on the amount of rows returned - it is a performance killer


2. Check if you have useful indexes for the predicates in the WHERE clause, and for each JOIN

The fact that a selection of one table takes up to 15 seconds, and that of another table also takes up to 15 seconds, is no guarantee that if those results are joined together that the performance is anywhere close to 30 seconds. On the other hand, eliminating some joins from the query might point to where your indexes are not very useful.

---

Gert-Jan

SSRS Report - Grouping/Merging similar columns in daily view of data

Hi GDov,

In Reporting Services, once we add a row (column) next to an existing group, the row will be automatically added based on that group. Because groups are organized as members of group hierarchies. Row group and column group hierarchies are identical structures on different axes. Think of row groups as expanding down the page and column groups as expanding across the page. So in your scenario, if weekday field is above the projects, we cannot make that child group grouped by P1 (the fifth row in your screenshot) to be displayed as you expect. This is by design.

Based on my further research, if there is no other group act as parent group of weekday field, we can refer to the steps below to work around this issue:

1. Move the rows from higher than the weekday to lower.


2. In the Column Groups pane, right-click the Weekday group to add a parent group grouped by Value.


3. Right -click the Value group to add a parent group grouped by P3 (the last row in your screenshot).


4. Use the same logic to add P2 (the sixth row in your screenshot) and P1 groups.


5. Delete the Sorting values in all groups.

The following screenshot is for your reference:

If you have any other questions, please feel free to ask.

Thanks,

Katherine Xiong

---

Katherine Xiong

TechNet Community Support