Comuni d’Italia goes live…on Windows 8 store!

Are you looking for information regarding an italian municipality like CAP, Fiscal Code or phone prefix? Do you want to have a quickly look at all municipalities in your region? Now you can with “Comuni d’Italia” for Windows 8.

Check-it out at


Free trial period for 30-days!


Solving problem: Nokia Lumia 800 doesn’t boot

Happy new year….and fortunately happy new solution! (I don’t really know if I’m lucky because of all those solutions or particularly unlucky because of all those problems!!)

Anyway: this evening my almost new (only one month old) Lumia 800 didn’t boot.

I found this simple solution from Nokia’s website (completely different of my personal experience with LG customer care).

  1. Connect your phone to your PC and start Zune
  2. Press and hold (for 10 seconds) both Volume down and Power buttons until your phone will vibrate
  3. Release them and after a little it should restart

Hope this will help a lot of you, as always!

Happy new year everyone

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!