Privacy Policy

This Privacy Policy governs the manner in which Event Live Pictures collects, uses, maintains and discloses information collected from users (each, a “User”) of the mobile app/Facebook app (“Site”).

Personal identification information

We may collect personal identification information from Users in a variety of ways, including, but not limited to, when Users visit our site, fill out a form, and in connection with other activities, services, features or resources we make available on our Site.. Users may visit our Site anonymously. We will collect personal identification information from Users only if they voluntarily submit such information to us. Users can always refuse to supply personally identification information, except that it may prevent them from engaging in certain Site related activities.

Non-personal identification information

We may collect non-personal identification information about Users whenever they interact with our Site. Non-personal identification information may include the browser name, the type of computer and technical information about Users means of connection to our Site, such as the operating system and the Internet service providers utilized and other similar information.

Web browser cookies

Our Site may use “cookies” to enhance User experience. User’s web browser places cookies on their hard drive for record-keeping purposes and sometimes to track information about them. User may choose to set their web browser to refuse cookies, or to alert you when cookies are being sent. If they do so, note that some parts of the Site may not function properly.

How we use collected information

Event Live Pictures may collect and use Users personal information for the following purposes:

  • To run and operate our Site
    We may need your information display content on the Site correctly.
  • To improve customer service
    Information you provide helps us respond to your customer service requests and support needs more efficiently.

How we protect your information

We adopt appropriate data collection, storage and processing practices and security measures to protect against unauthorized access, alteration, disclosure or destruction of your personal information, username, password, transaction information and data stored on our Site.

Sharing your personal information

We do not sell, trade, or rent Users personal identification information to others. We may share generic aggregated demographic information not linked to any personal identification information regarding visitors and users with our business partners, trusted affiliates and advertisers for the purposes outlined above.

Compliance with children’s online privacy protection act

Protecting the privacy of the very young is especially important. For that reason, we never collect or maintain information at our Site from those we actually know are under 13, and no part of our website is structured to attract anyone under 13.

Changes to this privacy policy

Event Live Pictures has the discretion to update this privacy policy at any time. When we do, we will revise the updated date at the bottom of this page. We encourage Users to frequently check this page for any changes to stay informed about how we are helping to protect the personal information we collect. You acknowledge and agree that it is your responsibility to review this privacy policy periodically and become aware of modifications.

Your acceptance of these terms

By using this Site, you signify your acceptance of this policy. If you do not agree to this policy, please do not use our Site. Your continued use of the Site following the posting of changes to this policy will be deemed your acceptance of those changes. Privacy policy created by

Contacting us

If you have any questions about this Privacy Policy, the practices of this site, or your dealings with this site, please contact us.

This document was last updated on April 30, 2015


Remove mapping between TFS and Project Server with empty Project (deleted Gantt)

As TFS admin I was asking to synchronize TFS with Project Server. There is nothing really special and MSDN is full of articles and guides about it.

But, what MSDN doesn’t say you is that if you had mapped a project on EPM with a team project on TFS and then you have deleted the project from EPM, you would experienced a lot of pains! You are not able to edit the synchronization system and, if you run the “TfsAdmin ProjectServer /GetMappedProjects” command, it will return you something like “Enterprise project  is mapped to team project XXX” where XXX is not an issue (it is the team project name) instead the big issue is the blank space between words “project” and “is”!!!

So, first piece of advice: never delete a project from Project Server without having unmapped it from TFS before.

But, what if someone else has deleted it without having unmapped it? Well, Microsoft doesn’t give you any solution and googling for it I didn’t find anything. Anyway, after having spent several months on it, I have found a solution.

But please attention: it is not a recommended solution by Microsoft: it is a my personal solution and it worked for me; anyway it could be really dangerous, so use it carefully and only if you are absolutely confident you are able to do it.

  1. Connet to the TFS Collection database (the name should be something like “Tfs_<CollectionName>”)
  2. Query table named “tbl_sync_mappings”: it should contain only one record
  3. You need to extract field named “mapping”: it contains an xml string; copy it in a text editor
  4. If you analyze the xml, you could find several useful infos but what you need is the “tpcProject” set of items: it contains on “psProject” item for each mapped EPM project!
  5. Compare this set with the output of the “TfsAdmin ProjectServer /GetMappedProjects” command and you will discover the deleted EPM projects. (If you want, you can query the MSP_Projects table inside ProjectServer_Published database with the id field of the “psProject” element to be sure that you are going to cut off the right one)
  6. So, what you need to do is simply eliminate the “psProject” element of “ghost” project and update the “tbl_sync_mappings” table: pay attention to not put any strange characters or space inside the xml!
  7. Et voilà, that’s all! Now run the “TfsAdmin ProjectServer /GetMappedProjects” command again and you will not see your deleted project anymore…




Solving error 8024402c for Windows Update

So far, many times I’ve found this strange error in Windows Update center stating that “Windows could not search for new updates”.

The reason is your pc is configured to access a WSUS Server that, for some reasons, isn’t accessible.

First question is: what is WSUS (Windows Server Update Services)?

WSUS or Windows Server Update Services is a free patch management tool available to Windows Server administrators allowing them to authorize, publish and distribute updates within a network (most of the times inside a domain).

Anyway, second (and most important) question is: how I can solve that error? It’s quite simple, following that procedure:

  1. Open registry editor (Start menu –> Run –> regedit)
  2. Find the following path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
  3. Chage the value of the UseWUServer from 1 to 0 (double click on it, change the value and click OK)
  4. Restart Windows Update service (Start menu –> Run –> services.msc, find the Windows Update service and click on Restart)

That’s all. Now you can download updates again.


EDIT 28/08/2013: On Windows 8 I’ve also experienced a different solution. From command prompt (as admin) type “netsh winhttp reset proxy” and then re-check for updates.

Use app.config transformation in WPF projects with ClickOnce publishing

Thanks to this great post of João Angelo, I finally found a solution to the issue of using app.config transformation in WPF projects with ClickOnce publishing.

Following are the steps I implemented to solve it:

  1. Right click on the WPF project and select Unload Project
  2. Right click on the unloaded project and select Edit projectname.csproj
  3. Add the following lines at the beginning of the file (just under the Project declaration):

    <!-- The transformation target (TransformWebConfig) in this targets file—>  

    <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets" />  

    <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" />

  4. Add the following lines at the end of the document (just before the Project tag closing):


    <!-- Prevent circular dependency on Build target –>    


    <!-- Override project config file name (By default is set to Web.config) –>    



    <!-- Removes the need to set config files Build Action as Content –>  


    <FilesForPackagingFromProject Include="$(ProjectConfigFileName)">      




    <!-- Insert transformation targets in the build process –>  


    <BuildDependsOn> TransformWebConfig; OverrideAppConfigWithTargetPath; $(BuildDependsOn); CopyTransformedConfig </BuildDependsOn>  





    <!-- Overrides AppConfigWithTargetPath allowing the transformed config to be used for manifest generation –>  

    <Target Name="OverrideAppConfigWithTargetPath">    


    <AppConfigWithTargetPath Remove="@(AppConfigWithTargetPath)" />      

    <AppConfigWithTargetPath Include="$(TransformedConfig)" Condition="'$(TransformedConfig)'!=''">        





    <!-- Copy transformed file to output directory –>  

    <Target Name="CopyTransformedConfig" Condition="'$(TargetName)' != ''">    

    <Copy Condition="Exists('$(TransformedConfig)')" SourceFiles="$(TransformedConfig)" DestinationFiles="$(OutputPath)$(TargetName)$(TargetExt).config" />    

    <Copy Condition="Exists('$(TransformedConfig)') And '$(TargetExt)' == '.exe'" SourceFiles="$(TransformedConfig)" DestinationFiles="$(OutputPath)$(TargetName).vshost.exe.config" />  


    <!--   Override After Publish to support ClickOnce      AfterPublish target replaces the untransformed config file copied to the   deployment directory with the transformed one   -->  

    <Target Name="AfterPublish">    




    <!-- Publish copies the unstransformed App.config to deployment directory so overwrite it –>    

    <Copy Condition="Exists('$(DeployedConfig)')" SourceFiles="$(TransformedConfig)" DestinationFiles="$(DeployedConfig)" />  


  5. Use the following lines to view App.Debug.config and App.Release.config under the default App.config file, as a subtree, in VS IDE:
     <None Include="App.Debug.config">
        <None Include="App.Release.config">
  6. Save the project and Reload the project.
  7. Try it changing the Build configuration and publishing the solution!

Reassigning the correct SSL certificate to SharePoint 2010 Web Services IIS Site

Yesterday I experienced an error on the Sharepoint 2010 Web Services IIS site. I wrongly changed the default binding certificate for the https protocol and the following are the errors I got in the event viewer:

The Secure Store Service application SecureStoreServiceApplication is not accessible. The full exception text is: There was no endpoint listening at https://sharepointserver:32844/d135288cc8de436c8d899a64003c5585/SecureStoreService.svc/https that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

An operation failed because the following certificate has validation errors:\n\nSubject Name: CN=<CN>, OU=<OU>, O=<O>, L=Rome, S=Rome, C=IT\n Issuer Name: CN=<CN>, DC=<DC>, DC=it\n Thumbprint: 8D149D3FA98CA0FF1F5D0077FFC4DF9D0318829A\n\n Errors:\n\n SSL policy errors have been encountered.  Error code ‘0x2’..

The Secure Store Service application SecureStoreServiceApplication is not accessible. The full exception text is: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was ’00:10:00′.

It was very frustrating because I unsuccesfully tried to rerun the Sharepoint 2010 configuration wizard, to cancel and recreate the binding and to change the certificate via the UI of IIS.

Then I found this excellent post about Rik Hepworth that solved my issue:

Basically the two command, I run, are:

netsh http delete sslcert ipport=0.0.0:32844


netsh http add sslcert ipport=0.0.0:32844 certhash=<thumbprint> appid=<appid> certstorename=SharePoint

After then I fixed the problem. Great!

For further reading, I also found this post that explain very well the SharePoint 2010 Certificates and Certificate Authority: