Since I installed Outlook 2010 technical preview I have not been able to search emails using the ‘search mail’ boxes in Outlook (which links into Windows desktop search). I had not realised how much I used the feature until it did not work. When I tried a search I was shown a dialog saying there was 40000+ items waiting to be indexed, and this number was not changing. It seemed that the indexing of Outlook contents had stopped.
The solution I found was to reset the indexing process.
- In Outlook select the back stage (brown button)
- Select Outlook options
- Select Search
- Select Indexing Options button
- Use the modify button to remove all options from the locations to be indexed
- Use the advanced button to select a re-index (with nothing selected)
- Use modify button again to re-select all the item you want to index (including Outlook)
- Finally use the advanced button again to select the re-index option to restart the process
- I then had to wait 24 hours, but at least I could see the index items count going up at the top of the Indexing options dialog until I got the message Indexing complete..
You can connect a Visual Studio 2008 IDE instance to a TFS 2010 server, as detailed in Martin Hinshelwood’s blog, but I cannot stress enough you have to have VS2008 SP1 installed. If you don’t, you get an error dialog when you enter the URL for the TFS server saying the URL contains invalid characters.
This seems a simple rule, but as I found today it is easy to not realise your PC is not patched. You look in the about dialog for Visual Studio and it says SP1 installed, but the Team Foundation Client has not been. This was because the following installation order was followed:
- Install VS2008
- Patch with SP1
- Install Team Foundation Client
The SP1 needed to be run again to patch the client then all was OK
With all this coverage of the moon landings I am surprised that the other major news item of 40 years ago today has not been covered – the Fennell family moved house. I ask you just what are the priorities of the news media?
I downloaded and installed the Office 2010 technical preview today. All seemed to go OK (after I realised I could only do an in place upgrade from 32bit Office 2007 –> 32bit Office 2010), once the upgrade was done I could load Word and using our VSTO based document templates all seemed to work fine. However when I tried Outlook I got a problem.
On the first loading it took a while, telling me it was doing something to 40K+ items, presumably checking the local OST file, but then seemed to load OK. However after about 30 seconds it crashed, and continued to do this every time I rebooted Outlook even when I was tried safe mode, add-ins switched off and/or offline working. It all had no effect. Checking the event log I saw I had the error:
Faulting application name: OUTLOOK.EXE, version: 14.0.4006.1110, time stamp: 0x4a468538
Faulting module name: mlang.dll, version: 6.1.7100.0, time stamp: 0x49eea59f
Exception code: 0xc0000005
Fault offset: 0x00016aef
Faulting process id: 0x1060
Faulting application start time: 0x01ca06e3140fb30d
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
Faulting module path: C:\Windows\system32\mlang.dll
Report Id: 5af5a171-72d6-11de-97df-001636a51764
I noticed that the in place upgrade had not removed Office 2007, so I did this via the control panel. After this Outlook loaded and was stable other than the fact the view panel would not load (was grey’d out on the menu), so stable but useless
I then tried a removing Office 2010 (there is no repair option) and reinstalling again using the same 32bit media. This time it knew it was not doing an upgrade but a new install. Once this completed I loaded Outlook and it worked fine including picking up my existing OST file (from a non default location, I keep it on a bitlocker partition) and also still had my CRM 4.0 add-in configured and working.
So it seems the upgrade can get bit confused
Thanks to everyone who turned up for my presentation on Typemock and Sharepoint in Glasgow last night. I have just upload my slides onto the Black Marble site. As the session was quite demo driven the slides don’t offer the best code samples. If you want to experiment yourselves I would suggest you look at my related posts on this blog and remember if you don’t have Typemock you can download trial versions of all the products I used from www.typemock.com
On Wednesday the 15th this week I will be speaking at Scottish Developers on developer testing of SharePoint. This is a free event so please come along if you are interested and in the area.
If you are not able to make it to Glasgow but are interested in the subject then why not check out Typemock’s free live webinars also on the 15th.
VS2010 has excellent new features to assist the tester in general, and specifically in the area of manual testing. One of these is the ability to video a manual test run; to get this to work you have to have the Windows Media Encoder 9 installed as well as the VS2010 Test Runner . If you don’t have it installed and try to use the video feature you get a dialog that warns you this component is missing and would you like to either download it or disable video recording feature for this test run.
The problem is the warning dialog has a link that takes to you the Windows Media Encoder 9 homepage. This gives you the option to install either the 32bit or 64bit version. I mistakenly assumed that I needed the version for operating system I have i.e. 64bit as I run 64bit Windows 7. THIS IS WRONG.
VS2010 Test Runner only seems to work if you have to install the 32bit and the hotfix the Test Runner dialog mentions. Once I installed the 32bit video recording of the test worked perfectly.
Ben Hall has written an interesting post on creating a testing framework with MEF. As Ben said it is more a learning exercise for MEF than a useful product but it certainly show show the ease you can add meta data and reflection like functionality to your codebase. Wish it had been about when I wrote GUITester
I have posted in the past about the TFS 2005 and 2008 Process Template eScrum from Microsoft; a template we use internally for a number of Agile projects. Well today it has been removed from the Microsoft download sites.
It was decided a while ago that it would not be updated to support TFS2010 and has been removed to avoid any confusion over whether it is support or not by Microsoft (FYI it was never officially supported anyway as it did not originate inside the TFS team)
So are we at Black Marble going to miss it? Well the main reason we had used it in the past was the web interface that gave a single point for updating the status of work items without the need to enter Visual Studio, it was our project wallboard. With the much enhanced Office integration with TFS2010 I think we are not going to miss eScrum. We can now provide an easy way with Excel or Project for any team member (developer or not) to update their work status and also Excel Services to provide a information radiator showing the overall project status.
If you do need a strict Scrum implementation template for TFS then have a look at Conchango’s Scrum for Team System which is going to be updated to make use of all the new features of TFS2010
On my development PC I had a 2005 instance of SQLExpress that was installed as part of the VS2008 setup. I thought I had upgraded it when I put on the SQL 2008 Management tools and/or VS2010 beta, but it seems I didn’t. I thought I would try the new Microsoft Web Platform Installer, but this also thought I had done the upgrade to 2008, I suspect due to the fact I had the 2008 management tools.
Note: If you are using the Microsoft Web Platform Installer 2.0 RC remember you can’t just click on it to run from the web if you are running as a non-administrator user on your PC (as you should be, running least privilege). You need to download it and ‘run it is administrator’ or open it in a browser running as administrator to get it t even load.
So I needed to download the SQLExpress 2008 media to do a manual upgrade, as I remembered I could not use the developer edition media I had to hand to upgrade and Express instance. This download in itself proved problematic. I did a downloaded from MSDN, but the file I got gave a ‘not a valid win32’ error when I tried to run it. Also I noticed each time I tried to download it in IE8 it was a different size – not a good sign! Once I swapped to Firefox it downloaded without issue.
Anyway in the end I got the right media and access rights and the upgraded went smoothly. However then I tried to attach a 2008 DB (the reason I needed the upgrade in the first place) I got the error
Parameter name: nColIndex
Actual value was -1. (Microsoft.SqlServer.GridControl)
I had yet again forgotten to run SQL Management Studio as an administrative user. This error dialog is SQL Management Studio was of saying you don’t have the rights!
Don’t forget this month’s Agile Yorkshire meeting is this Wednesday at the Victoria Hotel in Leeds. It is the usual mix of free beer, great conversation and an excellent speaker (note: you can assign your own ranking order as these factors, using a suitable Agile planning model).
This month the speaker is Nancy Van Schooenderwoert on ‘Seven Paradoxes of Agile Software Development’.
Hope to see you there.
To have a good look at TFS2010 I have migrated some existing VS2008 projects to VS2010. This has meant they are now being built using a new TFS 2010 build server. Now I wanted to make sure everyone still knew what was building and what was not, so I updated the configuration on our build wallboard to get the status from both the older 2008 and the new 2010 server – and it did not work. I fiddled around, upgraded the build wallboard to use the TFS2010 assemblies, all to no avail, the application just exited when I tried to get a reference to the build service.
Then I had another think, the Url of the TFS server has changed format in 2010. It used to be http://my2008server:8080 it is now http://my2010server:8080/tfs. I had been leaving off the trailing /tfs, an easy mistake to make. Once this was corrected my old build wallboard worked without a problem, there was no need to use the TFS2010 assemblies in the project.
After I upgraded an ASP.NET Web Application VS2008 solution to VS2010 I found a strange problem. When I build either the whole solution or the test project in the solution the test assembly gets copies to Web Applications bin directory. However if I build the solution from the command line with MSBUILD they are not copied (so MSBUILD behaves as VS2008 used to).
Turns out it is easy to repeat, the process is as follows:
- Open Vs2008 SP1
- Create an empty solution
- Add a C# Class library project (targeted on .NET 3.5)
- Add a C# ASP.NET Web application (targeted on .NET 3.5)
- Add reference from the web application to the class library
- Build the solution, note that we see the class library and web application assemblies are in the web application bin directory
- Add a C# Test project 3.5 (targeted on .NET 3.5)
- Add reference to the Web application project
- Build the solution, note that we still just see the class library and web application assemblies are in the web application bin directory – there is no test assembly
- Exit VS2008 and load VS2010
- Load the solution and allow it to be upgraded. On the dialog about .NET versions say to leave the projects on .NET 3.5.
- Rebuild the solution and note that now in the Web Application bin directory we have the class library, web application and test assemblies
- Do a clean of the solution, note that in the Web Application bin directory the test assembly is not removed.
So why is this a problem? .NET 4.0 is a replacement for previous .NET version not an extension as 3.0 and 3.5. were for 2.0. This means basically that in any given deployment you need to have all 4.0 assemblies or all 2.0, 3.0, 3.5 ones. However, under VS2010 a test project must target .NET 4.0 (to get all the new cool testing features), so the fact at this 4.0 test assembly ends up in a 3.5 based Web Application directory is a problem.
I have no answer to the problem as yet, though I have reported it. At present the workaround is to either
- Delete the test assemblies from the Web Application bin directory. once this is done everything behaves as you would expect.
- Or make sure you only target .NET 4.0, though I suspect this might be an issue for some people developing web applications as it will be a while before we see ISP deploying .NET 4.0
I am really happy to say that I have had my MVP for Team System Re-awarded, it is a privilege to get to work with such a great group of people as a have met via the MVP programme.