October 2005 - Posts
Here is another problem you may run into when running web tests in Visual Studio 2005:
With the upcoming release of Microsoft Visual Studio 2005, Microsoft will be making some exciting new changes to Visual Studio and MSDN Subscriptions products and corresponding pricing and licensing.
Join Jerry Flynn, Microsoft Developer Solution Specialist, as he hosts a Microsoft webcast presentation on the Visual Studio Team System and the transition plan to the new products on Thursday, October 20, 2005 9:00 AM (CST)
I had a conversation yesterday with John Cunningham and he mentioned a problem that I have not seen at all but I thought I'd share it along with the solution:
Problem: You may get an error the first time you try to run the Profiler on Windows 2000 if you have not rebooted your computer since you ran the installation of Visual Studio.
Solution: This is due to some differences on the OS APIs. The solution is to reboot your computer.
Cross Posting (until I start getting more traffic on my other blog :-)... http://teamsystemrocks.com/blogs/omarv/archive/2005/10/13/413.aspx
I am catching up on all the blog and forums posts that I had not been able to read since the week before PDC and it looks like there are several people out there having problems building Web Applications. It turns out that apparently you just can't say 'Any CPU' in your build options for Web Apps. You have to select a platform that is supported by ASP.Net or 'Mixed Platforms' in order to your webb apps to be built successfully.
Cross Post: http://teamsystemrocks.com/blogs/omarv/archive/2005/10/09/403.aspx
Dave had a problem yesterday while teaching a VSTS class in Illinois, himself and some of the students were getting a message box saying something like 'Object is in an invalid state' and the tests just wouldn't run. So Dave called me to see if I had seen the problem before and yes, I had seen it but disappeared on me after a VS restart. Well, I am in Redmond this week and Rob Caron pointed me in the right direction; after exchanging a few emails, about an hour later I received a response from the Test Tools team, namely, Eric Jarvi (Thanks Eric, for the quick response!) ...
Long story short: This is a known bug in RC and has been fixed in a later build.
The Solution: Close Visual Studio and delete your <solution>.suo file. This file does not contain any code, only user options and other information about the state of the solution in Visual Studio; and it is a per-user file.
Reminder: I am moving my blog to http://teamsystemrocks.com/blogs/omarv