Skip to Content

CRVS2010 – two month assessment from Dr. Doom

Those who know me well, often call me Dr. Doom. According to them I tend to see the dark side of things more than the lighter side. Well, with CRVS2010 – no Dr. Doom. Having supported the Beta of CRVS2010, I am quite content with the release. Are there issues? Absolutely – and I’ll document  the most pressing or reported issues along with possible work-arounds or even solutions. I will also touch on issues such as 32 / 64 bit confusion, SilverLight and the WPF viewer. I’ve decided to break up this blog into “user” issues and Crystal Reports issues. Oh, one more thing. I mention Service Pack 1 for CRVS2010 in a number of places in this blog. I suspect the obvious question is;  ETA? Answer; End of February(?). And remember, this is an ETA, not a guarantee(!).  *User Issues*  Creating a new Windows application in VS2010, there is no Crystal Reports viewer available from the .NET Toolbox. The reason for this is that the project must be set to use the Full 4.0 framework, not the .NET  Framework 4 Client Profile.
/
1 Comment
You must be Logged on to comment or reply to a post.
  • We use Web Deployment Projects for packaging our websites.  We install the CR runtime separately in production, because we update our websites quite often, and this makes the packaging simpler too.  But after upgrading to VS 2010 with CR 2010, we kept getting the common log4net.dll error on build, but the work around is quite different and I haven’t seen any documentation on it.  So I thought I would pass this on to you.  Compiling as x32 doesn’t work with WDP.