Get them here.
I could relay the yadda-yadda on the virtues of applying the SPs, but I figure that’s being done to death out there already by more capable folks. Ok, I’ll toss this bit of verbiage in:
- SP1 advances the art of application development
The new ADO.NET Entity Framework feature in SP1 offers developers a model-based paradigm and a rich, standards-based framework for creating data-oriented applications shared across multiple applications and platforms. The separation of presentation, data, and business logic used in concert with a single data model will enable developers to spend less time writing plumbing code and more time refining business logic.
- SP1 makes data-driven programming easier
SP1 offers developers support for ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data-driven development. Since ASP.NET takes care of creating the presentation layer, a fully functional Website is output and ready for customization without the developer writing a single line of code. Furthermore, with ADO.NET Data Services, Web developers can create RESTful Web 2.0-style applications that have better server scalability and improved caching support.
- SP1 is the fastest and easiest way to deploy Windows applications
With the .NET Framework Client Profile, a small subset of the Framework that powers client applications, developers can offer their end users a dramatically streamlined and rapid application download experience. In addition, improvements in SP1 result in dramatic reductions in cold start times, allowing developers to serve a broader set of customers with varying hardware profiles.
As we wait for details on .NET 4.0, these SPs can take your current experiences with VS2008 to another level – especially for those in the webdev space.
acf2c73e-2031-4e4d-944c-c5c3c29321c2|0|.0
A family relation of mine (via my wife) recently started blogging on all things .NET and had a runaway success with his list of fifteen (15!) Visual Studio addins. Unlike other lists that you might see out there, Carl J actually took the time to install and try out each one so as to provide an informed and thoughtful opinion.
Fantastic work on this and I guarantee there's at least a couple there that even seasoned pros won't have heard of yet. Check it out.
2e7d9f54-fe96-4746-a49a-6af87befdf5d|0|.0
Today's topic of fun: Permissions
The final leg of the journey for upgrading and migrating our Scrum for Team System 1.0 artifacts to the 1.1 template requires a rebuild of the TFS Warehouse to ensure all items are consistent and integrity maintained.
Fine. The instructions note that this can be done from the Migration.exe utility -- click the checkbox marked “Rebuild Warehouse” and Bob should be your uncle. In my case, he skipped town and disowned me.
So, the alternative is to do it from the command line. Fine - so be it.
I've been hacking away at this for a goodly chunk of time and cannot seem to get around either a connectivity or permissions problem. When I run the rebuild command, as directed, I get this message for my troubles:
An unexpected error occurred when connecting to the Analysis Server. Check that your Analysis Server is up and you have sufficient privileges on it: A connection cannot be made. Ensure that the server is running.
Let the turkey... er.. troubleshooting begin:
Is the Analysis Server up? Yes. Even the services are up. Everything seems to be a-ok.
Do I have sufficient privileges on it? Ah, the sticky wicket.
I check the MSDN reference on the SetupWarehouse command and notice a footnote:
To use the SetupWarehouse command, you must be a member of the sysadmin security group for the SQL Server on the Team Foundation data-tier server.
I'm pretty sure my own domain account hasn't been granted such prowess, so I try logging on as one of the TFS service accounts (TFSReports) which is in the sysadmin security role for the SQL 2005 server. No dice.
So, either the permissions are still the issue or, we indeed have a connectivity issue. I Google-up a blog post on Troubleshooting Analysis Services 2005 connectivity problems run by Edward Melomed, an MSFT Program Manager for Analysis Services.
Looks like it has some good info, which led me to check whether remote connections are enabled for the server (they are) and how to play around with the SQL Server Surface Area Configuration tool. Still no idea what I am going to do to get a rebuild of my OLAP cubes for the migration.
b00aca02-da38-456b-ae99-e1ffd3bffb2e|0|.0
So, on it goes.
After following the advice of a helpful poster on the Community Forums for the template, I reviewed the titles for my Sprint Backlog items, looking for duplicates and renaming them accordingly.
That got me past the first round of problems -- but the unhandled exceptions persisted and I was stymied. So, I put out another call for help and long story short, I've got an update to the ComponentLibrary.dll that the migration utility uses -- does it address the unhandled exceptions issue I mentioned in my last post.
No.
The unhandled exceptions still occur, but now I get a helpful message telling me what work item caused the exception.
Hardly a solution for a released product -- unhandled exceptions shouldn't be occurring at all. Catch the exception, log it, let me know at the end so I can fix the issues afterwards. I'm still unimpressed with the solution as, for each exception, I have to delete the TFS project, re-create it and run the migration utility -- wasting a lot of time.
962ef5d2-fb77-461d-a14b-ede710f4fc3a|0|.0
Most of today I've been fighting with my friendly neighbourhood VSTFS server, trying to get it to successfully take the 1.1 upgrade for Conchango's Scrum for Team System process guidance template. A couple of notes from the battlefield:
Problem 1: Cannot create a blank TFS project
Symptom: Progress bar goes 85% of the way through then notifies you that a TF30225 error has occurred and the whole process has been aborted and rolled-back. Checking the status log reveals that the bailage is occurring while trying to upload the All Sprints report.
After a lot of checking around and dead-end leads, the solution I found that worked for me was to add the machine account for the TFS server to the sysadmin role on the SQL 2005 server that TFS is back-ended against, ie: DOMAIN\MACHINE_NAME$
Problem 2: Can't delete old & busted TFS projects
Sigh. Everything has to be done the hard way. Assuming that you have Team Explorer installed with your VS2005 IDE, there should be a console app hiding in your c:\Program Files\Microsoft Visual Studio 8\Common 7\IDE folder: tfsdeleteproject.exe
Supply this bad-boy with the name of your TFS server and the project you want to delete and poof! It's toast. Non-recoverable, of course. So, the command line would be something like:
c:\tfsdeleteproject /server:my.tfsserver.com “The TFS Project I Want to Delete”
Now, I have a whole other issue with trying to get the Migration utility to run successfully to port my 1.0 template artifacts into a 1.1 templated project -- I'm getting this unhandled exception (boo! what's with that?):
System.Exception: Cannot save work item ---> Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF26201: This work item has unsupported fields, or user does not have permissions. ---> Microsoft.TeamFoundation.WorkItemTracking.Client.ClientException: The issue cannot be updated.
Stay tuned - I'm sure there's a really simple (ha-ha) solution to this one.
c7df9ff1-c84c-402a-b5fe-2ef412330d1c|0|.0