Roadmap for SourceSafe and Beyond

RE: Roadmap for SourceSafe and Beyond

Don McNamara — Thu, 31 Jul 2003 20:21:00 GMT

Hrmpf. Adding support for unicode and web services is certainly needed. Unfortunately, the team I'm working on was hoping for something a little more powerful in the next version of SS -- more feature parity with CVS. This just confirms my belief that our project has out grown SS and now is a good time to move on.

RE: Roadmap for SourceSafe and Beyond

Ryan Gregg — Thu, 31 Jul 2003 23:17:00 GMT

I'm disappointed to see nothing about better support for using VSS in diverse community environments via the Internet. Nothing is worse than trying to use VSS via a VPN link back to a company you're working for. How about a server-based version of VSS (yes, I know all about SourceOffSite and other similar products) that would support Internet clients!

RE: Roadmap for SourceSafe and Beyond

Sam Gentile — Thu, 31 Jul 2003 23:27:00 GMT

I am extremely happy that VSS will finally see some new development. That being said, the great majority of .NET developers do not work on Web Services and thus both new features listed are not very useful to me. I echo what the two previous persons said as well as wondering when Microsoft will provide a full CMS t(along the lines of Rational's ClearCase or Perforce) to overcome the many issues that we have in using VSS on group projects of any appreciable size. I appreciate your blog and work and if you would like any input, I would be glad to provide some.

RE: Roadmap for SourceSafe and Beyond

Phil — Fri, 01 Aug 2003 02:23:00 GMT

Good to know Korby. As my emails have pointed out, performance over slow network connections is my number one issue with VSS. These issues are addressed in the SourceGear product, so I would think that the VSS team would rank improving performance as the first item to fix in the next release.

RE: Roadmap for SourceSafe and Beyond

Yves Reynhout — Fri, 01 Aug 2003 12:57:00 GMT

Really, if you where to do a complete rewrite of VSS for use in a peer-to-peer, server-based and/or web-based environment, using WSE for all security aspects and implement a facade using Webservices, and maybe store everything in a SQL database... but wait, why bother ... Go get SourceVault.

RE: Roadmap for SourceSafe and Beyond

Nino Benvenuti — Mon, 04 Aug 2003 04:39:00 GMT

Good to know there is movement on this product, Korby (and nice to hear from someone on that team). As a VSS user for many years, I agree that unicode and web services support is needed; however, I think that many users would suggest tackling 'higher priority' items. Here are things that I would like to see: Better network (i.e. Internet / VPN) performance; current performance here borders on dismal. I would also like to see this product as a true server product (maybe using SQL Server on the back end) with Web Services and Remoting interfaces. I would also like to thank you for blogging, giving us some insight into this product. -Nino

RE: Roadmap for SourceSafe and Beyond

Mladen Mihajlovic — Mon, 04 Aug 2003 18:44:00 GMT

Also, I know this sounds stupid, but I think it really needs a "visual" upgrade. Those blue folders and old style icons are really starting to look crappy ;)

RE: Roadmap for SourceSafe and Beyond

Korby — Fri, 08 Aug 2003 03:43:00 GMT

One of the most frustrating aspects of my job is that I can't share all the cool things we're working on inside the fortress walls with my friends and family on the ouside. No, we're not the CIA and it's not a life or death matter. But imagine a world in which every Microsoft employee routinely spouted off about some feature or another without half of them ever getting shipped. That would be bad! Lately, Eric Rudder has been stressing the importance of transparency in our product planning so that developers like yourselves can have more information than you've had in the past and hopefully, create your own development strategies more effectively. I'm certain that the Roadmap to Whidbey is Eric's doing. Internally, I have been a vocal supporter of this Roadmap and the cultural shift it represents. Nonetheless, I still can't tell you everything about the next version of VSS. What I can say is that VSS is not a dead end product by any means and that the Whidbey Roadmap is not all-inclusive, especially in the source control space. The VSS team is firing on all cylinders and is anxious to deliver a great source control experience to our valued customers. Until we do, keep those comments coming! We're always listening, especially to comments like, "do a complete rewrite of VSS for use in a peer-to-peer, server-based and/or web-based environment, using WSE for all security aspects and implement a facade using Webservices, and maybe store everything in a SQL database.":-) btw, Yves, is your real name James? Using WSE-security is a wonderful idea... for any Web app.

RE: Roadmap for SourceSafe and Beyond

Martin Spedding — Fri, 15 Aug 2003 10:01:00 GMT

Why not intergrate the Gotdotnet workspaces technology with Visual Source safe ? Also after all the discussion about version contol management and stored procedures why not add a simple way of doing this out of the box. By the way I have learnt a lot through reading you blog.

RE: Roadmap for SourceSafe and Beyond

chris antos — Thu, 25 Sep 2003 19:54:00 GMT

Why not put the long-deserved bullet in SourceSafe's head and share Source Depot with the world?

RE: Roadmap for SourceSafe and Beyond

Mav — Thu, 13 Nov 2003 16:11:00 GMT

When will all of this explode onto the shelves or maybe into Beta testing hands. I am very keen to see this and beta it. When .. when .... when ?

Whidbey VSS Secrets?

Ken Brubaker — Tue, 17 Feb 2004 02:42:00 GMT

Whidbey VSS Secrets?

re: Roadmap for SourceSafe and Beyond

tomas HOISE — Mon, 12 Jul 2004 11:59:00 GMT

for business relationship.

re: Roadmap for SourceSafe and Beyond

replicarolex — Sat, 16 Sep 2006 18:46:48 GMT

[URL=http://http://replicarolexwatch.ir.pl]replica-rolex-watch[/URL]<a href="http://http://replicarolexwatch.ir.pl">replica rolex watch</a>