Rank 2
--
Stuart
13 Answers, 1 is accepted
You should stay with the way you are working. We will come up with a migration wizard for forward projects later. If you are missing the menus, please have a look here.
Kind regards,
Jan Blessenohl
the Telerik team
Rank 2
Thanks, I think :-) I never get to play with the nice toys!
> If you are missing the menus, please have a look here.
Ta, I'd already found that.
--
Stuart
Rank 1
the new version includes the wizard to change over the old projects? We have a larger model and would like to switch to the designer. Regards Christian
It is possible to use the OpenAccess "Upgrade to Domain Model" tool for the purpose but only if your model was built using the "Reverse Mapping Wizard". If there are any Parts of your model definition that were done with the "Forward Mapping Wizard", I would not recommend you to use the conversion tool as you might end up with some loss of settings that you have manually done before. Anyway, I do not expect that you will have to many problems by just deleting your previous model and importing the model from database into the rlinq designer from scratch.
Regards,Zoran
the Telerik team
Rank 1
this is not a good proposal and a big disappointment. We have many methods in our model and in the get and set parts logic is included, so the conversion is complicated. When I perform such a complex transition, I could also take the EF4 and I'm closer to Microsoft. I do not understand why it is possible to offer a converter for Linq 2 SQL, but not for their own "old" Foward projects. We urgently need the converter, so that we can use the round-tripping. The converter should have to read the attributes and the mapping and than convert to the new form.
Best regards Christian
Rank 2
--
Stuart
Rank 2
Iron
Veteran
I've done this upgrade manually a couple times, and it's really not that bad...
You really just need to identify which objects have custom methods, then in your new domain model project create a new partial class based on that entity and paste in the code. Really, if you can it's SO worth the effort...the domain model API is so slick.
However I do agree that it would be nice to see a release polish existing missing features rather than burn dev time making an SDK demo app and a Linq2Sql converter. I still encounter "X not supported" exceptions at runtime.
Steve
Thanks a lot for your feedback. We have considered this opportunity and it is now part of our backlog to extend our Upgrade Tool from older projects so that it can read the complete mapping - forward, reverse or mixed. We will release an internal build this week, but my personal expectations are to have these features on the tool for the first Service Pack for the Q3 2010 release.
All the best,
Zoran
the Telerik team
Monday, November 15, 11 am Eastern Time: Register here>>
Monday, November 15, 10 pm Eastern Time: Register here>>
Rank 1
I have read the instructions for q3 sp1. My question: Does the SP1 include the announced wizard to migrate from a classic forward model in order to use the designer mode?
Kind regards
Christian
Please excuse me for the misunderstanding that has is probably brought by my latest post in this forum thread. The Service Pack that we just released is actually the internal build that we planned and I mention in my latest post. A Service Pack 1 was planned for later this year. However because of the numerous fixes that we did, we decided to tag this release a Service Pack instead of an internal build. As you probably guess, this is not the release containing the desired functionality, it will be available later this year or in the beginning of the next.
Best wishes,Zoran
the Telerik team
Rank 1
the current schedule contains no information about the next step, or the exact date of publication. When the wizard for 'old' forward projects will be available?
Kind regards
Christian
Actually I have not given you an exact time frame because the migration of the older forward mapping projects is something that is not completely defined on our side, I must admit. We will definitely provide a way for the customers to move their projects to the Visual Designer approach but, doing an automatic upgrade is a risky approach due to the fact that clients writing forward mapping are usually writing their own logic in their persistent classes and there is a possibility for this logic to be gone after we uprade the project and generate the classes ourselves. We are thinking about a feature of the designer that would allow you to include your won classes in the designer without us touching those classes and not generating any code for them so that your code would stay the same as it was before. However that is a feature we have not yet developed and I believe that the only real time frame is Q1 2011 release.
I really apologize for the inconveniences this might be causing you, but this is a really delicate step and we thrive towards doing it in the safest way for our clients.
Also, in the meantime, maybe you could have a look into the fluent mapping API which is another way for you to map your classes using custom code. However if, you are a fan of the designer and would like to do more drag&drop, this is not the approach you should go for.
Zoran
the Telerik team
I would just like to update you guys, that the new Upgrade Wizard is part of the Q1 2011 product. With this version we are able to convert old forward mapping models with the new Fluent Mapping representation of the metadata. So we are not using the designer with Forward Mapping as it always generates code and we would not like to touch the user-defined classes as it is usually with Forward Mapped projects. That is why we took the Fluent Mapping approach. I hope you find it useful to utilize the new API in your existing projects.
Best wishes,Zoran
the Telerik team