Compartilhar via

Entity Framework Feature CTP 3 Now Available

  • Artigo

The information in this post is out of date.

Visit msdn.com/data/ef for the latest information on current and past releases of EF.

Today we are releasing Entity Framework Feature CTP 3.

This updated preview addresses compatibility with Visual Studio 2010 RC for Code First (the new name for Code Only) so that users can continue to work with our code-based metadata generation feature alongside the RC.

Other changes include:

  • Self Tracking Entities templates are no longer in this CTP as they are included with Visual Studio 2010 RC
  • Code First now exposes cascading delete functionality implicitly through some conventions and explicitly via the WillCascadeOnDelete API

Going forward we have many new additions and changes planned for Code First including a revised navigation API and improved conventions that we intend to share in future CTPs as features are ready.

- Entity Framework Team

Comments

  • Anonymous
    February 18, 2010
    Thanks for the release I am really enjoying the Code First Entity Framework Stuff. Is the Entity Framework going to be released with Visual Studio 2010 in April? Thanks Jon Shern

  • Anonymous
    February 18, 2010
    Jon, Entity Framework 4 is included in .NET Framework 4 / Visual Studio 2010, so yes it is included in the RTM version of Visual Studio 2010. Please note, however that Code First is not included as a part of that release. Hope this helps!

  • Anonymous
    February 18, 2010
    Great! What about PEM? Indeed, with RC, we can install it. Matthieu

  • Anonymous
    February 18, 2010
    Sorry, we can't install it. Matthieu

  • Anonymous
    February 18, 2010
    Is any of the features of the Entity designer database generation power pack in this CTP? Or we have to wait a new release of the power pack for VS2010RC?

  • Anonymous
    February 18, 2010
    This Features at CTP 1/2/3 not will be released with .Net 4??? How can I use at production?

  • Anonymous
    February 18, 2010
    I can't find the download. Error: Sorry, no results found for: downloads details aspx FamilyID af18e652 9ea7 478b 8b41 8424b94e3f58 displayLang en

  • Anonymous
    February 18, 2010
    @Felipe Code First is still under active development and will have some breaking changes so there is no go-live licence at this time. You could however use the WriteEdmx function as a way to export out the EDMX file to remove any runtime/deployment dependency on Code First for now. [)amien

  • Anonymous
    February 19, 2010
    Install this over VS2010 RC and Self-Tracking Entities Template is gone?

  • Anonymous
    February 19, 2010
    @Agustín -- the database generation power pack already supports VS2010 RC: http://bit.ly/8akJIs -adi

  • Anonymous
    February 19, 2010
    @Mark H, VS2010 RC includes Self Tracking Entities, and so we no longer need to ship it as a part of this CTP release. Installing CTP3 over VS 2010 RC does not break Self Tracking Entities.

  • Anonymous
    March 02, 2010
    please help to me!!! Error 1 Running transformation: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Unable to locate file   at Microsoft.VisualStudio.TextTemplating.VSHost.TextTemplatingService.ResolvePath(String path)   at Microsoft.VisualStudio.TextTemplating.VSHost.TextTemplatingService.ResolvePath(String path)   --- End of inner exception stack trace ---   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)   at Microsoft.VisualStudio.TextTemplatingA9DB2432A51EA8D42A615FBEB2ECB4E5.GeneratedTextTransformation.DynamicHost.ResolvePath(String path)   at Microsoft.VisualStudio.TextTemplatingA9DB2432A51EA8D42A615FBEB2ECB4E5.GeneratedTextTransformation.MetadataLoader.TryCreateEdmItemCollection(String sourcePath, String[] referenceSchemas, EdmItemCollection& edmItemCollection)   at Microsoft.VisualStudio.TextTemplatingA9DB2432A51EA8D42A615FBEB2ECB4E5.GeneratedTextTransformation.MetadataLoader.CreateEdmItemCollection(String sourcePath, String[] referenceSchemas)   at Microsoft.VisualStudio.TextTemplatingA9DB2432A51EA8D42A615FBEB2ECB4E5.GeneratedTextTransformation.TransformText()   at Microsoft.VisualStudio.TextTemplating.TransformationRunner.RunTransformation(TemplateProcessingSession session, String source, ITextTemplatingEngineHost host, String& result) 1 1

  • Anonymous
    March 09, 2010
    Can you please explain the reason for renaming 'Code Only' to 'Code First'.  In presentations of some months you seemed keen to make a distinction:  Code First then meant that you wrote the POCO objects first and then generated the .edmx from the code (i.e. the inverse of Model first).  Code Only meant:  no .edmx file.  Now you have dropped the distinction does this mean that your (new) idea of Code First will have the ability to generate the .edmx or not?  I find that a useful idea because for some things it would be easier to edit the .edmx than to specify everything with attributes in the code.

  • Anonymous
    March 23, 2010
    this is great easy and helpful

  • Anonymous
    March 23, 2010
    this is great easy and helpful

  • Anonymous
    April 14, 2010
    I can't believe you guys spent the time to implement model-first development, but don't have true POCO support ready for the .NET 4 release.  This was the one feature serious developers were really waiting for.  It seems once again Microsoft's support for TDD is an afterthough.