This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am really liking WebWorkbench, however it's insistence of forcing my project to contain a WebWorkbench.mswwsettings file is proving a large annoyance for me. As soon as I delete it, it automatically reappears seconds later - what's more frustrating is it then gets automatically tracked by my source control (TFS). I can understand the need for the file if I was creating some specific project settings, but it even gets created when I'm using the defaults. Could it perhaps work as ReSharper does, where it creates the files it needs but does so outside of the solution? If I want to share the file then around the project team members, I could choose to add it into the project. |
|
|
Any thoughts on this? As such I am having to remove the tool, which is a shame as it's very useful. I just don't want unnecessary tool-specific settings forced into my source-controlled projects at all. |
|
|
We are not intending to change this at this time as we expect the settings file to be part of the project. Sorry to hear this is a blocker for you.
|
|
|
This is a blocker for me, too. I really don't need the tool to create an empty settings file for every web project I open in Visual Studio. There are only one or two projects I've tried using the tool for, and even then, the others working with those projects don't want the project muddied with a tool-specific settings file. It was a neat tool to try out, but if it causes me to step on the toes of those around me, it has to go. |
|
|
I have a problem with that too. It would be nice if the tool would be turned off by default and you have to enable it only for specific projects. Best regards |
|
|
Have you tried navigating to the file in Explorer and setting its Read-Only property to "True"? I would not have expected this to work, but it appears to have done the trick. |
|