繁體中文当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
- ASP.NET
- blog程序新版本V2.0 Beta完成,提供V1.0全部源码下载
- “/”应用程序中的服务器错误
- asp.net(c#)复数类(复数加减乘除四则运算)
- asp.net(c#)不可访问，因为它受保护级别限制
- asp.net(c#) 水仙花数
- ASP.NET实现用图片进度条显示投票结果
- asp.net(c#) MS AJAX的安装
- asp.net(c#)有关 Session 操作的几个误区
- ASP.net基础知识之常见错误分析
- [.net] 操纵自如-页面内的配合与通信
- c# static的全部用法收集整理
- 使CheckBoxList的Attributes属性生效（修改微软的一个bug）
- 在ASP.NET中使用Session常见问题集锦
- [原创]完美解决Could not load file or assembly ''AjaxPro.2'' or one of its dependencies. 拒绝访问。
- 在Apache环境下成功的运行ASP.NET的注意事项
- ClickOnce DIY全自动更新下载升级的自我实现
- asp.net jscript 一句话木马
- 在ASP.Net中实现flv视频转换的代码
- 将DataTable中的一行复制到另一个DataTable的方法
- 在DataTable中执行Select("条件")后，返回DataTable的方法
ASP.NET 中的 The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
出处:互联网 整理: 软晨网（RuanChen.com） 发布: 2009-11-03 浏览: 73 ::
收藏到网摘: 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
