繁體中文当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
- ASP.NET
- 紧跟潮流:剖折QQ魔法表情实现原理
- VB PDU mode 7 bit 解码
- 在主页面初始化时先打开连接
- VB6窗体的生命周期
- 为.net中的ListBox控件添加双击事件
- VB6中ADO流对象实现对二进制大型对象的读取方法
- CASSINI源代码分析(4)
- Mono开发指南：第一章 Mono介绍
- ADO.NET Quiz 之对象序列化
- Mono开发指南：第二章 安装Mono
- Mono开发指南：第四章 Mono 初览
- 蛙蛙推荐：C#编码规范.doc
- Mono开发指南：第三章 Hello Mono
- Additional SOAP Namespaces Referenced In WSE 2.0 SOAP Headers
- Mono开发指南：第五章 Gtk#编程
- CASSINI源代码分析(5)：总结
- .Net线程学习手记(1)
- 关于C#中的结构(下)
- 如何用C＃在Excel中生成图表？
- Internet Explorer编程简述(一)
ASP.NET 中的 The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
出处:互联网 整理: 软晨网（RuanChen.com） 发布: 2009-11-03 浏览: 150 ::
收藏到网摘: 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
