Victoria .NET UG VSTS Topics Anyone?

I’m going to be in beautiful Victoria (BC) to present at the .NET UG on October 4th to talk on Team System on behalf of INETA.  Of course, I could present on something pre-canned but that would be boring… If you are planning to attend, why don’t you send me your feedback on what topics you would like to discuss and we can customize the session to exactly what you would like to see.  I can drill as deep as you want to go on any topic…so go nuts.

Post back to this blog entry with ideas and suggestions – go ahead – get specific – don’t be shy… Hope to see you there!

5 Comments

  • I'd like to see something like, "A day in the life of VSTS users." Show a class as it goes from design, through coding (with Source Control), then testing.



    Alternately, something on MSF/Agile, as I haven't found much there yet.



    Or, whatever I can get from you for a new article ;)

  • Deployment questions:

    I've tried to install VSTS Beta 2 but the TFS install dies 'cause I don't have SharePoint. What are all the MS products required to get the thing installed?



    Suppose I already have spent a lot of time, money and effort building a custom formal process around my tools for version control, document repository, bug database, unit testing, profiling tools, etc. Why should I switch to Team System?



    And what is it REALLY going to cost my company of, say, 50 people? How much hardware? Software Licenses? And maintenance of all the above.



    Is it easy to keep my <insert tool here> and use the rest of the TS (think NUnit, CVS, Bugzilla)?



    Is it worth getting the whole system if the architect, developer, and unit tester is the same person?



    Technical questions:

    I can't for the life of me find how to turn on coverage. Where do I do that?



    How easy is it to write custom add-ins to force VSTS into the process my company uses?



    I wouldn't mind seeing an end-to-end demo of the developer tools: take a design, write the code, test the code, perf the code.



    That's all I can think off the top of my head :)



    I'm looking forward to your talk. If you're preparing this early, it should be great. I usually prepare the night before :) BTW, can you a link to the victoria user group home page on the left there.

  • It would be interesting to see how the whole VSTS methodology could be scaled from teams of 5 to 50 to 500 devs.

  • I've been toying with MSBuild lately. What kind of MSBuild support does VSTS have? Can I use the features from the IDE in my daily build script? If so, which ones and how is it done?

  • Focus on workflow more than technical details: if the workflow is good enough we'll learn to live with whatever the details are. If you're going to demo tests, we'd find it much more valuable to see it from a test-driven perspective than test-after. How seemfully do other revision control systems plug in? How are templates and code-completion plugins developed?

Comments have been disabled for this content.