I have a question for those of you that have updated your Telerik WinForms controls to the recently released SP1 version. Did you have manually set your projects referencing Telerik WinForms controls to be writable before you could do the update? I did and have had to do so for each version update.
My question to Telerik is this; why is this not accounted for in their Project Update Utility? To the best of my knowledge Visual Studio typically sets all project files to be read-only so that changes are less likely to be made outside of Visual Studio, especially when source control is used. Visual Studio has no trouble writing back to project files every time you save your changes. This leads me to believe that it would also be possible for the Project Update Utility to do so, as well.
Granted, Microsoft may "cheat" when it comes to saving changes to read-only files, as they do in other instances of needing to "fudge" permissions, but there should be a way for a third-party provider to do so as well. Any light that can be shed on this would be greatly appreciated!
My question to Telerik is this; why is this not accounted for in their Project Update Utility? To the best of my knowledge Visual Studio typically sets all project files to be read-only so that changes are less likely to be made outside of Visual Studio, especially when source control is used. Visual Studio has no trouble writing back to project files every time you save your changes. This leads me to believe that it would also be possible for the Project Update Utility to do so, as well.
Granted, Microsoft may "cheat" when it comes to saving changes to read-only files, as they do in other instances of needing to "fudge" permissions, but there should be a way for a third-party provider to do so as well. Any light that can be shed on this would be greatly appreciated!