繁體中文当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
- ASP.NET
- ADO+ 引导数据种类的演变(转自 ms 一)
- C#抢鲜快报之FAQ20
- 通过指定IP地址得到当前的网络上的主机的域名
- 网上追捕(很多实用的port)
- asp+中的发送者是什么意思
- 一个完整的网上追捕的原程序
- C#里操作时间的例子!
- 查看主机的内存使用情况
- asp+中是如何连接数据库ado+的
- 一个用c#写的扫描asp源码漏洞的应用程序
- 一个用c#写的扫描asp源码漏洞的应用程序(续)
- 两个获取http页面的c#函数
- asp.net高级教程（一）---asp.net , 还是asp+ ？
- asp.net高级教程（二）--- 转换编程思维
- asp.net高级教程（三）---对象
- asp.net高级教程（三）---实战篇
- asp.net高级教程（五）---实战篇(中)
- C#消息队列应用程序 -1
- C#消息队列应用程序 -2
- 使用 ASP+ 列表绑定控件（上）
ASP.NET 中的 The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed
出处:互联网 整理: 软晨网（RuanChen.com） 发布: 2009-11-03 浏览: 147 ::
收藏到网摘: 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
