繁體中文当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
- ASP.NET
- ewebeditor在.net的使用方法
- Server.Transfer,Response.Redirect的区别
- ASP.NET2.0+SQL Server2005构建多层应用
- ASP.NET 2.0 中收集的小功能点(转)
- ASP.Net全局变量的设置和读取方法
- 数据库开发总结(ADO.NET小结)
- ASP.net(c#)打造24小时天气预报及实时天气
- 发布WEB站点时出现Server Application Unavailable
- 在asp.net中实现datagrid checkbox 全选的方法
- ASP.NET 2.0 URL映射技巧
- ConfiguraionSource节点及多个配置文件的应用
- SqlConnection.ConnectionString相关关键字
- 如何在WebForm中使用javascript防止连打（双击）
- 看到本质而不是现象--解决ASP.NET CS0016的问题
- 学会区分Visual Studio 2005,Visual Studio 2005 Team System和MSDN Premium 订阅的各个版本
- ASP.NET 入门的五个步骤
- ASP.NET 高性能分页代码
- 动态ItemTemplate的实现(译) - item,template
- 遍历Hashtable 的几种方法
- 通过VS中的数据源选择对话框简单实现数据库连接配置
ASP.NET 中的 The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
出处:互联网 整理: 软晨网（RuanChen.com） 发布: 2009-11-03 浏览: 114 ::
收藏到网摘: n/a
To solve my eariler problems with Crystal Reports, I upgraded to CR 9. This solved the deployment issue I was having, but caused a new problem on my system.
When using a Crystal Report inside Visual Studio, it automatically created a strong named class to go along with the report. A custom tool is executed that generates this code for each report. However, after the upgrade, any new reports I added to any project failed to generate the class files. I would get an error that said:
"The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed."
I figured that the name of the custom tool had probably changed in the new version, but I wasn't able to figure out the new name. I was however curious as to why my old reports were able to continue to build properly, when new ones wouldn't.
Upon closer examination, I noticed that the existing reports in my project had a different custom tool attribute value than the new ones. Changing the custom tool attribute of the new report to match the old reports fixed the problem.
If you are getting this error, but don't have any old reports to look at, try changing the Custom Tool attribute to: 'CrystalDecisions.VSShell.CodeGen.ReportCodeGenerator'. This fixed the problem for me and hopefully will for you too.
评论 (0) All
