I got the private 4.0.1 build so I can finally see the VS 2005 client. Although I just created a test project and am using a test repository as I wasted hours last night un&^%ing my solution of 10 projects that I tried converting...I have the following feedback items.
1) It is imperative your VS 2005 client provide us the same configurability as the legacy client. Where do we configure options such as checkout on edit, check in ALL on closing the solution? I just closed my solution and was shocked not to get prompted to check-in everything, which is what we all do to ensure we don't leave things checked out when done working.
2) When I checked in my solution, I had to reload the project. This is not going to float as we have large solutions, I have a solution with 130 class libraries in it, you can imagine I don't want to go reloading that solution just because of a check-in!
3) I like silent checkout dialogs, I realize I can set the option to only show the dialog when SHIFT is pressed, but I didn't try that
4) When checking in the bottom area to associate a bug tracking number is disabled, not sure how to work that area.
Based on my initial review, I would prefer the legacy (VS 2003) client integration due to the options afforded to the developer, I'm not sure why I would give that up to move to VS 2005 integration. I honestly feel like I'm losing functionality moving to VSIP integration. I would have imagined you would have met or exceeded the current feature set of SCC integration, i.e. end-user preferences, but I'm not finding that, if it's available somewhere.
My $.02
I have not tested to see if the WinXP install issue is resolved.
VS 2005 Client
Moderator: SourceGear
VS 2005 Client
Last edited by neal007 on Thu Jun 07, 2007 1:43 pm, edited 1 time in total.
1. You are correct in pointing out that many of the configuration options which applied in the older MSSCCI client are missing in in the new Visual Studio 2005 plugin. That's because these options were owned and controled by Visual Studio, which would trigger the source control events. Since we the Visual Studio 2005 client is now separate, those options would have to be implemented by us.
2. Wow, that's a lot of projects in one solution. I've also been annoyed by the reloading on a checkin, but not nearly to that extent. We'll investigate to see if we can find the cause of the reloading.
3. In the Visual Studio 2005 client, all automatic check outs are done silently. This is to avoid the situation where a refactor operation modifies dozens of files, which must all be prompted individually.
4. That area will be enabled if FogBUGZ is set for the bug tracking integration for the repository. Since you're using a test repository, that's probably not the case.
Thanks for you feedback. We hope that you'll keep checking in with the VSIP client as we add features, and attempt to meet and exceed your expectations.
2. Wow, that's a lot of projects in one solution. I've also been annoyed by the reloading on a checkin, but not nearly to that extent. We'll investigate to see if we can find the cause of the reloading.
3. In the Visual Studio 2005 client, all automatic check outs are done silently. This is to avoid the situation where a refactor operation modifies dozens of files, which must all be prompted individually.
4. That area will be enabled if FogBUGZ is set for the bug tracking integration for the repository. Since you're using a test repository, that's probably not the case.
Thanks for you feedback. We hope that you'll keep checking in with the VSIP client as we add features, and attempt to meet and exceed your expectations.
Yes, ALL repositories have the FogBugz integration. I have the drop down set to FogBugz and the URL set to:
http://myvaultdomain/VaultService/Vault ... ersion=^R2
I don't know what FogBugz Trial ID is so it's blank, I have a licensed copy of FogBugz.
http://myvaultdomain/VaultService/Vault ... ersion=^R2
I don't know what FogBugz Trial ID is so it's blank, I have a licensed copy of FogBugz.
Correction - in Vault I put in http://myfogbugzserver/ (no sub-directory is required for my setup). Still not seeing FogBugz fields enabled when checking in.
Also, your SGV 4 docs say:
Also, your SGV 4 docs say:
Are you saying my devs that are NOT admins cannot use the FB integration?To enable bug tracking, you must have Vault admin privileges and access to the Vault Admin Web Client.
We've cleaned up the documentation around configuring FogBUGZ integration, as it's very confusing, and has been for a while. To specifically answer, no you don't need to be an admin to use FogBUGZ integration, only to configure it.
The reason you had to restart is that the client only asks for the current bug tracking settings on startup. You needed to restart to ask the server what the settings are.
The reason you had to restart is that the client only asks for the current bug tracking settings on startup. You needed to restart to ask the server what the settings are.