Web Development
by dropysh05
I wouldn't be surprised by a security hole in an MS Product, but this is definitly NOT one of them. Security is very important and articals like this cause people, especially upper management, to believe this is a valid solution. Security in this aspect should really be focused around securing the networks where the developers work.
I see that Mark Peterson is a apparently is a very important person, but he doesn't seem to have a clue what he is talking about. If he has hackers getting onto his network and logging in to his machine he better have someone get onto the security holes on that first.
And as the last guy said never, NEVER EVER work right in production.
.john
by i_am_whopper
The article was trying to point out an often overlooked fact of working with Visual Interdev in Master Mode. I have yet to talk with anyone who realized that Master Mode will automatically propogate to the Master Web Server any change made to a file, regardless of how the change was made. Most people read the Microsoft documentation and assume that the updates of the Master Web Server are done through the Visual Interdev IDE.
Because it is not Visual Interdev that is responsible for migrating content, I am curious as to what modifications are made to the development machine's configuration to put it into Master Mode. Is it a pull or push subscription to the Master Web Server? What process/service is doing the pushing and the pullingof the content? I have looked all over MSDN and have not found any documentation on it. Has anybody else come across something?
by dropysh05
In master mode, if you open a file in an external editor and save your changes, those changes will not be copied to the master web until you close the project, or use the "Release Working Copy/Check In" commands, which explicitly update the master web.
Visual InterDev relies on being notified by the operating system when a file has changed outside Visual Studio in order to copy the changed file to the master web (or cause a reparse of the file in the local working web).
And I didn't miss his point. I only thought the title indicates somthing wrong with the product.
My point is you should never work directly on a production web server. If you need to work with other developers on a project you should setup a location on another server. If a company cannot afford a development server they should close the doors and go home.
This discussion is closed to new replies.
Sort by Trending