Search

Team Foudation Services by RodeoGon

Closed
as By Design Help for as By Design

1
0
Sign in
to vote
Type: Bug
ID: 776360
Opened: 1/11/2013 11:20:26 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When adding certain references MSBuild fails on tfs.visualstudio.com.

In this case Microsoft.Exchange.WebService

Buld and Deployment from Visual Studio 2012 works OK:

Error shown as:

Pages\About.aspx.cs (7): The type or namespace name 'Exchange' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Add reference to the project that has source control to Team Foundation Service for Exchange Web Service Managed API 2.0

Check in / or queue Build through interface, Build Fails

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

1 error(s), 1 warning(s)
$/Elix Web/WWW/Web.sln - 1 error(s), 1 warning(s), View Log File
Pages\About.aspx.cs (7): The type or namespace name 'Exchange' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1578): Could not resolve this reference. Could not locate the assembly "Microsoft.Exchange.WebServices". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

Expected results

It Should Build Successfully
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/18/2013 at 7:12 AM
Yes, that is the correct thing to do. The Hosted Build machines have a limited set of SDKs installed. Anything that's not there should be brought in via checking it in (as you did) or NuGet (if available).

Posted by Microsoft on 1/18/2013 at 7:12 AM

Posted by RodeoGon on 1/14/2013 at 2:56 AM
I have sorted this out now, and added custom binaries and added to the hosted build configuration.

It all works
Posted by Microsoft on 1/14/2013 at 2:51 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/11/2013 at 11:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.