OpenAccess_UseMSBuild="True" is EVIL in 2010Q1

[Ryan Norris]

So, to save everyone a lot of time...

We recently moved up to 2010Q1 release from the 2009Q3 release.  Initially, we encountered the problem described in this thread that required us to remove the project reference to the OpenAccess.targets file.  But that lead us to having our assemblies not enhanced by OA, and that lead to runtime issues.

The problem lies in this snippet from your project file - which has Telerik rely on MSBuild for enhancement tasks rather than the AddIn for VS.

  <ProjectExtensions>

    <VisualStudio>

      <UserProperties OpenAccess_ConfigFile="App.config" OpenAccess_ConnectionId="DatabaseConnection1" OpenAccess_Enhancing="True" OpenAccess_UpdateDatabase="True" OpenAccess_EnhancementOutputLevel="3" OpenAccess_UseMSBuild="True" />

    </VisualStudio>

  </ProjectExtensions>

OpenAccess_UseMSBuild is evil with this purported "fix" for the linked-to transient field issue.  You have been warned.

[Serge]

Hi Ryan Norris,

Can you please elaborate a bit on what approach you want to use? Are you trying to use the Reverse Mapping wizard or you want to use the new Domain Model?

What these lines you posted do is tell the enhancer that this is a reverse mapping scenario (via the old wizards). If you however want to use a domain model you should delete them and use the ones you previously commented.

Please give us more information on what you want to do so that we will be better able to help you. Looking forward to your reply.

All the best,
Serge
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.

[Ryan Norris]

This is an existing project that started on the 2009Q3 version and migrated to 2010Q1 as part of a purchase of the enterprise development license.  We have always forward engineered our database from classes.

There is some evidence that enhancement using the Telerik MSBuild tasks is not working at all, which makes me suspect that migration and other responsibilities of the MSBuild tasks are not working either.  I'll be investigating this over the next day or so - but this upgrade experience seems to indicate that the scenario where users of prior versions would be upgrading was completely ignored or undervalued.

[Serge]

Hi Ryan Norris,

 Let me clarify a bit here. Prior to the 2010 Q1 release the Forward Mapping wizard and Reverse mapping wizard were available. In the Q1 release we introduced the new Visual Designer, which currently only supports reverse mapping scenarios.

We fully support upgrade to our latest release for all our users. There is one thing to note though due to the breaking changes we introduced with the new Domain Model and the new enhancer: currently you can't and shouldn't add this model to an already enabled project. This will lead to a ton of errors and is not supported. It will be helpful for us to know your goal, are you trying to work with the new Visual Designer or are you trying to just move to the new version but still work with the old wizards approach?

Also we are currently working on an Upgrade Tool that will convert a project from the wizards approach to the new Domain Model one. 

If you can elaborate on the actual circumstances that troubled you we would like to further investigate this issue. 

We are looking forward to resolving this problem.

Have a great day,
Serge
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.