LinkedIn Suspicious Activity

Being a fan of LinkedIn I am frequently checking who’s viewing my profile. Approximately half a year ago I have noticed weird activity out there. My profile is being viewed by numerous “Accounting Professionals” with 0 connections. I have a feeling that someone not affiliated with LinkedIn is gathering account information and account updates.

UPDATE (2011-06-16): Wow, they listened. ;) Half of those profiles now shows as Anonymous LinkedIn User. They have changed thir privacy settings.

To whom it may concern: If you are scanning through LinkedIn profiles it makes sence to use only one account for that. Otherwise it shows ugly in Profile Stats.

Please comment if you experience the same activity or have any additional information.

Here is the list of suspicious accounts hitting my profile for the last three month:

Hulda Virgile
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Rico Natalizio
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Zulema Miyares
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Catheryn Rouw
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Moshe Hinkle
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Kendrick Corea
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Leopoldo Avner
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Ena Zenke
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Charley Darner
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Kellee Himelfarb
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Alana Shannon
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Julio Dyer
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Francisco Head
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Angelina Carroll
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Stanley Justice
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Isaac McCray
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Chester Booth
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

Fernando Sanchez
Title: Accounting Professional
Demographic Info: Greater New York City Area | Accounting

How to use MOSS Publishing EditingMenuActions

Let’s say you want to use any of the Microsoft provided Publishing EditingMenuActions. There are a few dozens of them.

For example, you want to save page and switch it to the view mode. If you try something like the following – it will fail:

SwitchToPublishedModeAction action = new SwitchToPublishedModeAction();
action.RaisePostBackEvent("switchToPublished"); 

You have to specifically assign the Page for the action. The following code will work:

SwitchToPublishedModeAction action = new SwitchToPublishedModeAction();
action.Page = this.Page;
action.RaisePostBackEvent("switchToPublished"); 

Any ConsoleAction is essentially a WebControl. It should either be placed on the page itself, and then referenced in your code, or you can just set its Page property.

Here is the list of actions accessible from Microsoft.SharePoint.Publishing.WebControls.EditingMenuActions namespace:

• public sealed class ApproveAction : BaseApproveAction
• public sealed class ApproveOrDeclineAction : ConsoleAction
• public abstract class BaseApproveAction : ConsoleAction
• public abstract class BaseDeclineAction : ConsoleAction
• public sealed class BrowseWebPartsAction : ConsoleAction
• public sealed class CancelApprovalRequestAction : ConsoleAction
• public sealed class CancelApprovalWorkflowRequestAction : ConsoleAction
• public sealed class CancelSchedulingAction : ConsoleAction
• public sealed class CheckInAction : ConsoleAction
• public sealed class CheckInWithCommentAction : ConsoleAction
• public sealed class CheckOutAction : ConsoleAction
• public sealed class CheckOutOverrideAction : ConsoleAction
• public sealed class CopyAction : ConsoleAction
• public sealed class CreateNewPublishingPageAction : ConsoleAction
• public sealed class CreateNewSiteAction : ConsoleAction
• public sealed class CreateNewsLinkAction : ConsoleAction
• public sealed class CreatePageVariationAction : ConsoleAction
• public sealed class CreateSiteVariationAction : ConsoleAction
• public sealed class DeclineAction : BaseDeclineAction
• public sealed class DeleteAction : ConsoleAction
• public sealed class EditListItemPropertiesAction : ConsoleAction
• public sealed class EditPropertiesAction : ConsoleAction
• public sealed class ExitMenuAction : ConsoleAction
• public sealed class ExitWithoutSavingAction : ConsoleAction
• public sealed class ForceSavePublishingPageAction : ConsoleAction
• public sealed class ImportWebPartsAction : ConsoleAction
• public sealed class ManageSiteAction : ConsoleAction
• public sealed class ModifyNavigationAction : ConsoleAction
• public sealed class ModifyPagesLibrarySettingsAction : ConsoleAction
• public sealed class ModifyWebPartsNode : ConsoleNode
• public sealed class MoveAction : ConsoleAction
• public sealed class OneClickPublishAction : ConsoleAction
• public sealed class PersonalViewAction : ConsoleAction
• public sealed class PreviewAction : ConsoleAction
• public sealed class PreviewExistingPublishingPageAction : ConsoleAction
• public sealed class PublishAction : ConsoleAction
• public sealed class PublishWithCommentAction : ConsoleAction
• public sealed class QuickDeployAction : ConsoleAction
• public sealed class ReportsNode : ConsoleNode
• public sealed class ReviewPublishingPageAction : ConsoleAction
• public sealed class RevisionHistoryAction : ConsoleAction
• public sealed class SavePublishingPageAction : ConsoleAction
• public sealed class SearchWebPartsAction : ConsoleAction
• public sealed class SharedViewAction : ConsoleAction
• public sealed class ShowUnapprovedResourcesAction : ConsoleAction
• public sealed class SiteDirectoryBrokenLinksCheckerAction : ConsoleAction
• public sealed class SiteSettingsAction : ConsoleAction
• public sealed class SpellCheckEntirePageAction : ConsoleAction
• public sealed class SwitchToAuthoringModeAction : ConsoleAction
• public sealed class SwitchToPublishedModeAction : ConsoleAction
• public sealed class UndoCheckOutAction : ConsoleAction
• public sealed class UnpublishAction : ConsoleAction
• public sealed class UpdateVariationsAction : ConsoleAction
• public sealed class VersionDifferenceAction : ConsoleAction
• public sealed class VersionInfoAction : ConsoleAction
• public sealed class ViewAllSiteContentAction : ConsoleAction
• public sealed class ViewRecycleBinAction : ConsoleAction
• public sealed class WorkflowApproveAction : BaseApproveAction
• public sealed class WorkflowDeclineAction : BaseDeclineAction
• public sealed class WorkflowStartAction : ConsoleAction
• public sealed class WorkflowStatusAction : ConsoleAction
• public sealed class WorkflowTasksAction : ConsoleAction

Enabling WCF support in SharePoint 2007 on Windows 2008 R2 IIS7

Installing SharePoint 2007 on Windows Server 2008 R2 sets SharePoint IIS application pools to Classic mode. In context of WCF this means that you have to manually configure WCF support in Web Applications web.configs. Otherwise you will get 404 errors trying to access any .svc files in your application.

In order to enable WCF support to SharePoint 2007 installed on Windows Server 2008 R2 with IIS 7.5, you have to put the following records to the web.config:

<system.webServer>
<handlers>
<add name="svc-ISAPI-2.0" path="*.svc" verb="*" modules="IsapiModule" scriptProcessor="%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" />
<add name="svc-ISAPI-2.0-64" path="*.svc" verb="*" modules="IsapiModule" scriptProcessor="%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness64" />
</handlers>
</system.webServer>

P.S.: It is probably the case with any web application runing in classic mode in IIS7.