Orcas Beta 2 Automation Planning

I am in the process of finalizing the C# automation matrix for Beta 2. One of the scenarios that I feel receives very little coverage today, and that I would like some help with, is the interaction of Visual Studio with other software or machine configurations.

Have there been any pain points that you have run into when attempting to use Visual Studio in the past or install it that we could have made better? How is your dev box configured? Do you run as an admin or normal user? What about on Vista? Have you ever needed to install VS on a domain controller? What about a server in a DMZ that is seeing an issue that is not reproducible in the dev environment?

Anyway... let me know your thoughts and I'll see what I can do in order to incorporate this into our testing somehow.

Are there things that you would like to hear about from the C# testing/automation perspective?

Comments

• Anonymous
  April 17, 2007
  probably not possible but I tried twice in XP to no avail was per usual editing code on a app that was running.  If testing the code could create another instance of the compiled code so that the developer could simultaneously tweak and test code that would probably be very helpful.

• Anonymous
  June 27, 2007
  I saw someone is already talking about Orcas Beta 2. Where can I find it?

• Anonymous
  July 16, 2007
  One of the things I'd like to see improved is the ability to register controls in the toolbox through the automation interface. Currently this is really flaky. It sometimes works - most of the times it doesn't resulting in some internal COM error in the bowels of VS.