I've found a bug with the current method of iterating through the project items for a WPF project, be it c# or vb. It is a well known bug with automation in visual studio for these project types. Ahhh Microsoft...
Basically when iterating only the top most file "Application.xaml" will be checked as this appears in the project items but "Application.xaml.vb" could have changed without the top file changing and wouldn't trigger the update.
Any ideas on a fix? I've included code in my own version to check for this instance, but its a bit of a hack.
Basically when iterating only the top most file "Application.xaml" will be checked as this appears in the project items but "Application.xaml.vb" could have changed without the top file changing and wouldn't trigger the update.
Any ideas on a fix? I've included code in my own version to check for this instance, but its a bit of a hack.