Using a managed Visual Studio 2013 Project that is saved in Team Foundation causes a huge delay in checking out the project when a Report folder is included in the build.
- Crystal Reports for Visual Studio
- Visual Studio 2013
- Team Foundation Server
Reproducing the Issue
- Create a new WEB project and including a folder with multiple reports in it
- Do not use strongly-typed reports.
- The web.config file is updated with the following line:
<add extension=".rpt" type="CrystalDecisions.Web.Compilation.RptBuildProvider, CrystalDecisions.Web, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
This causes the project to re-import the report folder which makes the checkout take a long time to complete.
This issue has been escalated to development and is targeted for Service Pack 14 but at this time we cannot confirm when a fix will be provided.
Update from DEV:
This is by design...
For Asp.net WebSite, the cs file is not be generated when you add a Report to the project. , the cs file is generated only when you first time build the project or rebuild the project.
For Asp.net WebProject, the cs file is generated when you add a Report to the project.
So the RptBuildProvider is only for WebSite to generate the cs file and is meaningless for the WebProject.
Crystal reports for visual studio, team foundation, folder, visual studio 2013 , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem