WCF 4.0 Routing Service in IIS7

Interessante articolo sulla nuova feature di WCF.

http://seroter.wordpress.com/2010/03/09/simpler-way-of-hosting-the-wcf-4-0-routing-service-in-iis7/

Massimiliano

 

Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2 RTM

http://weblogs.asp.net/leftslipper/archive/2010/03/10/migrating-asp-net-mvc-1-0-applications-to-asp-net-mvc-2-rtm.aspx

Massimiliano

Windows Azure AppFabric : Go

Inizia oggi il periodo di billing di test per AppFabric che si protarrà fino al 9 Aprile quando verrà rilasciato ufficialmente la piattaforma.

http://www.microsoft.com/windowsazure/offers/

[OT] Trailer Tron Legacy in HD

http://www.youtube.com/watch?v=xJHcyGS9tkI

Massimiliano

WF Migration Kit CTP 1

The WF Migration Kit helps users migrate WF3 (System.Workflow) artifacts to WF4 (System.Activities). The high level goal is to migrate workflow definitions and declarative conditions, but not code (such as workflow code-beside methods). Some WF3 workflows will be fully migratable to WF4, while others will be partially migratable and will require manual editing to complete the migration to WF4.

The WF Migration Kit provides an API as well as a command line executable tool, which is a wrapper around the API. Migrators are included for some, but not all, of the WF3 out-of-box activities. The WF Migration Kit offers an extensibility point so that custom activity migrators can be developed by third parties.

The WF Migration Kit CTP runs on top of the Visual Studio 2010 and .NET Framework 4 Release Candidate, which can be found here. Please note that the Client Profile of the .NET Framework 4 is not sufficient since it does not contain the WF3 assemblies.

 http://wf.codeplex.com/releases/view/41401

 Massimiliano

Claims Identity Guide is now available in .PDF

Claims Identity guide is now available in .PDF

 http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4c09ffe4-43dd-4fcc-be35-c897c9bc4386

 

Massimiliano

AppFabric Beta2-Caching

Visto che nel mio progetto facevamo uso di AppFabric Beta1 per il caching.
In questo articolo viene spiegato le nuove features della beta2 per la parte caching.

-Added PowerShell cmdlets for configuring cache clusters. The commands are New-CacheCluster, Add-CacheHost, Get-CacheClusterInfo, Register-CacheHost, Remove-CacheCluster, Remove-CacheHost, and Unregister-CacheHost. These commands give you granular control of cluster deployment.

-The Cache service now throttles when it is under memory pressure. When it is in the throttling state the service will allow all “read” and “delete” requests but will reject all “write” and “update” operations. This prevents the service from engaging in excessive paging. Throttling events get logged to the Event Log and allow administrators to free available memory, add nodes to the cluster, or change the expiration or deletion policy of cached items, for example.

-The Cache service now logs information to two ETW channels. The Admin channel is enabled by default and collects all events like Start Cache Service and Stop Cache Service and any unhandled exceptions. The Operational channel is disabled by default. When it is enabled it captures all warnings from the Cache service. The Event Viewer shows the collected data under Applications and Services Logs -> Microsoft -> Windows -> Application Server – System Services.

http://blogs.msdn.com/velocity/archive/2010/03/02/announcing-windows-server-appfabric-beta2-release.aspx

Massimiliano

AppFabric Beta2

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a1ed6018-ddd1-4bd8-b4af-6561e910ebb4

Massimiliano

Workflow Persistence and FaultHandler

Ciao, all'interno del progetto su cui sto lavorando, si fa uso di WF (3.5).

Ho notato che, se per caso in un'activity richiamo un servizio wcf che va in errore, il workflow va in errore :

Inner exception: System.Workflow.Runtime.Hosting.PersistenceException: Type 'System.ServiceModel.Channels.ReceivedFault'
in Assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable. ---> System.Runtime.Serialization.SerializationException: Type 'System.ServiceModel.Channels.ReceivedFault' in Assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
 is not marked as serializable.

Facendo una ricerca su google, ho letto quest'articolo :

http://goffkock.blogspot.com/2009/07/workflow-persistence-and-faulthandler.html

in cui conferma l'errore e come work-around, consiglia di utilizzare i proxy invece dei channel.
A qualcuno è capitato una cosa simile ?

Grazie

WCF Relative Binding Speeds

Ciao, sto lavorando in un progetto che largo uso di servizi WCF.

Cercavo su internet, un test di performance sui vari binding di WCF.

Ho trovato questo articolo :
http://www.netfxharmonics.com/2006/01/WCF-Relative-Binding-Speeds.aspx

Molto interessante, ecco i risultati per un trasferimento di un datacontract minimo (una classe con una sola property di tipo stringa)

Ecco i risultati.

Con Security :
WSDualHttpBinding: Processed 1602 calls in 10 seconds
WSHttpBinding: Processed 2531 calls in 10 seconds
BasicHttpBinding: Processed 17913 calls in 10 seconds
NetTcpBinding: Processed 39957 calls in 10 seconds
NetNamedPipeBinding: Processed 48255 calls in 10 seconds

Senza security:
WSDualHttpBinding: Processed 5773 calls in 10 seconds
WSHttpBinding: Processed 17257 calls in 10 seconds
BasicHttpBinding: Processed 19528 calls in 10 seconds
NetTcpBinding: Processed 39756 calls in 10 seconds
NetNamedPipeBinding: Processed 47457 calls in 10 seconds

Ciao
Massimiliano

«marzo»
domlunmarmergiovensab
28123456
78910111213
14151617181920
21222324252627
28293031123
45678910