-
-
After asking fellow MVPs to help us drive visibility to the new Team System User Group (Virtual Edition), we ran across some hosting issues. Last night we had a router issue and this morning we've had a cable cut. The provider has an 8-hour response time so hopefully we'll be back soon. But in the mean time, http://www.tsug-ve.com is down! Please be patient and check-back. We hope to see many of you at our inaugural meeting tomorrow!
The TSUG website has instructions and I will generally send our an invite before the meeting. In case you're not able to sign-up at the site before then, here is what you need to do to participate:
- Make sure you have SecondLife and LiveMeeting installed and configured.
- The meeting is
Thursday, Sept 18th [Update: the third Thursday of each month] at 6PM 5PM (Pacific time = GMT-08:00). [Update: There is an additional meeting on the third Saturday of each month at 9AM Pacific time, catering to European and Middle-Eastern time zones.] - Sign into both LiveMeeting and SecondLife a little early - we will try to start on time and you may want to socialize with fellow VSTS enthusiasts. If you haven't played with SecondLife, plan to spend a few minutes going through the tutorial before you get started.
- Be prepared to switch back-and-forth (Alt-Tab) between SL and LM. We will do demos in LiveMeeting and many slides and interaction in SecondLife.
Important links:
We hope to "see" you there!
-
-
Chewing Glas (aka Paul Hacker) and Daven Finesmith (aka Dave McKinstry) are proud to announce a new users group forming in your area: the Team System User Group (Virtual Edition)!!!! In addition to the few user groups focused on Visual Studio Team System in major cities, now all Visual Studio Team System enthusiasts and users can join together to share stories and learn. Like most user groups, we will meet on a monthly basis, socialize a little, and have presentations. We plan to have demo-rich presentations and support an interactive format allowing attendees to participate and ask questions.
Unlike the ‘classic’ user group, you will be able to participate regardless of your location! You no longer have to live in one of the handful of cities world-wide to join and participate in a Team Systems community! In addition, we can now pull from a broader pool of excellent presenters from around the globe!
Our initial meetings will all be in English and are targeting an Americas-friendly time zone. But other times and places are possible. If you are interested, visit our web site: http://www.tsug-ve.com/. Sign-up and we’ll contact you with additional meeting information. It is free to join and none of the underlying technologies require fees beyond what you already pay for your computer and network access! We will not use your contact info for anything other than user group communications (approximately once per month). Our first meeting is September 18th at 6PM (Pacific Time / SLT). We hope to see you there!!
-
-
Awhile ago I was working with a client and received an error message "UTA052: MyNamespace.MyTest is not a test class" after converting a unit test project created in Visual Studio 2008 to Visual Studio 2005 Team Edition. (Actually it was a VS 2005 nUnit/BizUnit test project converted to VS 2008 MSTest and then to VS 2005 MSTest.) The path I chose wasn't necessarily supported but it was necessary. The nearest help I could find was from MSDN Forums: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3820523&SiteID=1&mode=1. Luckily I figured out the cause of the problem and a solution. If you have run into this message and said to yourself "but it IS a test class," read on...
The scenario that led to my this problem was the conversion of a VS 2005 nUnit project to VS 2008. As expected, when I opened the VS 2005 project with VS 2008, Visual Studio successfully converted the project to Visual Studio 2008 format. I then went through the required search-and-replace and reference changes to modify the nUnit tests to be Microsoft-format tests. This was the easy part.
Next, I had to convert the project back into Visual Studio 2005 format. Why? The original conversion to 2008 was a convenience that I knew I'd have to undo... The test project was in support of BizTalk 2006 R2, which is developed in VS 2005, not 2008. I wanted to maintain the test project in the same tools as the test target.
In many cases, you can revert a VS 2008 .NET 2.0 project to VS 2005 by simply changing a few characters in the .SLN, .VBPROJ and/or .CSPROJ files. In the following snippet, changing the "10.00" to "9.0" may result in converting the solution back to Visual Studio 2005. A similar exercise may be necessary for the project files but I'll leave the specifics to you.
After bringing the solutions and project back to Visual Studio 2005, I did some minor cleanup and recreated the VSMDI and TestRunConfig files. The solution compiled without issue but when I tried to run the tests I received the aforementioned message: "Error xxx UTA052: MyNamespace.MyTest is not a test class". Of course the source code looked fine. So after all that, what is the punchline? I had the wrong reference. I was referencing the 9.0 version of Microsoft.VisualStudio.QualityTools.UnitTestFramework. Since my system had both Visual Studio 2005 and 2008 installed and the 9.0 DLL is compatible with .NET 2.0, I didn't have any issues with compilation. But the 2005 version of MSTest did no recognize the 8.0 version of the testing tools, hence the error.
Although this may be a niche problem, hopefully this blog posting will help someone else trying to perform similar unit test surgery find the solution faster.