繁體中文当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
- ASP.NET
- 动态加载Js代码到Head标签中的脚本
- asp.net Parameters.AddWithValue方法在SQL语句的 Where 字句中的用法
- ASP.NET 运行时错误: 没有为扩展名“.asax”注册的生成提供程序修正版
- Convert.ToInt32与Int32.Parse区别及Int32.TryParse
- WebService出现"因 URL 意外地以 结束，请求格式无法识别"的解决方法
- asp.net(C#) Xml操作(增删改查)练习
- asp.net 分页sql语句(结合aspnetpager)
- asp.net开发与web标准的冲突问题的一些常见解决方法
- asp.net Repeater中使用if的代码
- Asp.net FCKEditor 2.6.3 上传文件没有权限解决方法
- C# 命名规则(挺不错的)
- asp.net 动态生成控件并获取其值
- 使用DataGrid中扩展ItemRenderer和HeaderRenderer进行操作
- asp.net Hashtable 遍历写法
- asp.net GridView和DataList实现鼠标移到行行变色
- C# 邮件地址是否合法的验证
- .net发送邮件实现代码
- ASP.Net 上传图片并生成高清晰缩略图
- asp.net 事件与委托分析
- C# 无限级分类的实现
ASP.NET 中的 The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
出处:互联网 整理: 软晨网（RuanChen.com） 发布: 2009-11-03 浏览: 105 ::
收藏到网摘: 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
