The fine folks on the Visual Studio team have changed all that. Thank you! (It's the little things in life...)
Business and technology musings with an occasional economic, political, or consumer experience teaser thrown in to keep you on your toes.
Meeting Date & Time: 4/29/2008 5:30PM
Session Description:
Microsoft Visual Studio Team System is an extensible, life-cycle tools platform that helps software teams collaborate to deliver modern, service-oriented solutions. Visual Studio Team System is designed so every role in the development team has an integrated, seamless experience with the tools they are most comfortable with. Code Analysis, Code Metrics, Code Profiling, and Unit Testing are tools that are part of Team System and can be used through the software development lifecycle to improve quality. The impact of software defects is one of the reasons it is difficult to control the costs of the development and deployment activities on software projects. It is commonly accepted that defects that get resolved later in the development cycle cost more to fix. Learn how you can reduce defects by using the tools provided in Visual Studio Team System Developer Edition 2008.
Speaker Bio:
Randy Pagels - ALM Technology Specialist, Microsoft Corporation
Randy is an Application Lifecycle Management (ALM) Technology specialist for the Heartland District providing expertise on the Visual Studio Team System and Team Foundation Server products. He helps customers get the most out of their ALM tools by explaining best practices, installation, and configuration through presentations, workshops, or quick starts. Prior to Microsoft Randy worked as a developer for 16 years in the IT area of DTE Energy. He has architectured and development many .Net web applications using agile methodologies.
In advance of my presentation, I'm posting the slides and sample projects on SkyDrive. Hope you enjoyed the presentation and please post questions and/or comments here. Thanks for attending.
Quick off-topic post about allergy relief...
The databases were updated automatically.

I received a "Processor type and speed do not meet recommendations." warning but pushed on...this is a proof-of-concept box.

Excuse you? I can't run the services under the account I'm installing under? Great...starting over.
Had some red flags with the Best Practices Analyzer but they were easily fixed. BPA is a great tool (check out this tool for other products as well: Sharepoint, SQL Server).
powershell.exe -command "Get-ChildItem 'C:\Temp\' -recurse | where {$_.LastWriteTime -le (Get-Date).AddDays(-7)} | remove-item -recurse"
Tack on a -whatif to the end of the script to see what would be affected without actually executing the action. Very powerful. PowerShell.
Come see my "What's New in ASP.Net 3.5 Extensions" talk at 11:40AM. Here's the entire schedule. Hope to see you there!
Preparing for my upcoming "What's New with ASP.NET 3.5 Extensions" presentation at the Central Ohio Day of .Net, I ran into a roadblock with my simple Silverlight demo.
I have a Silverlight application calling an ASP.Net Web Service (traditional ASMX). The Silverlight application is hosted on an ASPX page served up in an ASP.Net Web Application.
I kept receiving a mix of the following two errors:
An exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.dll but was not handled in user code
Additional information: [CrossDomainError]
---------------------------------------------------------------
An exception of type 'System.ServiceModel.ProtocolException' occurred in System.ServiceModel.dll but was not handled in user code
Additional information: [UnexpectedHttpResponseCode]
Arguments:Not Found
Essentially, this is saying, "hey this control/page you're browsing on safesite.com is trying to interact with something over on unsafesite.com...and we're preventing it". Good for security, bad for demos.
Originally, when creating my Silverlight application, I chose the "Generate an HTML test page to host Silverlight within this project" option instead of creating a new web application. Bad idea. You'll always experience this cross domain issue using the HTML hosting page while calling a backend service. I quickly switched to a web application.
The easiest fix for me was to switch the web site and web service from using Cassini localhost with dynamic ports to the machine name and named virtual directories.
Here's my original properties on the web service project:
I switched it to:
The fine folks at Microsoft even provided a helpful "Create Virtual Directory" button.
Within my Silverlight project, I also needed to update the Service Reference (orginal):
I switched it to:
After you Configure Service Reference (above), make sure you Update Service Reference (below) to update the configuration code built for you by Visual Studio:
Despite the Silverlight 2.0 Beta1 recent release, there is much traffic about this issue in the forums and on blogs. It's actually nothing new. I ran into this issue with Flash a while back. Another, more production-ready solution is to leverage a policy file indicating to the object (Silverlight, in this case) that it's ok to interact with a particular service on some other domain. This is a file named crossdomain.xml and/or clientaccesspolicy.xml. More information at "Some tips on cross-domain calls" and "How to: Make a Service Available Across Domain Boundaries".
RELATED
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.