StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4533823
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-26T12:35:26.570
FavoriteCount
0
LastActivityDate
2010-12-26T12:35:26.570
LastEditDate
2017-05-23T10:33:07.437
LastEditorUserId
-1
OwnerUserId
221933
ParentId
3435985
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The way I understand your description, you have two problems: <ol> <li>A project reference from project A to project B is broken when the projects are instantiated</li> <li>A reference to a dll is broken when the project is instantiated</li> </ol> I'm also having problems with 1), and haven't found a way to solve that yet. For 2) you must make sure that the dll you are referencing is part of the project itself, and is listed in the project's content in your vstemplate metadata file. See for instance my template for F# and XNA: In the .fsproj file (similar to a .csproj for a C# project): <pre><code> <ItemGroup> <Reference Include="FSharp.Core"> <HintPath>Dependencies\FSharp.Core.dll</HintPath> </Reference> </ItemGroup> <ItemGroup> <None Include="Dependencies\FSharp.Core.dll"/> <None Include="Dependencies\FSharp.Core.xml"/> <None Include="Dependencies\FSharp.Core.sigdata"/> <None Include="Dependencies\FSharp.Core.optdata"/> </ItemGroup> </code></pre> In the .vstemplate file: <pre><code> <Folder Name="Dependencies" TargetFolderName="Dependencies"> <ProjectItem ReplaceParameters="false" TargetFileName="FSharp.Core.dll">FSharp.Core.dll</ProjectItem> <ProjectItem ReplaceParameters="false" TargetFileName="FSharp.Core.xml">FSharp.Core.xml</ProjectItem> <ProjectItem ReplaceParameters="false" TargetFileName="FSharp.Core.optdata">FSharp.Core.optdata</ProjectItem> <ProjectItem ReplaceParameters="false" TargetFileName="FSharp.Core.sigdata">FSharp.Core.sigdata</ProjectItem> </Folder> </code></pre> See also <a href="https://stackoverflow.com/questions/1343857/visual-studio-project-template-and-private-assembly-referencing">Visual Studio Project Template and Private Assembly Referencing</a> for an alternative solution if you don't want to include the dll in your template.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to keep reference between two projects when making a template in Visual Studio 2010
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJoh
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. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.