Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have project which is currently working and was developed long time back on dot net famework 1.1. Now here we are using visual studio 2010 and when i make any modifications to the project and upload it, I get error regarding compatibility. Can I convert this project so that I can make changes and it doesn’t give me compatibility problem on uploading on server? If yes, can u please tell me how? Or will I have to write the whole project again?
i53.tinypic.com/9iwk6w.jpg
tinypic.com?ref=9iwk6w
The error indicates that the application running on the server can’t find the Crystal Reports libraries. Those will need to be deployed to or installed on the server.
The Crystal Reports was dropping with Visual Studio 2010. If you upgraded your workstations to 2010 then the runtime libraries are likely still there from a previous version (note that multiple versions of VS run concurrently on the same machine just fine). So the code will continue to build and run fine locally because the Crystal Reports libraries are globally available on the workstations.
What is your build/deploy process? It seems that it was including the Crystal Reports runtime libraries previously but isn’t now. When building in Visual Studio 2010, if the code has a dependency on the Crystal Reports libraries, where are the references pointing? You’ll probably want to encapsulate those references into the build rather than rely on pulling them from the GAC or wherever you’re getting them. Maybe include them in a lib folder with other 3rd party DLLs, etc.