StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POVS2012 automated deployment - OutputPath property is not set for project
primarykey
Id
15879965
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-04-08T13:11:18.807
FavoriteCount
1
LastActivityDate
2015-05-04T14:34:12.460
LastEditDate
LastEditorUserId
0
OwnerUserId
2160491
ParentId
0
PostTypeId
1
Score
2
ViewCount
747
LastEditorDisplayName
text
Body
Ok, I know this has been asked a bunch of times... I have tried to change the configuration and the outputPath, but still I have this issue. I am setting up automated build and deployment for our product. We have a single solution file and multiple projects within it. Using VS2012 and the default build definition, I have set the "Items to build" to a single project - the one we wish to have build and deployment for. Lets call this project "Forms". When I run the build definition, it builds and says success. However, it gives a warning: <blockquote> $/XXX/TRUNK/XXX/Forms.Web/Forms.Web.csproj - 0 error(s), 1 warning(s), View Log File C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (610): The OutputPath property is not set for project 'Forms.Web.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Release' Platform='Any CPU'. You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project. </blockquote> I have checked the .csproj file and there is a property group with the OutputPath specified. I've also tried various combinations of configuration/platform, but the issue remains. Does anyone have any idea what could cause this? It's driving me nuts. Without this fixed, no deployment is done... It seems to only build and doesn't even generate the .DLL files.
Tags
<c#><visual-studio-2012><tfs2012><build-definition>
Title
VS2012 automated deployment - OutputPath property is not set for project
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USuser2160491
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POVS2012 automated deployment - OutputPath property is not set for project
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POVS2012 automated deployment - OutputPath property is not set for project
 UserUserId
 USRePierre
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POVS2012 automated deployment - OutputPath property is not set for project
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.