<< Great troubleshooting resource for Microsoft Dynamics AX 2009 installations. | The InnerException message was 'Type 'System. DelegateSerializationHolder +DelegateEntry' with data contract name 'DelegateSerializationHolder. DelegateEntry :http://schemas. datacontract.org /2004/07/ System' is not expected. >>

Bug with Visual Studio 2010 and DBML designer – Changes not causing regeneration of DataContext code.

By dsandor at July 17, 2009 00:16
Filed Under:

Vote for this bug if you encounter this problem. Basically in 2010, if you regen the DBML file outside of VS the underlying DataContext code does not get regenerated. This is bad because changes outside of VS 2010 to your DBML will not get ‘picked up’ when you rebuild.

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=474117

bffa88ee-8085-45e7-8d2b-e3811b7ecc2e|1|5.0

Tags: dbml, visual studio 2010, bug

Comments (0) E-mail Kick it! DZone it! del.icio.us Permalink Post RSS

Visual Studio 2010: Debug annotations (sticky notes) for debugging / Quick WatchTwo really cool features in Visual Studio 2010 for C# developers. 1) Sticky Notes Quick Watc...Silverlight Hover Button – XAML Style implementation with code that is dynamic and skinnable.So I needed to create a hover button. The idea is that when the mouse rolls over the button th...WPF Databinding visibility of a control to your ViewModel / DataContext boolean value.In many cases you will need to set the visibility of a control based on a value of a property of you...

Comments are closed

David Sandor

Build Succeeded: Software Architecture and .NET Develoment

Bug with Visual Studio 2010 and DBML designer – Changes not causing regeneration of DataContext code.

Month List

Page List

David Sandor

Build Succeeded: Software Architecture and .NET Develoment

Bug with Visual Studio 2010 and DBML designer – Changes not causing regeneration of DataContext code.

Tag cloud

Month List

Page List

Blogroll