For now, the best thing to do when you need to regenerate in another language is to physically remove the DomainModel and AppHelper projects altogether - from both the solution and the file system.  Then open up OM and try again.

 

I mispoke in the previous update, the Apphelper is not re-created properly and I now have a new file entitled "ServerNorthwindIB1.Designer.vb which causes duplicate definitions since there is also a file "ServerNorthwindIB.Designer.vb in the project. Remove one of them and now clean compile (except for the expected warnings).

 

Continued to add a form and a simple query and received an Invalid Operation Exception:

 

An error occurred creating the form. See Exception.InnerException for details.  The error is: Error in EdmKey Default: Unable to locate an ObjectContext in the probe assemblies.  This is often caused by not copying your EF model 'dll' to the deployment directory.  This will be either the client application directory in a two tier deployment or the server deployment  directory in an n-tier deployment.

 

This may be a result of my manual intervention so, I guess I'll start again from scratch.

I removed the Apphelper and DomainModel projects from the VS Solution Explorer and then loaded DevForce EF OM again and did a save. The Apphelper project re-built properly but the DomainModel project was re-built with both C# and VB classes again. Not what I wanted. In order to get things to work I had to remove the projects, manually remove all files except the .ibedmx file, reload Object Mapper and Save.

 

BTW, I know this is Beta1 and I expect issues; that's why I'm testing. Since I don't know what Beta1 really means in terms of the state now v.s. what is planned for the intiial release, please take the issues that I report as bugs or features I consider lacking now. No critisizm intended!