Overused? Just because a Web Solutions Architect[^]opens a VS solution to engineer an enterprise-level solution after reading a solution to their leading query on the Interweb ... oh. Nevermind. :laugh:

In our new-project writeups, phrases like this are popping up more often: "the customer shopping experience". It's an experience now, really? I thought it was just surfing, maybe with a prize at the end in the form of a bill from Visa. So that, and the new Model X will improve our "driving experience", and I'm sure there are others, but this one forces them to admit their inferiority. I was surfing enjoying a browser experience, looking for vids on .Net's take on MVC. One vid was pretty good, well structured, but then the presenter used the phrase "the user's textbox experience" as he clicked on the field. :wtf: No link2prove atm. May hunt that up later if I remember. :)

Thanks for all the leads, and details, and I'll definitely check these out. I think the request for better software was to avoid conflict by blaming software instead of devs. I interpreted it as "Find a system that doesn't allow" us to ignore/forget updates (and other stuff, but I'll keep the rant to a minimum). It seems like your system makes what we do irrelevant until items are checked in and shifted to the build server, and automates a lot of things that have caused us problems by doing them (or not doing, heh) manually. That sounds much easier, and less restrictive. :thumbsup:

I'm on a team of three, using VS2008 Pro/VB.Net on our main project, SQL 2000, and Sourcesafe from the same era. About a year ago there was a thread here to see who was moving to Team System, and for what reasons. My questions are: Short version: dev to dev, what's your opinion of TS now? Long version: for those of you who have gone over to TS from Pro (or other single-user version), what pros/cons really jump out at you? Do you notice a large performance gain/loss when working in a project? Is it more/less buggy in general? Is there anything you miss from Pro that isn't in TS? With integrated builds, is everyone required to work on the central dev server, or a version stored on your local computer? Would you consider TS worthwhile for such a small team? Do you prefer working with the database through TS, or through the database's own UI? <scenario rant> Our team doesn't keep each other too informed. Because there are so few of us, and no one who "knows code" to really call us on it, things are quite lax. There are no scheduled builds, and the dev server hangs whenever one starts - sometimes a dozen times an hour. Project changes are rarely reloaded until the GUI restarts, so new files are excluded from the project continuously for their first few days. Working on a local copy reduces the lag, but checking in a file does not automatically move the new version to the dev server, so there are a lot of lost/overwritten edits. These are all seen as software shortcomings and not flaws with personal habits, so I've been asked to find a VS-compatible system that will "do it right". </scenario rant> If TS is overkill or just not suitable for this scenario, what alternatives are you using? I'm in the research phase. Thoughts, opinions, and warnings are all welcome.