StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17534443
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-08T19:29:03.827
FavoriteCount
0
LastActivityDate
2013-07-08T19:29:03.827
LastEditDate
LastEditorUserId
0
OwnerUserId
211627
ParentId
17533744
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
This is possible via a number of possible routes. I'd prefer dependency injection in this case. First, create your global event owner project. I named mine GlobalEventSample. I removed the default namespace and declared it here explicitly to make the code structure more obvious: <pre><code>Namespace GlobalEventSample Public Module Module1 Public Event GlobalEvent As EventHandler Public Sub Main() Console.WriteLine("Press any key to raise event...") Console.ReadKey(True) RaiseEvent GlobalEvent(Nothing, EventArgs.Empty) Console.WriteLine("Press any key to quit...") Console.ReadKey(True) End Sub End Module End Namespace </code></pre> Now create the consumer project. I named mine GlobalEventConsumer. I removed the default namespace and declared it here explicitly (just as above): <pre><code>Namespace GlobalEventConsumer Public Interface IGlobalEventOwner Event GlobalEvent As EventHandler End Interface Public Class Class1 Public Sub New(ByVal globalEvent As IGlobalEventOwner) AddHandler globalEvent.GlobalEvent, AddressOf GlobalEventHandler End Sub Public Shared Sub GlobalEventHandler(ByVal sender As Object, ByVal e As EventArgs) Console.WriteLine("Event Handled!") End Sub End Class End Namespace </code></pre> Notice that I've declared an interface named "IGlobalEventOwner". All it does is define an object with an event. This event has a signature identical to the global event we want to handle. Go back to the sample project and create a reference to the consumer project. The consumer project requires an object which implements IGlobalEventOwner. Modules cannot implement interfaces, so we instead create a private class, GlobalEventRouter, which will simply handle the module's event and then fire its own event. Finally, we will create a new instance of Class 1 in the Main sub and pass an instance of the GlobalEventRouter class. <pre><code>Namespace GlobalEventSample Public Module Module1 Public Event GlobalEvent As EventHandler Public Sub Main() Dim consumer As New GlobalEventConsumer.Class1(New GlobalEventRouter()) Console.WriteLine("Press any key to raise event...") Console.ReadKey(True) RaiseEvent GlobalEvent(Nothing, EventArgs.Empty) Console.WriteLine("Press any key to quit...") Console.ReadKey(True) End Sub Private Class GlobalEventRouter Implements GlobalEventConsumer.IGlobalEventOwner Public Event GlobalEvent(ByVal sender As Object, ByVal e As System.EventArgs) Implements GlobalEventConsumer.IGlobalEventOwner.GlobalEvent Public Sub New() AddHandler Module1.GlobalEvent, AddressOf GlobalEventHandler End Sub Private Sub GlobalEventHandler(ByVal sender As Object, ByVal e As EventArgs) RaiseEvent GlobalEvent(sender, e) End Sub End Class End Module End Namespace </code></pre> The output: <blockquote> Press any key to raise event... Event Handled! Press any key to quit... </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEvents in a VB.Net multi-project solution
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJDB
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.