StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9454356
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-02-26T15:35:13.410
FavoriteCount
0
LastActivityDate
2012-02-26T15:35:13.410
LastEditDate
LastEditorUserId
0
OwnerUserId
50354
ParentId
9445915
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
For the most part the application migration is quite straight forward, but depending on your configuration and environment, you may need to make the following changes: <ul> <li>The new convention over configuration for endpoints may mean you will need to rename your endpoints to match your queue names (@andreasohlund has a good <a href="http://andreasohlund.net/2012/01/27/convention-over-configuration-in-nservicebus-3-0/" rel="nofollow">post</a> about this).</li> <li>persistence of saga, timeouts, subscriptions etc. now defaults to RavenDb, so if you use SQL Server to persist data, you need to make sure you have to correct profile and endpoint configuration. For SQL Server storage, make sure you add a reference to NServiceBus.NHibernate as it is no longer part of the core.</li> <li>Error queues are now referenced differently using different configuration ie. use MessageForwardingInCaseOfFaultConfig instead of the regular MsmqTransportConfig error property. You should still be able to use it, but it will look for the MessageForwardingInCaseOfFaultConfig first.</li> </ul> Other than that, I don't think you need to do anything else to get you upgrade working. I modified some of my message definitions to take advantage of the new ICommand and IEvent interfaces as a way communicatinf intent more clearly. Anyway, I'm sure there will be some cases that are specific to your environment that will require different changes but I hope this helps a bit.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMigration patch from NServiceBus 2.6 to NServiceBus 3.0
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USstephenl
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMigration patch from NServiceBus 2.6 to NServiceBus 3.0
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks setphenl, the configuration-over-convention changes are a good heads-up.
 singulars
 PostPostId
 PO
 UserUserId
 USSean Kearon
2. CONo problem, good luck!
 singulars
 PostPostId
 PO
 UserUserId
 USstephenl

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.