Wednesday, November 10, 2010
Monday, November 01, 2010
For People who attended the PDC in Redmond, or attended Local PDC as the one that has been held in Cairo, We all heard from BOB Muglia said that Silverlight strategy has been shifted. This doesn’t mean that Silverlight will die but, it will take a newer vision.
Couple of Minutes ago, Bob himslef has published a message for all PDC attendees clarifying this. The following words are an excerpt from Bob’s message.:
In the interview, I said several things that I want to emphasize:
- Silverlight is very important and strategic to Microsoft.
- We’re working hard on the next release of Silverlight, and it will continue to be cross-browser and cross-platform, and run on Windows and Mac.
- Silverlight is a core application development platform for Windows, and it’s the development platform for Windows Phone.
We haven’t yet publically announced a launch date for the next release of Silverlight, but we’ll talk more about it in the coming months.
Last week, we released some important updates to Silverlight 4, which shipped only six months ago and included major new features and tooling capabilities. Last week’s updates included improvements to WCF RIA Services, as well as the new Portable Library project –making it easier to share assemblies across SL Desktop, SL Phone, WPF and .NET on the server. John Papa delivered a PDC session on building business apps with Silverlight 4, and Shawn Burke delivered a PDC session on the portable library project. I recommend that you take a look at both of these.
I said, “Our Silverlight strategy and focus going forward has shifted.” This isn’t a negative statement, but rather, it’s a comment on how the industry has changed and how we’re adapting our Silverlight strategy to take advantage of that.
Below are some of the trends we’re tracking and optimizing around.
Customers are demanding the richest possible client experiences, and developers are increasingly looking to build premium, tailored experiences optimized for specific devices. Silverlight provides the richest way to build Web-delivered client apps. In particular, with Silverlight 4, we invested in enabling enterprise application development and now provide an outstanding platform to build rich business applications – both inside and outside the browser.
Customers want to be able to deliver client experiences that are optimized for specific form factors. Silverlight provides a rich UI framework that enables smooth animations and lends itself very well to touch input and embedded devices. At the PDC last week, we spent a lot of time talking about Windows Phone 7 and how Silverlight provides a great developer platform for creating apps for it. With the U.S. launch just days away, already we have more than 1,000 Silverlight apps built for Windows Phone, and consumers of the phone will be able to purchase these apps through an integrated marketplace built into each device. Recently, we’ve also demonstrated Silverlight apps running on Windows Embedded, and Silverlight is a critical component of our three-screen strategy.
Media delivery across the Internet continues to accelerate dramatically. Customers want HD, studio quality, premium media content. Silverlight has and will continue to be a pioneering technology that makes it possible to deliver the best media experiences anywhere. Whether it’s the Olympics, Netflix, or many other media experiences, we have and will continue to invest in it. Silverlight and IIS Media Services are the choice for premium media experiences with features like HTTP adaptive streaming, DECE-approved content protection, and offline media applications. In addition, IIS Smooth Streaming enables media delivery to a wide variety of devices, including devices where Silverlight isn’t supported.
Lastly, there has been massive growth in the breadth and diversity of devices made by a wide variety of vendors providing both open and closed systems. When we started Silverlight, the number of unique/different Internet-connected devices in the world was relatively small, and our goal was to provide the most consistent, richest experience across those devices. But the world has changed. As a result, getting a single runtime implementation installed on every potential device is practically impossible. We think HTML will provide the broadest, cross-platform reach across all these devices. At Microsoft, we’re committed to building the world’s best implementation of HTML 5 for devices running Windows, and at the PDC, we showed the great progress we’re making on this with IE 9.
The purpose of Silverlight has never been to replace HTML, but rather to do the things that HTML (and other technologies) can’t, and to do so in a way that’s easy for developers to use. Silverlight enables great client app and media experiences. It’s now installed on two-thirds of the world’s computers, and more than 600,000 developers currently build software using it. Make no mistake; we’ll continue to invest in Silverlight and enable developers to build great apps and experiences with it in the future.
End of Bob Clarification….
More and above Steve Ballmer:
has said the following that emphasizes that Silverlight will continue to be a very important product at Microsoft Products’ roadmap :
[We’ve seen the emergence of a wide variety of Internet connected devices – and as I said last week, HTML 5 will provide the broadest, cross-platform reach across these devices, and Microsoft will build the world’s best implementation of HTML 5 for devices running Windows. At the PDC we showed the great progress we are making on this with IE 9. We will also enable browser scenarios that provide additional capabilities, including Silverlight. Silverlight provides the richest media streaming capabilities on the web, and we will continue to deliver that on both Windows and Mac.
Client applications are important to take maximum advantage of devices, and we will deliver rich platforms and frameworks that enable developers to best take advantage of them. We’ve sold more than 240 million copies of Windows 7 in the last 12 months - an absolutely phenomenal number. Developers can build great applications for it using Win32, .NET, Silverlight and HTML5. ]
Thursday, October 28, 2010
A few Minutes ago, Brian Harry has just announced and demoed the Availability of the Team System as Service over Microsoft Cloud for renting. Think this will be of a great benefit for lots of small, and Medium ISVs that wont to invest in licensing, admin, and operations of a dedicated Team system installation.
Sunday, October 03, 2010
SharePoint 2010 leads the Gartner Magic Quadrant 2010, Microsoftians now in an even stronger position than before
Last September, 3, 2010 Gartner has released the new portals’ market report.
The great news was that SharePoint 2010 Leads the Magic Quadrant of Horizontal Portals; heading in this, IBM WebSphere portal, as well as Oracle Solutions. Microsoft SharePoint is a consideration in more Gartner portal inquiries — over 70% — than any other vendor.
According to Gartner: The portal market continues to consolidate, with most enterprises focusing on a core set of strategic providers. Yet, emerging demands and technology disruptions are raising the bar for value, as well as opening opportunities for new approaches and new entrants.
The Report Summary said:
The field of viable portal vendors has narrowed considerably, dropping from more than 50 vendors in 2003 to fewer than a dozen in 2010. However, the consolidation of traditional portal vendors doesn't necessarily mean the commoditization of the market. In light of pressing business needs to improve the user experience across channels, and amidst the innovations of Web 2.0 and the cloud, making the right portal choice is more important than ever.
The major technology shifts toward Web 2.0, the cloud and business versus the IT influence are galvanizing the portal market. Portals provide a single, personalized point of access to relevant information, processes and people. They appeal to business leaders as a means to improve employee productivity and collaboration, extend business processes and applications to broader audiences, improve business visibility and responsiveness, engage and serve customers, and improve relationships and efficiency among value chain partners. More importantly than ever, portals appeal to end users overwrought with too many systems to log into and too much information. Enterprise portals unify the user experience, and provide relevancy and context across disparate applications. They provide a unified user experience by spanning across on-premises and cloud boundaries, as well as business and social boundaries. IT organizations need them more than ever to pull together and aggregate disparate information, exert control and ensure compliance, and scale their ability to agilely deliver these applications to the business and users.
Looking forward, the horizontal portal market will serve as an important foundation for the emerging user experience platform (UXP). Organizations are focusing on business-level issues, requiring better engagement of users across a widening range of devices and channels, and new vendors are entering the market with alternative approaches to accomplishing the portal proposition. As portals, user interfaces, and user interaction technologies and practices have proliferated, they have evolved into disconnected stovepipes. Portal products, mashup tools, rich Internet application (RIA) tools, Ajax solutions, Web content management and mobile application development tools all target their respective platforms effectively, but they require enterprise developers to create separate user interaction models and code bases — with few, if any, cross-platform capabilities. Vendors have started to address enterprise concerns with the convergence of these related technologies. The UXP provides integration of technologies used to deliver portals, mashups, RIAs, Ajax-enabled websites, Web content management and mobile applications. This integration can take the form of a set of separate, yet integrated, products (that may or may not be delivered as a suite) or a single product. Early examples of the UXP are largely derived from portal technology, and include Microsoft SharePoint, Oracle WebCenter along with Universal Content Management (UCM), and IBM's broadening WebSphere Portal with its related collaboration and content management portfolio, which is developing toward a more cohesive user experience platform.
The importance of portals and the future of UXP are not lost on vendors; enterprise vendors are using portals to promote their most-sweeping and most-critical agendas. Many of the vendors are using the portal to promote a far broader and deeper agenda, whether it's their developer platforms and tools, content management capabilities, databases and middleware, or enterprise applications. As an inherently cloud-friendly aspect of middleware, portals are also a fundamental vehicle for transitioning customers to the cloud. The portal choice is, therefore, critical to ensure that organizations can accomplish their business goals, while ensuring vendor independence and agility.
Organizations tend to make portal decisions based on a wide range of factors, including functionality, familiarity, price, interoperability, usability, momentum among customers and the IT ecosystem at large. As portals have evolved, basic portal functions, such as user management, personalization, content management and integration, have been extended and enhanced, and new capabilities, such as social computing, analytics and business process management, have been added to respond to subsequent customer demands.
Click here to Read the full, report
Friday, October 01, 2010
As a Microsoft Regional Director – ME , and a co-founder of MS3arab community as well as a Principal Technical Consultant of Compu Pharaohs, have used all my communications along with the support of Compu Pharaohs, and the cooperation with the Rocking MS3arab new community in order to bring the PDC10 first time to Cairo. If you will attend , you will be able to watch the Keynote of Steve Ballmer live. Go and register. Registration is free but Tickets are about to finish up.
Thursday, September 09, 2010
Great Moves in Visual Studio 2010 Team System Licensing, as usual….for the benefit of the customer 2/3
2- TFS Inclusion in all MSDN Subscriptions
"We focus on one end of the spectrum on our large enterprise customers where we offer a rich set of features, integration with other source code integration, back-end management tools, portfolio [tools and more], but our biggest vision at Microsoft is to bring the benefits of ALM to all developers," says Sean McBreen, senior director for Visual Studio and MSDN product management at Microsoft. "In this release we did a lot of things to help bring ALM to the masses. We reduced the price, we included TFS in all of our MSDN subscriptions and we've really focused on simplifying the experience as well."
Early on, those moves seem to be paying off. "It used to be reasonably hard to get, very expensive and reasonably hard to deploy as well," says Ben Day, a Visual Studio ALM MVP and head of Benjamin Day Consulting Inc. "Now that they've made the deployment a lot easier, the licensing is $500 retail and TFS comes with just about every MSDN license that's out there. So Microsoft is trying to make it so that no one has an excuse to go to Subversion or Git or any of those other free open source version control systems.
Since that has changed, I personally see a lot more people who are interested in moving to TFS off of Visual SourceSafe."
"TFS is ultimately going to replace Visual SourceSafe," agrees Gousset. "The fact is, TFS can be used whether you've got one person or whether you've got a shop of 3,000 or 30,000 people."
To be Continued Later……
Wednesday, September 08, 2010
Great Moves in Visual Studio 2010 Team System Licensing, as usual….for the benefit of the customer 3/3
3-Lab Management Inclusion into Visual Studio 2010 Ultimate
Lab Management enables organizations to use virtual labs to optimize the team development process. The goal is to help customers to manage their entire application lifecycle while achieving higher software quality and ROI. Lab Management is critical in realizing this vision. This change will dramatically reduce the adoption friction for Microsoft customers and increase the value of Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional with MSDN. Lab Management in Visual Stud in 2010 effectively democratizes virtual lab management.
Tuesday, September 07, 2010
Q: As a Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional 2010 with MSDN subscriber, where
can I get the Release-to-Web (RTW) version of Lab Management and when can I start using this functionality?
Answer: Active Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional 2010 with MSDN subscribers can
follow these simple steps to get the RTW version of Lab Management
1- Log into MSDN Subscriber Download.
2- Navigate to “Developer Tools” and then click on “Visual Studio 2010 Lab Management Deployment Guide” and
3-follow the instructions from the guidance document to set up Lab Management.
Q: In the SCVMM download details, why are there two hyperlinks? Which version of SCVMM should I download?
Answer: With this change in approach, Microsoft licensing documents are in the process of being updated to allow use of SCVMM
by Visual Studio Test Professional 2010 with MSDN and Visual Studio 2010 Ultimate with MSDN subscribers as part of the
Lab Management functionality. The licensing changes are expected to be in place at the start of October, at which time all
subscribers can download and install the full version of SCVMM available from MSDN Subscriber Downloads. In the interim,
you may choose to evaluate SCVMM using the trial download link provided, or using the full version from MSDN Subscriber
Downloads if your Microsoft Volume Licensing agreement provides evaluation use terms (such as through the Enterprise
Agreement or Select programs). Retail subscribers may have these rights earlier than October.
Q: Does my Visual Studio 2010 Ultimate with MSDN and/or Visual Studio Test Professional 2010 with MSDN subscription
include System Center Virtual Machine Manager 2008 R2 (SCVMM)? What are the usage rights of SCVMM under this
Answer: SCVMM 2008 R2 will be included as part of your Visual Studio 2010 Ultimate or Visual Studio Test Professional 2010
MSDN Subscription. You may use SCVMM 2008 R2 solely for development and testing use rights as described in your Visual
Studio Ultimate with MSDN or Visual Studio Test Professional with MSDN Subscription EULAs. This allows you to use
SCVMM 2008 R2 for creating/configuring/removing virtual machines to use in development and testing scenarios allowed
by these licenses.
Q: What happens if my Ultimate or Test Professional with MSDN subscription lapses – do I lose access to Lab
Management or are the rights perpetual?
Answer: Since Lab Management is now effectively a benefit for Ultimate with MSDN and Test Professional with MSDN subscribers,
the “perpetual” use rights for it are the same as that of the respective MSDN subscription. However, the ability to download
new or updated software version and product keys ends when the MSDN Subscription expires. An expired subscriber can
only use software that was available during the subscription term for the subscription level purchased. See MSDN Licensing
for more details.
Q: Can I use my MSDN Subscription for the operating systems running on the Lab Management guest VM’s? Can I also use my MSDN Subscription for the operating systems hosting the Lab Management VM’s?
Answer: Yes, in both cases, as long as the usage is strictly for development and testing of your applications
Q: Does my SCVMM administrator need Visual Studio 2010 Ultimate with MSDN or Visual Studio Test Professional 2010
with MSDN in order to administer my SCVMM deployment for Lab Management?
Q: How does Lab Management support VMware?
Answer: Today, you can already create environments on the VMware platform and do your testing on those environments using
Visual Studio 2010 testing tools, just like you can create environments that are based on physical machines. However, Lab
Management features such as snapshots and self-service creation of environments are currently only supported on Hyper-V
using SCVMM 2008 R2. We have not made plans to extend the support of these additional features to VMware at this point.
Q. What additional resources exist to help me educate my customers about Lab Management?
Answer: The following resources are available for you today to help customers understand Lab Management and deploy it.
Sunday, September 05, 2010
Great Moves in Visual Studio 2010 Team System Licensing, as usual….for the benefit of the customer 1/3
During the Last 6 Months, Microsoft has released great bulk of ALM Products. This is normal, expected and old news…
I know :)
But during these releases, one shared thing has to be noticed by the customers, which is, How do Microsoft tries to regroup products for the benefit of the customer with a target of less expensive offer with More productive solutions. We can see that at the following points:
1- Integrating DB Professional Features into the Developer Features:
- On Feb 2007 Microsoft has released the DB professional Edition. During this time there was a free Add-On for the Super Mega Suite of Team System which was Team Suite. Every other single user for VSTS had to pay for that as separate version.
-On November 2008, Microsoft has released the DB professional as part of the Team System 2008 Editions.
since this date, Lots of MVPs, Customers, and Partners called for availing these great tools with less expensive schema and easier licensing way.
on March 2010, Microsoft Launched VSTS 2010 and included the DB Professional features as part of the Dev Tools.
To be Continued….
Wednesday, September 01, 2010
These are some Common Q&As about Visual Studio 2010 Lab Management. Hope to be quiet helpful
Q: What is Visual Studio 2010 Lab Management?
Answer: Microsoft’s Visual Studio Lab Management solution extends the existing Visual Studio Application Lifecycle Management (ALM) platform to enable integrated Hyper-V based virtual machine management. Lab Management automates complex build-deploy-test workflows to optimize the build process, decrease risk and accelerate your time to market. Organizations can use it to reduce development and testing costs associated with setup, tear down and restoration of virtual environments to a known state. Lab Management helps to streamline the collaboration between development, Quality Assurance and operations to help organizations achieve higher ROI and realize the benefits of Microsoft’s entire ALM solution. Lab Management also enables testers to file rich bugs with links to environment snapshots which enable developers to quickly debug complex environments.
Q: Who is Lab Management intended for? How will it benefit me?
Answer:: Lab Management is intended for anyone involved in the application development and testing process. Lab Management helps to reduce costs associated with setup, tear down and restoration of complex virtual environments to a known state for build automation, test execution and build deployment. This eliminates waste across the entire application lifecycle by allowing development and QA to work together to effectively optimize the build process and minimize regression testing efforts. Lab Management also enables customers to easily file ‘rich actionable bugs’ with links to environment snapshots that developers can use to recreate the tester’s environments and identify issues. Lab Management enables the automation of build-deploy-test workflows to reduce overall risk and accelerate time to market.
Q: As an inclusion to Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional 2010 with MSDN subscriptions, is Microsoft divesting the Lab Management functionality going into the next release of Visual Studio?
Answer:: No, quite the opposite. This move represents a conscious decision to equip a much larger set of our customers with the ability to use virtual labs to optimize the team development process. Our goal is to help our customers better manage their application development and testing lifecycle while achieve higher software quality and ROI. Visual Studio Lab Management is critical to realizing this vision. Q: Which licenses are required to enable the Lab Management functionality? A: You must have at least one team member with one of the following licenses so that he or she can download required software from MSDN Subscriber Downloads to configure Lab Management: 1)Visual Studio 2010 Ultimate with MSDN, or 2)Visual Studio Test Professional 2010 with MSDN Once Lab Management is configured, any team member with an active MSDN subscription containing the software being used (for example, if the lab is running Windows Server and SQL Server then Visual Studio 2010 Professional with MSDN would be sufficient, but the subscriber would need Visual Studio 2010 Premium with MSDN if the lab uses Microsoft Office SharePoint Server or Microsoft Dynamics software) can leverage the Lab Management infrastructure. For example, team members can enable Build-Deploy-Test workflows through Team Explorer once Lab Management is configured. However, team members still need Microsoft Test Manager to file bugs and debug issues with environment snapshots.
Wednesday, August 25, 2010
Tuesday, August 17, 2010
On Wednesday, August 4th, as part of the VSLive! keynote at 8:30 a.m. Pacific Time, Microsoft announced that
Lab Management will not be sold as a separate product, but instead will be available to Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional with MSDN subscribers. In addition, Microsoft will announce the general availability of Lab Management as “end of August.”
Why does this Change take place? Lab Management enables organizations to use virtual labs to optimize the team development process. The goal is to help customers to manage their entire application lifecycle while achieving higher software quality and ROI. Lab Management is critical in realizing this vision. This change will dramatically reduce the adoption friction for our customers and increase the value of Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional with MSDN. Lab Management in Visual Stud io 2010 effectively democratizes virtual lab management.
Wednesday, January 13, 2010
Last Thursday I have been acknowledged that I was selected to be Microsoft Regional Director for Middle East and Africa. It was one of my most pleasant moments for me during my career life.
I am excited for this opportunity, and I think it will empower my passion to strengthen Microsoft Position into my Region’s Microsoft.
This year we have lots of things to succeed in together, It is not right to unveil it here but surely it will be reported to the Microsoft people :)
Thank you Microsoft.
I would Like to thank my Dear Friends; Goksin Bakir; at Microsoft MEA, and one of the most famous geeks at the region for more than a decade, for his nomination.
Ahmed Adel; Egypt’s DPE Lead as well his key team members, Mohamed Wahby, and Mohamed Nar.
Sunday, January 03, 2010
As I have said couple of days ago at the first part of this article, Power tools for TFS 2010 is there now, you can check the first article for the downloading it.
If you are interested into more details after reading the following you can check Brian Harry Blog.
This release of the Power Tools will only run in a VS 2010 IDE. Most of the features will work against both a TFS 2010 and earlier servers. However a few features will only work against a 2010 server. More on this below when we talk about the individual features. The 2005/2008 Power Tools can still be used with the 2005/2008 VS installs while using a TFS 2010 server. So pick the version of the Power Tools that matches your client environment.
The first step to getting the Power Tools ready for 2010 was removing all of the features that are now built into the 2010 product (or in some way no longer relevant). If you still want to use some of these features against a TFS 2005/2008 server, you will need to use the TFS 2005/TFS2008 Power Tools. For example, the Rollback command has been added to TFS 2010 and removed from the Power Tools. However, the product feature requires new server side support in TFS 2010. If you want to continue to use Rollback against a TFS 2005/2008 server, you will need to use the TFS 2005/2008 Power Tools.
The list of things we’ve moved into the product includes:
- Quick Label – Replaced by the new Team Explorer label dialog.
- Rollback command – Replaced by the new TFS 2010 command line Rollback feature.
- History command – tfpt history /followbranches replaced by new merge tracking features in both the command line and GUI.
- Find Changeset menu – Replaced by built in “Find Changesets…” in 2010
- Support for Client Certificates – Built in to TFS 2010
- Build Notifications – An improved version is now included in Team Explorer 2010
- TFSUsers – Not necessary because TFS 2010 now automatically reacts to Active Directory user name changes.
- DestroyWI Command – Incorporated into witadmin.exe
- DestroyWITD Command – Incorporated into witadmin.exe
- TweakUI Command – Replaced by tf certificates and other 2010 features.
- Destroygl – Incorporated into witadmin.exe
- changedocUrl – Replaced by Configure menu in Office apps
they were able to incorporate so much of the Power Tools capability into the shipping product. The next step was getting the rest of the existing features working against VS/TFS 2010. Here’s the list of features supported in the upcoming Power Tools release and the changes we’ve made:
- Process Template Editor – Our biggest investment has been in the Process Template Editor. Not only did it require a bunch of new features to support all of the new TFS 2010 work item tracking features but the team also invested quite a lot in clean up and bug fixing – we’ve received quite a few bug reports. In all, 80 bugs have been fixed in the Process Template Editor. The new Process Template Editor will not edit process templates associated with older TFS versions. If you need to edit a Process Template for TFS 2005 or TFS 2008, use the TFS 2005 or TFS 2008 Power Tools. The new features include.
- Support for out-of-the-box 2010 versions of MSF for Agile and MSF for CMMI process templates
- Creation and editing of query folders
- Creation and editing of custom link types
- Support for the new work item form controls: Label, enhanced links control, web page and link labels.
- Creation and editing of work item type categories.
- Command Line Interface (tfpt) – No enhancements but other than the removed list above, everything should work.
- Visual Studio Integration – There’s a bunch of miscellaneous IDE features that have been updated to work with VS/TFS 2010 but without feature enhancements. The most prominent are:
- Work Item templates
- Alerts Editor
- Find in Source Control
- Check in Policy Pack – Updated to work with VS 2010 while still allowing policies to be shared with older clients.
- Best Practice Analyzer – Because the architecture of TFS has changed so substantially in this release (AT scale out, DT scale out, Team Project Collections, new “Job Service”, Lab Management, etc we need to completely overhaul the BPA tool. You can think of this release as the first step. The BPA tool now runs against a TFS 2010 server (however you’ll need to use the BPA tool from previous Power Tool releases against previous TFS versions because the new BPA tool won’t run against a TFS 2005 or TFS 2008 server). It now recognized all of the components of a TFS 2010 farm but has very few rules to validate it yet. Expect a big increment of new work on the BPA tool in the next Power Tools update.
- Windows Shell Extension – Updated to work with TFS 2010 but no new features.
- PowerShell Cmdlets – Updated to work with TFS 2010 but no new features.
- MSSCCI Provider – Updated to work with TFS 2010 but no new features.
Truthfully, many of the Power Tools required no updates because the team has maintained pretty good compatibility between 2008 and 2010.