Safe Visual Source - Delete Files from Web Projects
I'll try to make it as direct as possible.
- Our team currently has a VSS database that stores our projects.
- Developers grab the code and host on their local machine and develop locally.
- The designated developer grabs the latest version and pushes to the development server.
The problem is that when a file is removed from the project (by deleting it in VS2008), then the next time another developer checks out (and not the one who deleted it), he prompts them to check those deleted files, because they are still there is a copy on their local machine.
Is there a way to get around this? So that VSS instructs the client machine to delete these files instead of asking them back? What's the preferred approach for this?
Edit note (s):
- I agree that SVN is better than VSS
- I agree that a web application design is better than a website design.
- Problem . The same thing happens with files that are removed from class libraries.
source to share
You are on the same path to stop using website projects. Website designs force visual studio to automatically add whatever it finds along the way to the project.
Instead, go to web application projects that don't have this behavior issue.
Website designs are good for one person development.
UPDATE:
VB stores have had similar issues since days gone by, as everything they installed affected the build process. You can take a page from your book and have a clean build machine. Before deploying, you will delete all project folders and then get the latest version. This way, you will be sure that the only thing deployed is what you have in version control.
By the way, this is also how the TFS build server works. It deletes the workspace, then creates a new one and loads the required project files.
Alternatively, you can use something like Cruise Control to handle assemblies.
source to share
The best solution would be to move to a better version control system like SVN.
At my job, we recently acquired a project from an outsourcing company that used VSS as version control. We were able to import the entire changelog into SVN from VSS and run quickly and quickly from SVN.
And with SVN, you can set up ignores for files and folders, so files in your web projects don't end up in SVN, and ignore attributes are output to every developer machine.
I believe we used VSSMigrate to migrate to SVN http://www.poweradmin.com/sourcecode/vssmigrate.aspx
source to share
VSS is a terrible version control system and you should switch to SVN, but that has nothing to do with the heart of the problem. The project file contains links to which files are actually part of the project. If the visual studio project is not checked out along with the changes in it, however, no other developer can be completely updated, hence the file deletion requests when they grab the latest VSS. From there, you have several options ...
-
Make the vbproj part in the repository. Any project level changes will be part of the commit and other developers can be notified. The problem here is that it will also be on the dev server. Ideally, you can use pretty much the same process for deploying to dev as you would for deploying as a release. This leads to a different path ...
-
SVN gives you hooks for almost all major events, where hooks are literally a properly named / exe batch file. For your purposes, you can use the post-commit hook to push relevant files, say via ftp, to the server on every commit. The file issues have been resolved and, more importantly, closer to the concept of continuous integration.
source to share