I have a support ticket on this, but maybe someone can answer before they do...
I have created a sample project using Open Access ORM based on video:
http://telerikwatch.com/search/label/OpenAccess%20ORM
As per the above example, I create my ORM class, add the project to my web project, add a reference, etc., add a radgrid to the default page and bind it to the ORM menu table. Locally, I run it in debug and it opens up my grid fine.
I am now trying to publish it remotely to my windows server 2008 web server. I have never done a "project" publish before, only copying website files. So what's happening could very well be my stupidity, as usual.
I use "Build" and "publish websitename." I've tried all 3 Copy options, only files needed, all project files, all files in sourcefolder, and checked Include files from app_data. I publish, it's a successful publish.
I go to run my web site and it errors:
Parser Error Message: An error occurred creating the configuration section handler for openaccess: Could not load file or assembly 'Telerik.OpenAccess.Config, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342' or one of its dependencies. The system cannot find the file specified.
Line 15: <section name="openaccess" type="Telerik.OpenAccess.Config.ConfigSectionHandler, Telerik.OpenAccess.Config, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342" />
Here is my generated web.config with openaccess section too:
<openaccess xmlns="http://www.telerik.com/OpenAccess">
<references>
<reference assemblyname="OOpOrm" configrequired="True" />
</references>
<connections />
</openaccess>
So locally, works. Remotely doesn't.
What am I lacking? thanks.
Moon.
9 Answers, 1 is accepted
You can find in our help section what exactly libraries you need on the server where you publish the site project. The resource is available at: http://www.telerik.com/help/openaccess-orm/runtime-libraries.html.
Or you just add all the libraries from the OpenAccess runtime directory to your applications directory.
Please tell us whether this helps.
Best wishes,
Dimitar Kapitanov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Rank 2
>>Or you just add all the libraries from the OpenAccess runtime directory to your applications directory.
Do you mean to add all the dll's from:
c:/program files/telerik/openaccess orm/bin
??
Yes, sorry the bin was named runtime before.
Best wishes,
Jan Blessenohl
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Rank 1
I too ran into this problem - specifically I publish to the IIServer on my development system, and when I am happy with the results I copy the content to the production server.
This process works quite happily for the RadControls since the necessary DLLs are installed in the bin folder for me. But only some of the OA DLLs are installed. Since the missing ones are present elsewhere there is no problem until deployment.
I note that some of the necessary DLLs are installed, so why not all of them? (And the related files if necessary, e.g. the PublisherPolicy config files), surely this would be a handy convenience to new users who are more likely to get fed up working through teething problems.
Further when upgrading to a new version, to have the appropraite repalcement DLLs installed automatically would be enormously helpful.
We are aware of the obstacles that pop up when the OpenAccess version is changed and we are working in that direction. In the near future we are going to introduce a new Upgrade wizard which will automatically change all necessary references and dll files when such event occurs.
Regards,
Alexander
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Rank 1
I ran into this same thing on a release to a staging server.
3 mysterious DLLs that I needed to deploy that I did NOT need to have direct references to within the project during development.
Telerik.OpenAccess.Config.dll
Telerik.OpenAccess.Runtime.dll
Telerik.OpenAccess.Adonet2.dll
I'm not sure what all else could go on in the development that may or may not cause others (beyond the basics when working with OA) to be needed upon deployment, but the handy .NET blowup screen will be nice enough to tell you one by one.
It's funny how the entire RadControl toolkit... I need ONE reference/dll.
With OpenAccess I need SEVEN.
Just saying... seems like that can be streamlined. I can't do much of anything without all 7 assemblies, so why not just have 1, so we don't have to chase these things around all the time?
These assemblies are installed in the global assembly cache, and this is the reason why you didn't have direct references. One solution would be to install OpenAccess or manually add the assembly to the GAC on the staging server.
However we will be working the structure of OpenAccess particularly the assembly structure in the near future.
Thank you for the suggestions.
Serge
the Telerik team
Rank 1
Installing or GACing onto our development/testing/staging servers is one thing.
Doing that on client testing and live production servers (by the dozens) is not going to happen. Not only would it be a big hassle, but with most client machines, you are not going to have access to do such things... So, the only thing you can do is make sure you deploy in the BIN...which means you need to remember which ones are needed and make sure they get into the deployment.
I know I'll never remember (at least not without writing it down)... and I don't want to create some complicated build process just for something like this. So, the easiest way for me is to just create a reference to these "mysterious dlls" and make sure COPY LOCAL = TRUE. Then, I have them in the BIN... and then in my PUBLISH (in VS2010) it copies everything out to a client staging folder with everything I need and I don't need to remember anything about it... Just copy/paste the folder to the client.
We have updated the help article that is referring to this issue. I hope that this will be a good starting point for everyone that is deploying OpenAccess applications.
Thank you for your collaboration on the subject.
Serge
the Telerik team