This is a migrated thread and some comments may be shown as answers.

Adding domain model failing

26 Answers 481 Views

Data Access Free Edition

This is a migrated thread and some comments may be shown as answers.

This question is locked. New answers and comments are not allowed.

26 Answers, 1 is accepted

answered on 25 Mar 2010, 05:54 PM

Hello MrWilder,

The wizard you tried to start is actually the old Enable project wizard which is not needed if you want to work with the new visual designer. You can add a domain model item by opening the project's context menu, then Add -> New Item... From the Add New Item dialog select the Telerik OpenAccess Domain Model template and follow the wizard.
Note that you cannot add such an item in a Web site project. It is required that the project containing the .rlinq item can be compiled to an assembly, so please use some of the other Visual Studio templates (Web Application, Windows Application, Class Library, etc.) or create the model in a separate Class library project and reference that project from the Web Site.
You can find additional information about how the designer and the model are used in the OpenAccess Tasks chapter of the documentation which is installed with the product. Unfortunately the online documentation is not updated yet. Hope that helps.

Sincerely yours,
Alexander
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

answered on 07 Apr 2010, 08:00 PM

addnew.png

I'm trying to follow these directions, but I do not see the OpenAccess Domain Model template. Any idea why?

I am using a newly created RadControls C# Silverlight project. I just installed downloaded and installed the new Data Services Wizard on top of the Q1 release.

answered on 08 Apr 2010, 03:31 PM

Hello James,

Please note that at the moment the domain model templates are not installed in Visual Studio 2010. There are some breaking changes in the code generation introduced in VS2010 that hopefully we will be able to avoid soon in one of the next builds.
Additionally, it is not recommended to add .rlinq files to WPF or Silverlight projects. Please use a separate Class library project to keep the domain model items and reference that project from the Silverlight application. This is the most clean and bullet-proof approach.

Best wishes,
Alexander
the Telerik team

answered on 09 Apr 2010, 03:11 PM

Hi James,

You should be able to create a new Class Library project in your solution but you cannot reference it from a Silverlight project because the Silverlight Framework is only a subset of of the .NET Framework. What you can do is create a Silverlight Class Library project, but you will not be able add a Domain Model in it, because System.Data cannot be added as a reference.

The preferred approach when developing Silverlight applications is to create a service that is consumed by the application. I think that the new Data Services Wizard will be of great help to you.

If you need further assistance, do not hesitate to contact us.

Kind regards,
Serge
the Telerik team

answered on 28 Apr 2010, 04:27 PM

Hi Alexander,

I'm evaluating the data model disigners. I added a Datamodel consiting of a single entity to my business objects class library.
I noticed that the generated class doesn't include any kind of mapping information (attributes).
I'm trying to use this genereted class within a system that was already working with a forward mapped class. So, I created a new dll for it, which I replaced in my solution. In other words, I removed my original BusinessOjects project and added a new one instead, containing my Domain Model.
In theory, everithing should work normally. But when I try to run my application the following error occurs when trying to instantiate the database object:

The assembly 'BusinessObjects' does not have a config file with an openaccess node.

And it's true... indeed. The generated config file contains just this:

xml version="1.0" encoding="utf-8"?>

configuration>

connectionStrings>

add name="WorkHoursEntityDiagrams" connectionString="data source=SANDIA\SQLEXPRESS;initial catalog=WorkHours;integrated security=True" providerName="System.Data.SqlClient" />

connectionStrings>

configuration>

The code I'm using to get the database object is as follows:

Telerik.OpenAccess.

Database.Get("WorkHoursEntityDiagrams");

Even I was not convinced, I supposed I had to enable the project to get the required openaccess nodes inside the config file. But when I tryed that approach it failed telling me that I cannot enable a proyect that already contains a domain model.
So, I seem to be in a dead-end street. I can't 'foward map' my entity nor I can run my application.

What may I be doing wrong here?

Best wishes,

Gonzalo

answered on 29 Apr 2010, 12:55 PM

Hello gmendez,

You are going in the right direction. In fact you cannot add a Domain Model to a project and 'enable' it. You were correct to delete your project and create a new one. The issue here lies in the fact that we have changed the way one works and queries OpenAccess.

If you are using the Model Designer you should use the created context class to create and execute queries. We are now working on extending the documentation and providing new samples, code libraries and knowledge base articles on this topic, but for the time being you can check this sample project as it shows how to use the new context.

I do hope this helps.

Best wishes,
Serge
the Telerik team

answered on 13 May 2010, 05:53 PM

Hello Josh McCullough,

This is true, but this way you can not use the new Visual Domain Model Designer, but you are obliged to develop your application using the old wizards approach. What everyone in this forum thread is actually asking for is support for the new Telerik Domain Model Designer.

As to the time frame, we hope to deliver the build next week. As I have mentioned earlier, I will keep you posted on the progress in this thread.

Greetings,
Serge
the Telerik team