Hello!
Wouldn't it be a good idea to add a switch for the sqlmetal.exe program for making it to implement the System.ComponentModel.INotifyPropertyChanged in all the relevant classes
Best regards,
Henrik Dahl
Support for the System.ComponentModel.INotifyPropertyChanged interface
Hot Topic
- IDTExtensibility2.OnConnection not called on first load of Word after installation
- Can't Uninstall VS 2003...
- Create Pivot Table in VSTO2
- Display HTML Snippet?
- enable/disable - wizard navigation buttons
- Generate Proxy class with MSMQ
- problem deploying a new project type
- Code Optimization
- Getting RID of Just-In-Time debugger
- MSMQ error opening queue
Visual Studio
- how to bind items in a group?
- Path Rotation
- selecting the style dynamically
- Problem building Managed C++ project with Msbuild that has multiple assembly references
- SessionState and IE Privacy settings problem
- xbap and database
- Display vertical rows in a ListView
- Does VSS 2005 have Netsetup?
- Indigo January CTP: Creating interface-compliant proxy on top of interface with overloaded methods
- VS 2005 he&&
Support for the System.ComponentModel.INotifyPropertyChanged interface
MB98
Golm
laforced
We are considering ways to make DLINQ and SqlMetal more extensible. The reason we did not go ahead an simply use the INotifyPropertyChanged interface was that we needed an INotifyPropertyChanging event. (One that fires before the change and not after.) We may still rationalize the two, change the one we are using, etc, somewhere down the road to release.
Tian
Matt Warren!
Yes, but couldn't we say that the object is observed from two angles, from the DLINQ infrastructural point of view and from the system developer's point of view. From the infrastructural point of view the INotifyPropertyChanging event matters, which is needed due to all kinds of ordinary infrastructural considerations. From the system developers point of view the INotifyPropertyChanged event is needed due to the common reasons.
Therefore I still think you should just provide the switch for having SqlMetal to generate code for raising this as well AFTER the property has been changed. It could obviously be an idea with a more rich template approach, i.e. some XSLT transformation of the XML document (or is it actually this you do internally ).
Best regards,
Henrik Dahl