Martin Hinshelwood's Blog

RDdotNET

Well I finally got of by behind and set up a site for RDdotNET, its not special or clever, but it does let me host ClickOnce Applications like the TFS Sticky Buddy and give a single portal to my other tools. I only have TFS Sticky Buddy and TFS Event Handler up at the moment, but I will expand on that.

Eventually all my bits and bobs will be up there with my blog over here.

Hopefully you will find the ClickOnce hosting useful, if not the site content…

posted @ Wednesday, July 30, 2008 6:19 PM | Feedback (0) |

Messenger United

Although the site is a little skewed today…

…This is an excellent application. Role on the LinkedIn sync.

When you click the button (the big green one) you get taken to another site that has the actual application on it.

This it seams is part of Microsoft's Connected Systems initiative that Bill has been pushing for years. They are now starting to open up their services (recently with their Exchange and Messenger products) to allow better integration with third parties.

For those that do not use Hotmail (perish the thought) the only sync / import available is the Facebook one.

posted @ Tuesday, July 08, 2008 7:50 AM | Feedback (6) |

Error creating listener in Team Build

If, like me you are trying to run tests against your web services and you the error below, you will need to give permission to the service account that runs your Build Agent to create listeners in IIS.

Class Initialization method TestServiceProjects.RentalCentreServiceRemoteTest.MyClassInitialize threw exception. System.ServiceModel.AddressAccessDeniedException:  System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:3456/RentalCentreServiceRemoteTest/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details). --->  System.Net.HttpListenerException: Access is denied.

I first tried giving the service account administrator rights, and this did not work, so I added “Act as part of operating system”. Lo and behold, that worked…

Happy now…

posted @ Friday, July 04, 2008 4:09 PM | Feedback (1) |

TFS Error: MSB4018 The "BuildShadowTask" task failed unexpectedly

There seams to be a problem in MSBuild when you add an “Accessor” as part of a Unit Test project.

C:\Program Files\MSBuild\Microsoft\VisualStudio\v9.0\TeamTest\Microsoft.TeamTest.targets(14,5): error MSB4018: The "BuildShadowTask" task failed unexpectedly.
System.IO.FileLoadException: API restriction: The assembly 'file:///C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll' has already loaded from a different location. It cannot be loaded from a new location within the same appdomain.
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, StackCrawlMark& stackMark)
   at System.Reflection.Assembly.ReflectionOnlyLoadFrom(String assemblyFile)
   at Microsoft.VisualStudio.TestTools.UnitTesting.Publicize.WebBinder.LoadData()
   at Microsoft.VisualStudio.TestTools.UnitTesting.Publicize.WebBinder.Init()
   at Microsoft.VisualStudio.TestTools.UnitTesting.Publicize.Shadower..ctor()
   at Microsoft.VisualStudio.TestTools.BuildShadowReferences.BuildShadowTask.Execute()
   at Microsoft.Build.BuildEngine.TaskEngine.ExecuteInstantiatedTask(EngineProxy engineProxy, ItemBucket bucket, TaskExecutionMode howToExecuteTask, ITask task, Boolean& taskResult)

An Accessor allows your test project to access code that would normally be “Private” or “Friend” from outside the Assembly that it resides in.

It creates a little file with the “.accessor” extension that is the same name as your DLL, and contains the name of the DLL.

If you remove this file then your remote MSBuild server will then build you solution successfully again including running your Unit Tests.

Reference:

Re: BuildShadowTask Failed unexpectedly - Accessor Problem (Upconvert VS 2005 to 2008) – URGENT

BuildShadowTask Failed unexpectedly - Accessor Problem (Upconvert VS 2005 to 2008) – URGENT

posted @ Thursday, July 03, 2008 4:54 PM | Feedback (1) |