afbird
Registered: 08/14/08
Posts: 19
|
| Posted 10/15/08 at 10:05 AM | Reply with quote #1 |
|
After following the steps in the article on Crystal Reports Integration using the Crystal Reports Viewer, the only thing holding me back from seeing it work in my app is that I am receiving the following message when I open the report viewer page:
"Could not load file or assembly 'System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)"
I am using ISD 5.2.1, VS2008, .NET 3.5 SP1, and the Crystal Reports tool included in VS2008. All definitions in web.config point to .NET 3.5.0.0.
Any help resolving this problem will be greatly appreciated.
|
| Loading... | |
echo4sos

MVP Developer
Registered: 01/20/06
Posts: 609
|
| Posted 10/15/08 at 02:30 PM | Reply with quote #2 |
|
You may have an incorrect version of the assembly trying to load. If you are using VS 2008, it should be this:
Code:
__________________ -Bill |
| Loading... | |
afbird
Registered: 08/14/08
Posts: 19
|
| Posted 10/15/08 at 03:33 PM | Reply with quote #3 |
|
Thanks for your kind reply. Within the web.config file, the assembly settings are as shown in the snippet of code below. If you notice, the correct version (3.5.0.0) is being referenced.
It seems like some hidden code, maybe AJAX, is invoking 2.0.0.0 regardless of this definition. Somebody had replied in another thread that setting the System.Web.Extensions.dll reference to "Copy Local=True" would force the use of the right version. However, that requires converting the Web Site Project into a Web Application Project in Visual Studio and that carries its own slew of other issues.
By the way, since I'm using .NET 3.5, the right version of AJAX is also installed. Could Crystal Reports be the culprit?
Code:
|
| Loading... | |
afbird
Registered: 08/14/08
Posts: 19
|
| Posted 10/16/08 at 06:01 AM | Reply with quote #4 |
|
Solved it!!!
You need to change the "bindingRedirect oldVersion" range for the System.Web.Extensions.dll in the "runtime" section in the web.config file from "1.0.0.0-1.1.0.0" to "1.0.0.0-3.0.0.0" as shown below (Note: I remarked the replaced entries). Once this is done, the app looks for the 3.5 version instead of the 2.0.0.0 as it originally wanted.
Code:
|
| Loading... | |
JimiJ

MVP Developer
Registered: 03/31/05
Posts: 4,808
|
| Posted 10/16/08 at 03:53 PM | Reply with quote #5 |
|
Alfredo,
That's very helpful post!
Thanks, __________________ Jaime Jegonia
JimiTron Software
JimiTron.Net | JimiTron.Com
"...and whoever sows generously will
also reap generously" 2 Cor 9:6 |
| Loading... | |
vijaygarg
Registered: 01/13/09
Posts: 1
|
| Posted 01/13/09 at 03:08 AM | Reply with quote #6 |
|
Solved for me also. thanks !!!
|
| Loading... | |