StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3047263
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-15T16:48:58.653
FavoriteCount
0
LastActivityDate
2010-06-15T16:56:39.370
LastEditDate
2010-06-15T16:56:39.370
LastEditorUserId
243245
OwnerUserId
243245
ParentId
3047055
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You mean <a href="http://mvccontrib.codeplex.com" rel="nofollow noreferrer">http://mvccontrib.codeplex.com</a>? They publish source, so probably the easiest way is to download their source and rebuild it yourself. Essentially you need the assemblies, PDB files that correspond exactly to the built assemblies, and source code on disk where the PDB files can find this. You can either <ol> <li>rebuild the source yourself: this way you have new assemblies, new PDBs and source code on disk in the exact place referenced by the PDBs. Either add their projects to your solution build it in place. The downside with this is that they might have odd external dependencies that they might not include or a crazy build system so this might not be trivial. (A further downside is that you'll then be testing and debugging with your own build not their official release. Depending on your deployment policies you may prefer to run production code against the official build not your own, and there's a risk with switching back to the official build albeit minimal. Hopefully you have unit tests you can use to revalidate after debugging!)</li> <li>download their PDBs - this looks like it's in their "Extras" download and unpack these alongside the corresponding assemblies on disk. Download their source and unpack theis too: if possible, into the same path that is hard-coded into the PDBs as the place where the source was built from (you'll be prompted for this the first time you try to step into it) or add the path you've extracted the source into to the source directories list under tools/options.</li> </ol> Either way you'll probably have to untick the 'step into my code only' option in Tools\Debugging unless you go down the add-to-your-solution route if you want to actually step into their code, although if you just want to catch exceptions inside their code and debug from there this shouldn't be necessary.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I debug my MVC application together with MVC contrib project downloaded from codeplex
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRup
UserOwnerUserId
1. USRup
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I debug my MVC application together with MVC contrib project downloaded from codeplex
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.