Microsoft is looking for a few good projects!

Through a local friend who's company that is the leading Connected Systems content provider for Microsoft, we are partnering with them and Microsoft to engage on projects to develop solutions built using Windows Server AppFabric, Workflow Foundation and Windows Communication Foundation. We will be co-sponsoring software development projects that meet business and technical criteria elaborated below.  If you are interested, feel free to email me (chris@architectingconnectedsystems.com) or DM me on Twitter (@givenscj).

Qualifying “Business Criteria”

·        Signed PR Release Form

·        Premier Support

·        MCS and/or Partner Engaged

·        Current Release of Product

 

Qualifying “Technical Criteria”

·        Hosting:  Throughput: WF/WCF > 100 tx/second

·        Integrated Platform: AppFabric, WIF, SharePoint Server or BizTalk integrated solution

·        Management: PowerShell API | SCOM

·        Monitoring:  >100M tracked events (15 events/instance @ 50 calls/sec, 8-hour day, over 5 days)              

·        Persistence:  >50K persisted active instances | >10 persist points/workflow

·        Tier1/Mission Critical:  Cache HA feature and WF/WCF mission critical application

 

 ·         Projects that have case study potential due to the client’s name.

o   Usually for companies that have strong name recommendation or a large in size, but exceptions often occur and smaller companies can still participate, just at a smaller dollar amount.

o   Example: a Fortune 1000 corporation embarking on a new project using Workflow Services or WCF Services hosted on Windows Server AppFabric.

·         Projects that are technically interesting.

o   The project may be developing items which are of interest to the broader Microsoft ISV community, and the work product can be generalized (e.g., removing the client’s IP) for sharing. For example, getting AppFabric to use Oracle for persistence and monitoring.

o   The project may well provide lots of feedback on less used aspects of AppFabric, WF and WCF that can be a source of bug reports to MS and guidance to the ISV community. For example, building a Workflow Services design environment completely external to Visual Studio.

o   The project itself does not have to be large in scope- it may be just a proof of concept effort. In effect, Microsoft will “seed” the development’s success.

WCF Timeouts on small memory’d SharePoint 2010 machine

In writing labs for an upcoming Microsoft Course, I found that the limitations on my environment was less than satisfactory to run all of the services of SharePoint 2010 at the same time.  Even though all Web Application and app pools were running, I was getting WCF timeouts mainly for the User Profile Service.  The default timeout value in SharePoint for the services is pretty much set to 20 sec.  If you have a machine that doesn't have the full 8GB of memory needed, then you may find your services are taking a while to spin up.  This can be devistating to some of the setup/install things you may be doing (because there are still many things that are NOT transnational). 

I found that by increasing the WCF timeout, I could avoid a lot of setup/install problems (mainly around service applications like User Profile).  To change the WCF timeout, open the C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14WebClientsProfileclient.config file, update the Bindings to double the timeout from "00:00:20" to "00:00:40".  Bam!  Your user profile won't timeout all the time and the service management page will display!

Chris

 

WCF – MessageSecurityException: The security timestamp is invalid because its creation time (‘2009-03-30T20:33:51.481Z’) is in the future.

What a crazy error.  I spent two hours on this today!  What ended up happening was that my machine ran it's Windows Time update and my web server did it's…they updated to be 15 minutes apart!  This caused my messages to stop working!  Man…wish the auth error had bubbled up the stack!  You have to add settings to the service side to get it to log the error, otherwise you will never know what is going on!  Reference this to see how to add the configuration value:

 <serviceSecurityAudit auditLogLocation="Application" serviceAuthorizationAuditLevel="Failure" messageAuthenticationAuditLevel="Failure" />

http://msdn.microsoft.com/en-us/library/ms731694.aspx

Chris