My team currently uses Visual SourceSafe (VSS) 6.0 as the source control for our team project. Recently we decided the switch to the latest source control technologies such as Team Foundation Server.
SourceSafe has check-in/check-out functionality which works in this way: when I check-out a file, any other team member cannot edit the file until I check-in. Now I am playing with team foundation server, and I am looking for the similar functionality in TFS. But it looks like even if I check-out a file, other team member can still edit and check-in the file. So when I want to check-in my own file I have to resolve all conflicts as now server has different version than I have.
Can anyone tell me if is it possible in TFS to lock a file before editing, thus preventing other users to edit that file and avoiding all merge and resolving conflict issues?
I tried ‘Get latest version of item on check out’ option. But this does not work for local workspace. So if I enable this option, and do check-in, it completely removes changes in my local file that I am intended to check-in and replaces it with latest server copy.
Can anyone give me any suggestion?
Thank you.
This link might be helpful for this, I believe setting off "Multiple checkout" will do what you want.
Related
When I use .dll files in the ASP.net toolbox with the chosen item menu, a message displays like: "The following controls were successfully added to the toolbox but are not enabled in the active designer". I want to use this .dll (Aguage.dll file downloaded from internet & want to use in my project).
What can I do to solve this issue.
This .dll file basically contain a gauge like speed meter of car, clock etc
The following link appears to have the answer to your question (though is slightly different, it appears).
how to import a dll into a asp.net web application running on webserver
So hopefully you should find all the info you need there. However if you need more help do let me know :).
Edit: I have checked and the initial version of the file seems to have been created for .NET 2.0 rather than the version you are currently using. There may be a way to amend the DLL file but I would suggest this is problem.
Edit 2: Works fine on my system with latest version of VSEE 2015 so outdated file doesn't seem to be the issue. Suggest there is a likely a probably with user's setup. More info in comments.
http://www.codeproject.com/Articles/17559/A-fast-and-performing-gauge
I have uploaded a video to help:
https://www.youtube.com/watch?v=HWFIgFonZ3A
(in reply to the user who previously removed reference to this question, this is not a link only answer by any stretch of the imagination; furthermore, the answer holds information which is likely useful to other users and is part of a process of ongoing inquiry into the roots of the user's issues, which we are more than happy to look into as deeply as the concerned party is willing to furnish us with additional information)
Additional note: At the current time our best information has been forthcoming regarding the problem the user is experiencing. If the user wishes additional support, and assuming Visual Studio had been installed from scratch, we would be ok to remote on to the user's system if they wish us to do so
I am working on an ASP.NET web project in Visual Studio 2013 and it worked couple of hours before. But an hour ago I was tweaking something in the project and messed up the entire project. Is there anyway to restore to the version I had yesterday?
If you are using Version control, such as Mercurial, GIT, Subversion, TFS -- and you remembered to commit your work then YES, definitely.
If you're not using Version Control then you need to ask yourself why not? And don't turn off the computer today until you've corrected that oversight.
Also, you may have previous versions/restore points saved for you in Windows. In windows explorer, right click on the folder where your work is being saved and select properties. They may be a 'previous versions' tab, and inside there you may be able to revert to an earlier version. If so: lucky lucky you.
Also, if your work is being shared using a service like DropBox, you will be able to find earlier versions of your solution or project files.
There is one other technique, and I... I hesitate to mention this. What you need is a DeLorean car from the eighties, and enough plutonium to generate 1 point 21 GigaWatts. You also need.... forget it, no, Version Control is your best bet. Or Ctrl+Z.
Holding ctrl+z for a few minutes, and using version control are the only two ways I am aware of doing that..
In case you're like me and trying to recover from what you just did, if you saved your work to OneDrive, you can find the previous version of your work by logging into OneDrive through a web browser.
Newer versions of Visual Studio should have a "Timeline" feature that shows up in your left bar. It has probably been saving past versions of your files. But I would agree with others that using Version Control (like just committing your changes to a Github repo) is probably a smart idea!
I recently upgraded my computer which I use for a lot of asp.net projects among other things.
I moved all my projects over from the old pc to the new one, but I no longer have the publish settings in the solutions (well I assume they are all the same as the current one I am working on).
I did find some import/export available in studio (express) but nothing pertaining to publish, which I assumed to be a solution (or even project) level setting.
It would be most helpful to get my original publish settings, any help would be appreciated.
Regards
Marts
I found the solution quite by accident.
Since I needed to publish something, I started creating a "first" publication profile, and at the and of that process, my original publications appeared in the list.
There must be an issue where the special message "Create Publish Setting" in the profiles list somehow overrides the existing list for new installs of VS.
Martin
Is it possible to exclude a folder in a web project from being published? We've got some documentation and scripts that included in a particular project folder, and are added to the project, but when I do a VS publish, I don't want them to go up to the production server.
I know they shouldn't be in the project, but I thought I'd find a workaround before I try to convince the owner to modify the way he's doing things.
Old question, but I found if I mark the folder as hidden in Windows Explorer, it doesn't show/publish in your solution.
This is good for example to stop original photoshop images being included in uploads which aren't used and are big. Anything more complex though you'll probably want to write your own publish tool.
This doesn't answer your question, exactly, but my feeling is that unless you are a single developer publishing to a server, you would be better off doing builds on a dedicated workstation or server using MSBuild (or some other building and deploying solution) directly (and thereby would be able to very granularly control what goes up to production). MSBuild can not only build, but using some extensions (including open source types), it can also deploy. Microsoft has a product called MSDeploy in beta, and that might be an even better choice, but having no experience with it, I cannot say for certain.
In our situation, we have a virtual workstation as a build box, and all we have to do is double click on the batch file that starts up an MSBuild project. It labels all code using VSS, gets latest version, builds the solution, and then deploys it to both servers. We deploy exactly what we want to deploy and nothing more. We're quite happy with it.
The only downside, if it could be considered a downside, is that at least one of us had to learn how to use MSBuild. VS itself uses MSBuild.
For the files you don't want to go, loop at the properties and set the 'Copy to Output Directory' to 'Do not copy'
This option is not available for directories, however.
Can you not exclude them from the project through visual studio to stop them being published. They will the still exist in the filesystem
The only way that you can do this to my knowledge would be to exclude it from the project, do the publish, then re-include it in the project. That can be an issue.
There are probably much better ways to solve this problem but when we publish a build for our dev servers, we'll run a batch file when the build is complete to remove the un-needed folders and web.configs (so we don't override the ones that are already deployed).
According to http://www.mahingupta.com/mahingupta/blog/post/2009/12/04/AspNet-website-Exclude-folder-from-compilation.aspx you can just give the folder the "hidden" attribute in windows explorer and it won't publish. I tested this and it works for me.
Seems like a straightforward solution for quick and dirty purposes, but I don't think it will carry through our version control (mercurial).
Select all the files that should not be published.
Go to Properties
Set
Build Action -> None
Have to repeat the process for each sub-directory.
Right now I'm working with an ASP.NET website that automatically generates images and stores them in a temporary folder. When working on my local system these go going into a temporary folder that gets picked up by Visual Source Safe which then wants to check them in. As such, I am wondering if there is a way to just exclude that particular folder from source control?
I've done a bit of reading and found that there are ways to do this for individual files, but I haven't found anything yet about an entire folder.
I think you've found one of the main reasons MS went back to projects in VS2008 and in MVC.
It's been a long time since I've used VSS (mainly because it's really out of date now), but most source providers let you exclude files and folders as a setting of the provider, rather than the project under control.
If you can switch to a Web Project rather than a WebSite then do so, otherwise I'd look at updating your source control provider, as this sort of exclusion is easy with Vault, CSV, SVN, Git, VSTS and so on (to name but a few).
Are you using ASP.NET Website or ASP.NET Web Project? The difference is significant enough to solve or promote this problem.
Websites, love to scan the file system and auto checkin.
Projects, checkin only what you tell them to.
Also Visual Source Safe is pretty out dated, most recent source control systems allow you to do what you are asking. SVN and TFS 2008 SP1 do from my experience.
You can also try to right click and pick "Exclude" on the folder, but in the case of a Website I believe this renames the folder.
I'm not sure if this is an option for you, but if you exclude your temporary folder from VSS (delete the folder inside VSS using the VSS UI), the files that go into it should not get "picked up" again.
If you perform operations on a parent project of the temporary folder, you may try cloaking the folder.
http://msdn.microsoft.com/en-us/library/x2398bf5(VS.80).aspx
I would suggest emptying/deleting your folder from your website. Have your website on startup create/verify the folder, and on shutdown to clean it up and remove anything in it. This can be DEBUG code only (wrap in #if DEBUG) if so needed. Also add a build script to your project that does this every time it is built also.
Could you just make your application write to a temporary folder that is outside of your website?
e.g. in C:\tempfiles
VSS shouldn't be able to pick it up then.