Friday, April 25, 2008
The fine folks on the Visual Studio team have changed all that. Thank you! (It's the little things in life...)
Wednesday, April 23, 2008
To accommodate the schedule of our speaker, we've moved our meeting this month to Tuesday April 29th from 5:30-7:30pm at the Polaris Microsoft office. (Normally, we meet every other month on the 1st Thursday, opposite the MOCSDUG.org user group.) Our web site is www.COALMG.org. Look forward to seeing you there!
Meeting Date & Time: 4/29/2008 5:30PM
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.
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.
The best explanation of ALM (I think) comes from Eric Sink who asks and answers "What is ALM? Traceability." Yes, it's long but worth the read.
We hope to answer this and lots of other questions about software development with the new group we formed called the Central Ohio Application Lifecycle Management Group (COALMG). Check it out. We hope to see you there!
Monday, April 21, 2008
.Net 3.5 Enhancements Training Kit Download
Overview of ASP.NET 3.5 Extensions Preview
ASP.NET 3.5 Extensions Preview
(unrelated) Central Ohio Application Lifecycle Management Group: COALMG
Update 4/22/2008: Props to Dan Hounshell for finding this CODODN video. I'm in there 2-3 times. Nice!
Friday, April 18, 2008
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.
I've been plagued by allergies since childhood: trees, cats, dogs, ragweed, you name it. I've been on every drug on the list. I can remember being sick every Easter and every birthday (end of September) for...well ever. A few years ago, I consulted an allergist who ran me through a series of tests, determined my exact allergies, and gave me some solid guidance.
Following my allergist's advice, I've not been 100% allergy/cold-free but I've noticed a significant improvement. His recommendations:
- Exam from an Ear, Nose, and Throat (ENT) doctor. I have a slightly deviated septum and some nasal dollops but otherwise, nothing horrid. He checked my jaw, my hearing...all kinds of stuff. Fortunately, nothing major is/was wrong. He did recommend I wear a mouth guard at night to prevent teeth grinding (which may cause eustachian tube clogging).
- Take a daily Loratadine (generic Claritin).
- Daily Fluticasone steroid nasal spray (generic Flonase).
- NeilMed Sinus Rinse in the morning and before bed.
- (I think I came up with this one but...) Wear a particulate mask (just one of the cheap ones) when mowing the lawn. I'm sure the neighbors think I look like a weirdo but [without scientific evidence] it helps keep the dust and particles from getting into my sinuses...and causing infections.
I hope you find relief from your allergies. Looks like this spring will be rough.
Wednesday, April 16, 2008
We finally got the RTM bits and I'm upgrading now. My steps:
- Follow the uninstall steps to the letter. Get rid of all that old stuff!
- Backup your existing TFS databases.
- Kick off the TFS 2008 installation and follow instructions
- Install everything else you need: Build, Proxy, Explorer, etc. Oddly, the installation utility must be re-executed and these services installed individually.
- Execute the TFS Best Practices Analyzer (BPA) found within the TFS 2008 Power Tools.
(Good how to here on BPA from Richard Hundhausen.)
- Resolve issues discovered with the BPA tool.
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).
Tuesday, April 15, 2008
[I missed this but props to Michael Collier for catching it.]
Saturday, April 12, 2008
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]
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".
Wednesday, April 02, 2008
"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.
Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:
- Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
- Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_Shrink == true didn't assist us in trimming the file sizes.
- Executed the following SQL as described here to understand the space available.
- Executed the following SQL as described here to shrink the log file down to 1GB (1000MB)
- Checked the data
- Performed a second backup for safe keeping