繁體中文当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
- ASP.NET
- 自定义控件（支持模板）
- 自定义控件（模板+数据绑定）
- 自定义控件(可以动态加载用户控件)
- 在代码隐藏中遍历当前页的所有控件
- 关于C#调用Office Web Components绘图的问题
- 利用Visual C#打造一个平滑的进度条
- [VB] 防止程序运行多个实例
- Visual Studio.Net 快捷键表
- WinForm中ToolBar与TabControl的一些事件写法（C#）
- 【翻译】Managed DirectX（第六章）
- 利用.NET语言开发自己的脚本语言(一)
- 自动改变CheckBoxList选择项目的背景颜色
- vb.net中windows服务的创建
- BASE64编码规则及C#实现
- .net中判断该应用程序是否已经启动,防止重复启动
- XML Web Service 数据交换
- 开发花絮：一个DataList的ItemCommand事件意外
- Snake.Net中的ORM(二)
- ASP操作XML数据小结
- 可用来显示空值的时间选择控件4
ASP.NET 中的 The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
出处:互联网 整理: 软晨网（RuanChen.com） 发布: 2009-11-03 浏览: 42 ::
收藏到网摘: 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
