Wednesday, 26 October 2011
Nokia with windows phone 7
Tuesday, 25 October 2011
Microsoft Dynamics CRM Delivers Social Productivity to Customers
Delivering Social Productivity
Social CRM is the convergence of social technologies with CRM processes and technology, and organizations today are looking for ways to leverage social technologies to deliver improved business results and customer satisfaction. The Microsoft Dynamics CRM approach to social technologies enables people to use social CRM in a highly productive way from within the tools they already know.
With the new release, Microsoft Dynamics CRM introduces new social collaboration capabilities that include the following:
| • | Activity feeds. Configurable, real-time notifications on important relationships and significant business events via a blended view of micro-blog posts and interactions for a person, customer or sales opportunity. |
| • | Micro-blogging. Status updates and notifications regarding business events and actions, providing simple experiences for users. |
| • | Conversations. Post questions, observations, suggestions and status updates, allowing users to collaborate quickly and efficiently, locate information or expertise and gather feedback from others. |
| • | Automated activity updates. Post information directly to the activity feed based on configurable event rules (for example, when a sales opportunity is closed). People can subscribe to or “follow” these activity feeds and consume them in a variety of ways. |
| • | Mobile activity feeds. A new Microsoft Dynamics CRM mobile Activity Feeds application for Windows Phone 7 allows users to view their activity feeds while away from the office.* |
“As companies grow across geographical and technological boundaries, businesses need to be able to capture knowledge and disperse it effectively to ensure people have the most up-to-date information when they need it,” said Jim Steger, co-founder and principal at Sonoma Partners. “To be effective, social tools need to be easily accessed and usable, they need to be searchable allowing you to filter information, and they need to be a holistic part of the CRM solution. Microsoft’s approach to social productivity uniquely meets those criteria.”
More information about Microsoft Dynamics CRM and a demonstration of the new social collaboration capabilities are available at http://crm.dynamics.com/nov2011.
Delivering a Unified Office 365 Experience and Enterprise Cloud Enhancements
Today, Microsoft Dynamics CRM Online and Office 365 provide a seamless experience for end users. With the Microsoft Dynamics CRM November 2011 service update, Microsoft Dynamics CRM Online simplifies cloud service management by offering a common administration, billing and provisioning platform with Office 365.**
In addition, the Microsoft Dynamics CRM November 2011 service update offers improved disaster recovery features with in-region replication to further help protect data and offer high levels of business continuity in the event of a disaster.
More information about partners and customers deploying Microsoft Dynamics CRM 2011 can be found at http://crm.dynamics.com. Those who want to follow and engage with the Microsoft Dynamics CRM community can do so at @MSDynamicsCRM, #crm2011.
About Microsoft Dynamics
Microsoft Dynamics CRM and ERP solutions empower your people to be more productive and your systems to last longer and scale as your business grows, while enabling you to derive the insights necessary to respond quickly in an ever-changing world of business.
Sunday, 23 October 2011
Microsoft Unveils Preview of Roslyn Compiler-as-a-Service
HoloDesk - Microsoft
Wednesday, 19 October 2011
Microsoft wants to transform your hand into a touchscreen
Tuesday, 18 October 2011
The Specification Pattern
Following pattern is very use full decupling intermediate functionalities in between two domains.
Thanks shanka (My team member) for valuable contribution on research
Cheers!!!!
Continuing our series on Domain Driven Design, we now get to one of the more interesting patterns in DDD – the Specification.
A Specification is, in simple terms, a small piece of logic that sits on it’s own and gives an answer to a simple question … “does this match?”
With a Specification we split the logic of how a selection is made, away from the thing we are selecting.
We have a Customer, and we want to be able check if they are eligible for a discount on a Product.
If we were to put a method on the Customer entity, for example .IsEntitledToDiscountPrice(Product) we start to couple our entities tightly together, and as the number of questions we want to ask of our entity increases, the more polluted its interface becomes.
To avoid this we can use a Specification.
Some Code – A First for the Series
The basic implementation of Specification has a single method .IsSatisifiedBy, in our Discount example above we may have a EligibleForDiscountSpecification, the method would be .IsSatisifiedBy(Customer c)
The actual Specification is variable in how it is defined, but a very simple version for this scenario would be:
public interface ISpecification{ bool IsSatisfiedBy(T sut); } public class EligibleForDiscountSpecification : ISpecification<Customer> { private readonly Product _product; public EligibleForDiscountSpecification(Product product) { _product = product; } public bool IsSatisfiedBy(Customer customer) { return (_product.Price < 100 && customer.CreditRating >= _product.MinimumCreditRating); } }
This now simplifies selection or matching, and the Customer and Product are no longer coupled – our Specification now knows how to decide if the Customer is eligible for a discount. Ignoring the fact that the following is a rotten unit test, we can use our Specification like this:
[Fact] public void TestSpecification() { var product = new Product() { MinimumCreditRating = 3, Price = 50 }; var spec = new EligibleForDiscountSpecification(product); var goodCustomer = new Customer() { CreditRating = 3 }; var badCustomer = new Customer() { CreditRating = 1 }; Assert.True(spec.IsSatisfiedBy(goodCustomer)); Assert.False(spec.IsSatisfiedBy(badCustomer)); }
Two things become very easy when using Specification – we can easily select from lists and we can pass dependencies without creating coupling.
Extracted from - http://devlicio.us/blogs/casey/archive/2009/03/02/ddd-the-specification-pattern.aspx
Monday, 17 October 2011
Microsoft Tellme "Say it. Get it."
The Future --------------It’s not about you learning the technology .It’s about the technology leaning about you
Monday, 3 October 2011
Enterprise app makers not fully embracing HTML5
While developers working on business apps agree that development of HTML5 is coming along, they’re not ready to abandon native applications. At Mobilize 2011, the theme was hybrid.
Salesforce.com SVP Sean Whiteley, speaking from very recent experience, said his company hedged their bets with a hybrid solution for their upcoming application, Do.com. He said Salesforce built it as a native app for iPhone and Android because they “didn’t want it to feel like a web app, it needed to be fast and snappy,” and it needed to take advantage of all the features available on the user’s iPhone or Android.
But for tablets, they did go HTML5. ”We’re doing it all. We didn’t have to make a decision, we just had to figure out what to do using what. HTML5 is still not there yet, it’s very early, but we do believe it will evolve.”
Adam Blum, CEO of Rhomobile, agreed that such a choice between the two does not need to be made. “It’s not HTML5 versus native. It’s all about native apps. You need device capability… but [you] also [need to] leverage HTML5.”
That’s because it’s all about getting people to use those apps at work. If they’re not easy to use, they won’t be used, and Blum says that you need native apps for that because people aren’t comfortable working on the web all the time. “They need to know that when they save something to a device you save it,” he said as an example.
Santiago Becerra, CEO and co-founder of MeLLmo said that while there are advantages to hybrid applications that leverage both native and HTML5, there are some things that are “impossible” to recreate in HTMl5. “For high-end experiences you really have to go native,” he said.
Blum agreed that native will stay out in front of where HTML5 is for a while. “I don’t think HTML5 will keep up with [native] device capabilities, but I do think you owe it to yourself as an enterprise developer” to incorporate HTML5 in enterprise apps in some way