1. 首頁
  2. 問答
  3. BIDS 2008 SSRS項目顯示感嘆號

BIDS 2008 SSRS項目顯示感嘆號

2012-07-03 101 views
1

我創建了一個包含多個SSRS報告項目的解決方案。每個項目都包含一些報告文件（.RDL）的定義。它們被分成多個項目，因爲每個項目都使用不同的部署目錄。BIDS 2008 SSRS項目顯示感嘆號

我在TFS 2010中檢查瞭解決方案。我正在爲開發人員準備如何獲得解決方案的文檔，所以我將其備份並從工作站中刪除。我在BIDS 2008中做了一個簡單的「從源代碼控制打開」的命令。該項目從源代碼控制中拉出，最後到達完全相同的位置，文件夾結構和文件名完全相同。但是，每個項目中的每個RDL都有一個帶有感嘆號的鎖，旁邊有一個黃色圖標。我正在尋找這個圖標顯示的原因，但根本沒有看到它。

我已經研究了互聯網上的問題，但大多數情況下，那裏的一切都指在項目之間移動文件或缺少依賴關係引用。這裏我沒有這些問題。

任何人都可以建議什麼是警告圖標的原因，或診斷方法？

來源

2012-07-03 beeen

回答

3

我有同樣的確切問題。我所要做的就是關閉BIDS exe並重新運行它。從「最近的項目」鏈接再次打開解決方案後，項目打開並且驚歎號消失了！希望你現在也明白了這一點。

來源

2012-09-26 16:01:49 Jay

1

首先，我會爲您解釋發生了什麼的xml代碼的數量表示歉意。

我們在這裏有同樣的問題。我發現，無論出於何種原因，當新的報告文件被添加到項目中時，無論名稱如何，它都會將它放在解決方案資源管理器的列表末尾。

此外，它將這作爲列表中的最後一個孩子。在提交到TFS並將它拉回來的xml節點仍然是相同的方式，但在您的解決方案資源管理器中，文件以正確的alpha順序出現。但是，由於項目xml和解決方案資源管理器不同步，因此會顯示感嘆號。

我找到的解決方案是卸載項目文件，然後編輯xml，使元素按正確的順序排列。

例

<Reports> 
<ProjectItem> 
    <Name>AccountGroupListing.rdl</Name> 
    <FullPath>AccountGroupListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ApprovalRouteListing.rdl</Name> 
    <FullPath>ApprovalRouteListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BalanceSheetWCodesReport.rdl</Name> 
    <FullPath>BalanceSheetWCodesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BalanceSheetWOCodesReport.rdl</Name> 
    <FullPath>BalanceSheetWOCodesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BankAccountListing.rdl</Name> 
    <FullPath>BankAccountListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BankReconDetail.rdl</Name> 
    <FullPath>BankReconDetail.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BankReconSummary.rdl</Name> 
    <FullPath>BankReconSummary.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BasicBudgetProof.rdl</Name> 
    <FullPath>BasicBudgetProof.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BillsToBeApproved.rdl</Name> 
    <FullPath>BillsToBeApproved.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ChartOfAccountsListing.rdl</Name> 
    <FullPath>ChartOfAccountsListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryGuideListing.rdl</Name> 
    <FullPath>DoubleEntryGuideListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryPaymentProcessing.rdl</Name> 
    <FullPath>DoubleEntryPaymentProcessing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryReport.rdl</Name> 
    <FullPath>DoubleEntryReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryReportDetail.rdl</Name> 
    <FullPath>DoubleEntryReportDetail.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>InvoiceForm.rdl</Name> 
    <FullPath>InvoiceForm.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>InvoiceFormSelfSealer.rdl</Name> 
    <FullPath>InvoiceFormSelfSealer.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PaymentHistory.rdl</Name> 
    <FullPath>PaymentHistory.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PaymentRegisterDetailReport.rdl</Name> 
    <FullPath>PaymentRegisterDetailReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PaymentRegisterSummaryReport.rdl</Name> 
    <FullPath>PaymentRegisterSummaryReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>POByAccountCode.rdl</Name> 
    <FullPath>POByAccountCode.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>POPaperlessDistibutions.rdl</Name> 
    <FullPath>POPaperlessDistibutions.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PORequiresPayment.rdl</Name> 
    <FullPath>PORequiresPayment.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ProrationListing.rdl</Name> 
    <FullPath>ProrationListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PurchaseOrderForm.rdl</Name> 
    <FullPath>PurchaseOrderForm.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PurchaseOrderFormLineItems.rdl</Name> 
    <FullPath>PurchaseOrderFormLineItems.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ReceivablesReport.rdl</Name> 
    <FullPath>ReceivablesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RequisitionApprovalAudit.rdl</Name> 
    <FullPath>RequisitionApprovalAudit.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RequisitionForm.rdl</Name> 
    <FullPath>RequisitionForm.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RequisitionProof.rdl</Name> 
    <FullPath>RequisitionProof.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RevenuesReport.rdl</Name> 
    <FullPath>RevenuesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>UnapprovedRequisitions.rdl</Name> 
    <FullPath>UnapprovedRequisitions.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>VoidPayments.rdl</Name> 
    <FullPath>VoidPayments.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>LoriTest.rdl</Name> 
    <FullPath>LoriTest.rdl</FullPath> 
</ProjectItem>

通知的LoriTest.rdl是怎麼VoidPayments.rdl文件之後到來。如果你看看我的圖像，圖標是否有驚歎號。

Solution Explorer

我的同事加入這個文件，犯下的變化和我拉下來。該文件在解決方案資源管理器中以正確的順序出現，但不在實際的項目xml中。如果我關閉BIDS並重新打開標記消失，但項目文件仍然混亂，直到我添加一個新文件。現在我的文件放在最後，loritest.rdl在列表中移動到正確的alpha順序。

看到我的第二張圖片。

Solution Explorer 2

現在看項目文件代碼

<Reports> 
<ProjectItem> 
    <Name>AccountGroupListing.rdl</Name> 
    <FullPath>AccountGroupListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ApprovalRouteListing.rdl</Name> 
    <FullPath>ApprovalRouteListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BalanceSheetWCodesReport.rdl</Name> 
    <FullPath>BalanceSheetWCodesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BalanceSheetWOCodesReport.rdl</Name> 
    <FullPath>BalanceSheetWOCodesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BankAccountListing.rdl</Name> 
    <FullPath>BankAccountListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BankReconDetail.rdl</Name> 
    <FullPath>BankReconDetail.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BankReconSummary.rdl</Name> 
    <FullPath>BankReconSummary.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BasicBudgetProof.rdl</Name> 
    <FullPath>BasicBudgetProof.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>BillsToBeApproved.rdl</Name> 
    <FullPath>BillsToBeApproved.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ChartOfAccountsListing.rdl</Name> 
    <FullPath>ChartOfAccountsListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryGuideListing.rdl</Name> 
    <FullPath>DoubleEntryGuideListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryPaymentProcessing.rdl</Name> 
    <FullPath>DoubleEntryPaymentProcessing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryReport.rdl</Name> 
    <FullPath>DoubleEntryReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DoubleEntryReportDetail.rdl</Name> 
    <FullPath>DoubleEntryReportDetail.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>InvoiceForm.rdl</Name> 
    <FullPath>InvoiceForm.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>InvoiceFormSelfSealer.rdl</Name> 
    <FullPath>InvoiceFormSelfSealer.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>LoriTest.rdl</Name> 
    <FullPath>LoriTest.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PaymentHistory.rdl</Name> 
    <FullPath>PaymentHistory.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PaymentRegisterDetailReport.rdl</Name> 
    <FullPath>PaymentRegisterDetailReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PaymentRegisterSummaryReport.rdl</Name> 
    <FullPath>PaymentRegisterSummaryReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>POByAccountCode.rdl</Name> 
    <FullPath>POByAccountCode.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>POPaperlessDistibutions.rdl</Name> 
    <FullPath>POPaperlessDistibutions.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PORequiresPayment.rdl</Name> 
    <FullPath>PORequiresPayment.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ProrationListing.rdl</Name> 
    <FullPath>ProrationListing.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PurchaseOrderForm.rdl</Name> 
    <FullPath>PurchaseOrderForm.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>PurchaseOrderFormLineItems.rdl</Name> 
    <FullPath>PurchaseOrderFormLineItems.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>ReceivablesReport.rdl</Name> 
    <FullPath>ReceivablesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RequisitionApprovalAudit.rdl</Name> 
    <FullPath>RequisitionApprovalAudit.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RequisitionForm.rdl</Name> 
    <FullPath>RequisitionForm.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RequisitionProof.rdl</Name> 
    <FullPath>RequisitionProof.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>RevenuesReport.rdl</Name> 
    <FullPath>RevenuesReport.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>UnapprovedRequisitions.rdl</Name> 
    <FullPath>UnapprovedRequisitions.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>VoidPayments.rdl</Name> 
    <FullPath>VoidPayments.rdl</FullPath> 
</ProjectItem> 
<ProjectItem> 
    <Name>DerekTest.rdl</Name> 
    <FullPath>DerekTest.rdl</FullPath> 
</ProjectItem>

我發現，您需要做的是在你，這意味着增加一個新文件的人，需要要做的是在添加新的報告文件之後，卸載項目文件並直接編輯項目文件以按照正確的順序放置文件。您不必絕對做到這一點，但如果您在提交之前沒有得到答案，那麼當多個人在添加報告時會遇到問題，因爲他們會在項目文件中被覆蓋，但他們，報告，存在於源代碼管理中。

希望這有助於解釋發生了什麼。我還沒有真正找到解決這個問題的解決方案。我的想法是創建一個腳本或VS插件來解決訂購問題。你會認爲微軟會在VS/BIDS中注意到這個bug，並且有一個修補程序，但是我還沒有找到它。

來源

2014-01-17 15:05:10 dklingman

相關問題

 相關問題