Attn! Always use a VPN when RSSing!
Your IP adress is . Country:
Your ISP blocks content and issues fines based on your location. Hide your IP address with a VPN!
Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Independent Experts. Real World Answers.

older | 1 | .... | 9 | 10 | (Page 11) | 12 | 13 | .... | 40 | newer

    0 0

    Today is Friday, which means it’s time for another MVP Friday Five! MVPs were posting some great content this week and we are excited to bring you a taste of it with five articles written by MVPs. As always, all five posts have great tips and information across a variety of technical expertise.

     

    1. Building an Sencha’s ExtJS 4.0 MVC Application With Microsoft’s ASP.NET MVC3 Series / Basics

    By ASP.Net / IIS: Development MVP Peter Kellner |@PKellner

    This article is the first in a series in which Peter takes the reference application build by the Sencha product team for using Sencha’s MVC pattern running with an ASP.NET 4.0 projects (IIS in production). In this article Peter takes the reference Sencha MVC app and with almost no changes, makes it work with the ASP.NET Visual Studio 2010 project.

     

    2. How to Use PlaySoundAction Behavior in WP7 Application

    By Silverlight: Development MVP Kunal Chowdhury | @kunal2383

    Kunal covers how to use the inbuilt “PlaySoundAction” behavior to add sound effects on button clicks with a demo using a Windows Phone 7 application.  

     

    3. Html5 Windows Azure Dashboard Part 2

    By Windows Azure: Architecture MVP David Pallmann | @davidpallmann  

    This article is part 2 of David’s HTML5- Windows Azure Dashboard experiments with HTML5 cloud dashboards. In this post he moves beyond charts to include media content, including HTML5 video.

     

    4. Video: How to Plan & Manage SharePoint Projects  

    By SharePoint MVP Dux Raymond | @meetdux

    In this video presentation Raymond covers the best ways to manage and plan successful SharePoint projects. 

     

    5. Create Consistent Slides with Layouts

    By PowerPoint MVP Ellen Finkelstein| @EFinkelstein

    Ellen shares her tricks for keeping PowerPoint Slides consistent so that they look great!

     

    We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!

     

     

     

     

     

     


    0 0

    Today's MVP Monday post comes from French Surface: Development MVP Nicolas Calvi and is provided in both French and English.

    Bases de la programmation tactile avec WPF4 et le SDK

    • Gestuelles
    • Programmation tactile avec WPF 4
    • Extension de la programmation avec le SDK Surface 2.0
    • Intégration avec MVVM

    Dans cet article on va aborder quelques approches basiques pour bien débuter avec la programmation tactile sous Windows 7. Que ce soit avec WPF 4 ou avec le SDK Surface 2.0, il faut bien comprendre en quoi ces deux technologies nous servent pour créer des interfaces tactiles intuitives.

     

    Les Gestuelles:

    Avant toute chose, il faut déjà bien comprendre qu’en programmation tactile on ne parle pas de clavier et de souris. Faire du tactile c’est faire des interfaces naturelles (NUI pour Natural User Interface). Dans ce cas, on parle de gestuelles. Cela va de la plus simple avec le contact basique (figure A) jusqu’à des choses plus complexes comme le zoom (figure D et E).

    Dans la figure 1, on peut voir le contact (Figure 1-A), la rotation (Figure 1-B), le déplacement (Figure 1-C) et le zoom (Figure 1-D et 1-E). Ce sont les gestuelles les plus couramment utilisées, elles couvrent une utilisation largement suffisante pour la grande majorité des applications tactiles.

    Il faut donc, quand on réalise une application de ce type, résonner avec ces gestuelles et oublier les interfaces GUI (Graphic User Interface) qu’on utilise habituellement. Fini donc les menus ou les fenêtres modales, on doit penser que c’est le doigt qui contrôle l’interface. Il est important de bien penser nos applications pour que les zones de contacts soient suffisamment grandes, que les objets manipulés soit cohérents et intuitifs. Il est généralement fortement recommandé de faire appel à un Designer Industriel et Interactif afin de réaliser le Design de l’application pour ensuite mettre en image celle-ci avec l’aide d’un graphiste. Ces métiers bien différents ne sont pas à négliger si vous voulez une application cohérente et intuitive.

    Il est donc important de comprendre qu'une application tactile reste une application NUI et doit répondre à des normes en termes d'expérience utilisateur. Le fait de faire une application intuitive et ludique est toujours le fruit d'une profonde réflexion en début de projet. Il ne faut pas perdre de vue qu'un périphérique tactile s'utilise d'une certaine façon et qu'il faut nécessairement revoir le Design d'une application quand on la porte d'une tablette vers une table Microsoft® Surface® 2.0 par exemple.

     

    Programmation avec WPF 4 :

    Pour le développement on utilise WPF 4 sous Visual Studio 2010 qui permet la réalisation d’applications tactiles sous Windows 7. La gestion du tactile fonctionne à première vue comme la gestion de la souris, il suffit de remplacer le pointeur de la souris par un doigt qui fait contact avec une surface tactile. Pour cela, chaque « UIElement » possède une série d’événements sur lesquels on peut se brancher : TouchDown, TouchUp, TouchMove, TouchLeave et TouchEnter. 

    Ces événements s’utilisent comme ceux de la souris, à savoir quand un contact se produit (TouchDown), quand ce contact bouge (TouchMove), quand il disparait de la surface tactile (TouchUp), mais aussi quand il entre ou sort d’un élément graphique (ToucheEnter, TouchLeave). Jusque-là rien de bien compliqué, il suffit sur le callback de l’événement de récupérer dans l’argument les coordonnées du contact pour pouvoir le traiter.

    Ceci est pour l’accès bas niveau des contacts. Si on devait par exemple essayer de savoir si un utilisateur fait un zoom dans notre application, il faudrait donc commencer à créer une classe qui permettrait de gérer cette

    gestuelle : à savoir traquer les contacts sur l’élément, faire un historique de leurs déplacements pour ensuite les analyser et déterminer si la gestuelle a eu lieu. Fort heureusement pour nous, Microsoft nous épargne ce dur labeur en intégrant dans chaque « UIElement », une classe qui permet de scruter les gestuelles de la figure 1.

    Cette classe est la classe « Manipulation ». Chaque « UIElement » possède une instance de cette classe et il suffit de mettre la propriété « IsManipulationEnabled » à vraie pour activer cette fonctionnalité. Une fois ceci fait, on a accès à d’autres événements : ManipulationStarting, ManipulationStarted, ManipulationDelta et ManipulationCompleted.

    Quand des contacts sont détectés (TouchDown) sur l’élément, la manipulation est initialisée et l’événement « ManipulationStarting » est levé. Dans le callback de cet évènement, on va indiquer quelle gestuelle on va suivre (une translation, un zoom, une rotation), quel élément graphique va nous servir de référentiel pour la manipulation ou encore le point de pivot pour la rotation. Une fois ces informations traitées l’événement « ManipulationStarted » est levé pour indiquer que les manipulations sont sous surveillance avec les paramètres indiqués précédemment.

    Une fois cette initialisation terminée, un événement va être levé régulièrement tout au long de la manipulation, il s’agit de « ManipulationDelta ». Celui-ci va nous notifier de tous les changements liés aux gestuelles en cours de reconnaissances. Les informations fournies sont complètes car elles tracent autant le changement depuis le dernier « ManipulationDelta » levé que les changements globaux depuis le début de la manipulation. Le plus intéressant est que si des contacts s’ajoutent ou se retirent pendant la manipulation, ils seront traités et les informations de la manipulation seront mises à jour également.

    Pour finir, quand plus aucun contact ne sera sur l’élément, on considèrera que c’est la fin de la manipulation, l’événement « ManipulationCompleted » sera donc levé. A ce moment-là, il sera possible de gérer de l’inertie avec l’objet manipulé en fonction de sa dernière position. Pour cela, il suffit d’implémenter l’événement « ManipulationInertiaStarting ». Dans celui-ci il suffira de renseigner les « Behaviors » pour le traitement de l’inertie.

    Prenons pour exemple un rectangle dans un « Canvas » : 

    Voici le code pour faire en sorte que si on touche au rectangle il se comporte dans un « ScatterView » (contrôle qui permet de manipuler des objets  naturellement sur une surface tactile).

    Voici donc une première approche des possibilités tactile de WPF 4 sous Windows 7 à savoir la gestion des contacts mais aussi des manipulations les plus courantes. Pour étendre ce modèle, Microsoft a mis à disposition le SDK Surface 2.0 qui ajoute des APIs pour la gestion des contacts, c’est le point que nous allons aborder maintenant.

     

    Programmation avec le SDK Surface 2.0 :

    Tout d’abord, il faut bien comprendre la philosophie de ce SDK que l’on peut résumer par « Write once - touch anywhere ». En effet, comme son nom ne l’indique pas, ce SDK peut être utilisé par tous les périphériques tactiles compatibles Windows 7. C’est une chose importante car tout code écrit avec ce SDK sera portable à l’identique (en terme d’exécution) sur les autres supports compatibles : Tablette, écrans tactile, Microsoft® Surface® 2.0.

    Dans un second temps, ce SDK apporte des contrôles complémentaires pour la gestion des applications tactiles, ces contrôles sont préfixés par « Surface ». Il y a donc des contrôles retravaillés (SurfaceButton, SurfaceScrollViewer, SurfaceListBox, SurfaceWindow, etc.) qui viennent en remplacement des contrôles WPF 4, mais aussi de nouveaux contrôles (ScatterView, TagVisualizer, etc.) qui traduisent les nouveaux usages liés à ce type de périphérique.

    Dans les faits, le SDK Surface 2.0 va étendre les possibilités de WPF 4. Par exemple, sur les événements de contact (TouchDown, TouchUp, etc.) l’argument contiendra de nouvelles API sous formes d’actions et d’informations. Pour cela, un peu comme pour les extensions « Linq » on doit ajouter à notre classe la référence de l’assembly « Microsoft.Surface.Presentation.Input » ce qui va permettre d’étendre l’une des propriétés de « TouchEventArgs » à savoir le « TouchDevice ».

    Une fois étendu, il sera possible de savoir de quoi est capable le périphérique tactile. En effet un écran tactile simple (qui ne peut reconnaitre qu’un seul contact) n’a pas les mêmes possibilités qu’une table Microsoft® Surface® 2.0 (reconnaissance des tags, orientation des contacts). Par exemple, la nouvelle classe « InteractiveSurface.PrimarySurfaceDevice » permet de connaître ces fameuses capacités :

    IsFingerRecognitionSupported: Permet de savoir si le périphérique est capable d’identifier la différence entre un doigt posé sur celle-ci ou un objet quelconque. La table Microsoft® Surface® 2.0 par exemple en est capable, mais si d’autres périphériques peuvent le faire, ils peuvent le signaler par cette fonction.

    IsTagRecognitionSupported: Permet de savoir si le périphérique à la possibilité de reconnaitre des « Tags » (comme Microsoft® Surface® 2.0).

    IsTiltSupported: Permet de savoir si le périphérique est inclinable (comme Microsoft® Surface® 2.0).

    IsTouchOrientationSupported: Permet de savoir si le périphérique peut tracer l’orientation d’un contact sur celui-ci (comme Microsoft® Surface® 2.0), à savoir l’angle qu’il forme avec le point zéro de la zone tactile.

    IsTouchBoundsSupported: Permet de savoir si le périphérique peut connaitre la surface de contact (comme Microsoft® Surface® 2.0), c’est-à-dire la forme et l’aire de ce qui touche le périphérique.

    Il suffit juste donc d’interroger cette classe pour savoir si certaines actions sont réalisables. De même, on peut, sur chaque contact, via la classe d’argument des événements de contact (TouchUp, TouchDown, etc.), savoir si le contact est d’un type particulier (doigt, tag, etc.) et en récupérer les informations. Par défaut, il faut tester les capacités avant de les invoquer car votre code peut être exécuté sur des périphériques complétement différents.

    Le développement est ensuite assez similaire par rapport à WPF 4. Il existe cependant des extensions  pour gérer des gestuelles simples comme le « Tap » ou le « Hold » et qui sont fournies dans le SDK de cette façon :

    Cela permet de se brancher facilement sur ces gestuelles courantes, ce que ne permettait pas WPF 4.

    Il faut donc voir ce SDK comme un complément très utile qui fournit tout ce qu’il manquait à WPF4, tout en préparant l’arrivé de la table Microsoft® Surface® 2.0.

     

    Information Importante :

    Il faut savoir qu’avec WPF 4, si l’on active la manipulation sur un élément (« IsManipulationEnabled »), ses enfants ne recevront plus l’événement « TouchUp », ce qui peut être problématique notamment avec le SDK Surface 2.0. Si on place des éléments dans un « SurfaceScrollViewer » par exemple, il n’est plus possible d’intercepter le « TouchUp » dans les éléments qu’il contient, et ce car il implémente la manipulation. De ce fait, le « Behavior » « s:TouchExtensions.TapGesture » ne fonctionnera pas.

     

    Intégration avec le pattern MVVM :

    Une problématique importante est la gestion des gestuelles avec un pattern de type MVVM, à savoir comment lié l’interface (Vue) avec son ViewModel. La solution est très simple : un « Behavior » (ajouter l’assembly « System.Windows.Interactivity »). Pour cela il suffit d’en créer un très simple : 

    La commande étant un mécanisme courant de gestion des informations entre la « View » et le « ViewModel », en créant ce « Behavior », il devient très simple de faire le pont. Dans la méthode « OnAttached », il suffit de se brancher sur les événements de manipulations grâce à la propriété « AssociatedObject ».

    Quand on a fini de traiter la gestuelle, il suffit d’invoquer la commande avec la fonction « ManipulationDetected ». C’est aussi simple que ça. Pour déclarer le « Behavior » sur son objet il suffit de faire comme ceci :

    En conclusion, la programmation tactile via WPF 4 ou le SDK Surface 2.0 est très accessible. Elle repose sur les mêmes fondements que la programmation GUI classique avec l’adaptation des interactions (ici  plus de souris ni de clavier, mais nos doigts). Le but restant, au final, de concevoir les applications pour qu’elles soient intuitives et accessibles.

     

    English Translation:

    Basis of tactile programming with WPF4 and Surface 2.0 SDK

    • Gestures
    • Tactile programming with WPF 4
    • Programing extension with Surface 2.0 SDK
    • Integrating with MVVM

    In this article we will discuss some basic approaches to get started with tactile programming under Windows 7. Whether it is with WPF 4 or Surface SDK 2.0, it is important to understand how these two technologies are used to create intuitive touch interfaces.

    Gestures:

    First of all, we must understand that in touch programming we don’t talk about keyboards, mouse clicks or other interactions with these two devices. Programming in "tactile" is creating natural interfaces (NUI for Natural User Interface). In this case we talk about gestures, this goes from simple contact “tap” (figure A) to more complex things such as zooms (Figure D and E).

    In figure 1, we can see the simple contact named “tap” (Figure 1-A), rotation (Figure 1-B), move (Figure 1-C), zoom in (Figure 1-D), zoom out (Figure 1-E). These gestures are the most commonly used, they are sufficient for the great majority of touch applications.

    Therefore, when you create this type of application you must use those gestures and forget the menus and modal windows usually used on GUI (Graphic User Interface). You must think for finger interactions and not for mouse interactions. It’s important to create big enough contacts areas so that the objects are easily movable with a finger. Objects must be intuitive so that the understanding of the object induces the required gesture. So it is generally recommended to hire an Industrial & Interaction Designer for the concept, gestures and interaction and a Graphic Designer to create the visual (color and layout). These two different skills are determinative if you want to produce an intuitive and consistent application.

    It is important to understand that in the case of touch technology, we are concerned with NUI applications. This leads to an adherence to standards and the inclusion of constraints in terms of user experience. To make an application intuitive and fun, a reflection period at the beginning of the project is fundamental. We must not forget that a touch device is used in a precise way. It is above all, necessary to review the design of an application when one converts it from a tactile tablet to Microsoft Surface 2.0 for instance.

     

    Programming with WPF 4 :

    The basis of this programming uses a WPF 4 project, which allows the developement of touch application on Windows 7. Tactile handling works in the same way as mouse handling, you just need to replace the mouse pointer with a finger on a tactile surface. So each “UIElement” has a set of events to which you can subscribe: TouchDown, TouchUp, TouchMove, TouchLeave and TouchEnter.

    These events behave like mouse events: when a contact occurs (TouchDown), when this contact moves (TouchMove), when it disappears from the tactile surface (TouchUp), also when it enters or leaves a graphical element (TouchEnter, TouchLeave). Nothing to complex here, you just need to get the contact coordinates in the argument of the event callback to handle it.

     

    This is for the low-level contact access. But if, for instance, you want to know if a user is zooming, you would have to create a new class to handle this gesture. This class should look for all contacts on the element, back up and analyze all theirs moves to then find out if the gesture occurred. Fortunately, Microsoft spares us this hard work by building a class in each “UIElement” to examine all the gestures you have seen in figure 1.

    This class is the “Manipulation” class. Each “UIElement” owns an instance of this class and you just need to set the “IsManipulationEnabled” property to true to get this functionality. Once done, you have access to more events: ManipulationStarting, ManipulationStarted, ManipulationDelta and ManipulationCompleted.

    When contacts are detected (TouchDown) on an element, the manipulation is initiated and the event “ManipulationStarting” is raised. In the event callback, you have to tell the object which gesture you are expecting (translation, zoom or rotation), which graphical element is the referential for the manipulation or what is the rotation pivot point. Once that information handled the “ManipulationStarted” event is raised to notify that the manipulation are monitored with the parameter previously set.

    Once this initialization done, the “ManipulationDelta” event is regularly raised during the manipulation. This one will notify every change about currently monitored gestures. The information provided are complete because it provides all changes from the beginning of the manipulation and from the last ManipulationDelta raised. The most interesting is if new contact are made or removed during the manipulation, they are handled and information is updated.

    Finally when no contact remains on the element, the manipulation is considered completed and the “ManipulationCompleted” event is raised. From this moment, it’s possible to handle inertia with the manipulated object depending on its last position. To do so, you just need to handle the “ManipulationInertiaStarting” event. In this handler, you need to give information about the inertia behavior.

    Let’s take a rectangle in a “Canvas” as example:

    Here is the code to make sure that the rectangle behaves like it was in a “ScatterView” (control allowing natural object manipulation on a tactile surface).

    Here is a first approach of WPF 4 tactile possibilities on Windows 7, that is to say contacts but also widely used manipulation handling. To extend this model, Microsoft released the Surface SDK 2.0 which adds APIs for contact handling, that’s the next topic.

     

    Programming with Surface SDK 2.0:

    First of all, you have to understand the SDK philosophy that can be summarized with “Write once – touch anywhere”. Indeed, as its name doesn’t tell, this SDL can be used by all tactile devices Windows 7 compatible. That’s important because all the code written with this SDK can be identically executed on any compatible support: tablet, tactile screen, Microsoft® Surface® 2.0.

    Secondly, this SDK bring complementary controls for tactile application management, those controls are prefixed with “Surface”. There are reworked controls (SurfaceButton, SurfaceScrollViewer, SurfaceListBox, SurfaceWindow, etc.) which replace WPF 4 usual controls, but also new controls (ScatterView, TagVisualizer, etc.) which translate new usages for those devices.

    In facts, Surface SDK 2.0 is extending WPF 4 possibilities. For example, on contact events (TouchDown, TouchUp, etc.), the argument provides new API as actions and information. Like “linq” extensions, you have to add the “Microsoft.Surface.Presentation.Input” referenced assembly to your class. This will extend a “TouchEventArgs” property called “TouchDevice”.

    Once extended, it will be possible to know what the tactile device supports. Indeed a simple tactile screen (which can only recognize one finger) won’t have the same possibilities as a Microsoft® Surface® 2.0 (tag recognition, contact orientation). For example, the new “InteractiveSurface.PrimarySurfaceDevice” class lets you know those capabilities:

    IsFingerRecognitionSupported: Lets you know if the device can make the difference between a finger and any object. The Microsoft® Surface® 2.0 table can do this for example. But if another device can, it can report it with this function. 

    IsTagRecognitionSupported: Lets you know if the device can recognize « Tags » (like Microsoft® Surface® 2.0).

    IsTiltSupported: Lets you know if the device support tilt (like Microsoft® Surface® 2.0).

    IsTouchOrientationSupported: Lets you know if the device can define the contact orientation (like Microsoft® Surface® 2.0), that is to say the angle it forms with the zero point of the touch area.

    IsTouchBoundsSupported: Lets you know if the device can know the contact area surface (like Microsoft® Surface® 2.0), ie the form and area of what touches the device.

    You just need to ask this class to know if some actions are feasible. The same, via the contact event argument class (TouchUp, TouchDown, etc.), you can know for each contact if it’s a particular type (finger, tag, etc.) and get information about it. By default, you have to test every capability before using it because your code can be executed on any device.

    The development is then similar to WPF 4. However, you can use some extensions provided by the SDK to handle simple gestures like “Tap” or “Hold” like that: 

    This lets you handle simple, commonly used gestures, which you couldn’t do with WPF 4.

    So, this SDK can be seen as a useful WPF 4 complement which provides every feature needed while preparing Microsoft® Surface® 2.0 table release.

     

    Important information:

    You need to know that with WPF 4, if the manipulation is enabled on an Element (“IsManipulationEnabled”), its children won’t receive the “TouchUp” event, which can be problematic especially with the Surface SDK 2.0. If you have some element inside a “SurfaceScrollViewer” for example, it’s not possible to catch the “TouchUp” event on those elements, and this because its implements the manipulation. Thus, the “s:TouchExtensions.TapGesture” behavior won’t work.

     

    MVVM pattern integration:

    A big problematic is gesture handling using an MVVM pattern, that is to say, how to link the interface (View) with its ViewModel. The solution is easy: a Behavior (adding “System.Windows.Interactivity” assembly). For that, you just need to create a new simple behavior:

    The mechanism command being a common handler for information between the View and the ViewModel, by creating this Behavior, it becomes easy. In the “OnAttached” method, you need to subscribe to the manipulation events thanks to the “AssociatedObject” property.

    When the gesture is done treated, you just need to invoke the command with the “ManipulationDetected” function. It's that simple. To declare the behavior on its object, you need to do like that:

    To conclude, tactile programming with WPF 4 and Surface SDK 2.0 is really accessible. It remains on the same foundations as classical GUI programming with interaction adaptation (here no more mouse or keyboard, only fingers). The goal remains, ultimately, to design applications so that they are intuitive and accessible.

     Author's Bio

    Nicolas Calvi is a consultant and trainer for Winwise. Winwise is a French company specialized in Microsoft technologies. His fields of expertise are the natural interfaces such as Microsoft® Surfaces® or Kinect® and the multidisciplinary Agile methodologies. He brings his expertise to companies in order to create rich intuitive interfaces. For this, he places the user in the center of all the concerns during conception. He shares his experience within his "Black Blog" (http: // blog.nicolascalvi.com) as well as on Twitter via @nicolascalvi.

    Nicolas Calvi est Consultant / Formateur pour Winwise une société Française spécialisé dans les technologies Microsoft.  Ses domaines d’expertises sont les interfaces naturelles comme Microsoft® Surface® ou Kinect® et les méthodologies Agile pluridisciplinaires. Il apporte son expertise aux entreprises pour créer des interfaces riches intuitive et replace l’utilisateur au centre des préoccupations de conception. Il partage son expérience au sein de son « Black Blog » (http://blog.nicolascalvi.com) ainsi que sur Twitter via @nicolascalvi.

     

    MVP Mondays

    The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them.


    0 0

    We caught up with SQL Azure MVP Herve Roggero at the recent PASS Summit in Seattle. We spoke with Herve and Product Manager for SQL Azure, Cihan Biyikoglu, about the relationship between MVPs and Microsoft in the SQL Azure community. Herve also offered to share his thoughts on the value he has found in his first year as an MVP. (Please visit the site to view this video)

    Being an MVP: The Ultimate Community Reward

    This post contributed by SQL Azure MVP Herve Roggero

    It’s been almost a year as of this writing that I have been honored with receiving the SQL Azure MVP Award. As a first timer, it really wasn’t clear to me what being an MVP could bring me. It turns out I was looking at it the wrong way. It isn’t as much what the MVP Award brings me as it is what it allows me to bring to others. I can breakdown my experience in the following categories: individuals, businesses and product involvement.

    Individuals

    This is perhaps the most obvious aspect of becoming an MVP: the community you affect monthly, weekly and sometimes daily. MVPs get involved in various ways. Whether it is running a user group, answering questions on the MSDN Forums, writing books, helping out at SQL Saturdays, speaking at .NET User Group venues, flying to Tennessee to run an Azure Code Camp or even planning a trip to Paris to speak about SQL Azure, all these activities have one thing in common: they provide unique opportunities to help people one on one, have candid conversations about Microsoft technologies and hopefully help individuals achieve greater results with the Microsoft platform. At no charge.

    Businesses

    As an MVP I often reach out to the corporate world, performing various presentations, trainings and guidance. Some of this is done for-hire, but many meetings are an extension of my community work and as a result are performed at no charge. However the most important aspect of working with businesses is to obtain on-the-floor feedback on the realities of what companies are struggling with, in terms of process, people and technology. As a result, this category becomes an important source of information that leads to the third category…

    Product Involvement

    This is perhaps the area that l least expected as a new MVP: being involved in early technical previews and providing feedback to Microsoft on design features, prioritization and even early bits of upcoming features. Above anything else, I consider this the cherry on the cake, a second layer of icing, the ultimate chocolate fondue! I’ve met a lot of SQL Server/SQL Azure team members and provided feedback on early previews of upcoming features. I also met Cihan Biyikoglu (blog: http://blogs.msdn.com/b/cbiyikoglu/) in March while visiting the Microsoft Campus for the MVP Global Summit. Cihan knew that I was building a sharding library for parallel processing of SQL requests. Since Cihan was leading the SQL Azure Federation feature he invited me to participate in the Federation Evaluation Program. Since then I updated my sharding library on codeplex to support Federations (http://enzosqlshard.codeplex.com/)and presented the library at the recent PASS Summit 2011. Cihan and I connected again and made this video announcing the upcoming features of SQL Azure and discussing some of the ways MVPs work with the SQL Azure team.

    Being involved with the product teams completes the circle of the community picture; it is a win-win situation for all parties, from the individuals and businesses seeking advice, to Microsoft obtaining feedback from the field. If you are thinking about becoming an MVP I hope I gave you some motivations to pursue your goal. It is well worth it.

    Author

    Herve Roggero (http://www.herveroggero.com) is co-founder of Pyn Logic (http://www.pynlogic.com) and Blue Syntax Consulting (http://www.bluesyntax.net). Herve’s experience includes software development, architecture, database administration and senior management with both global corporations and startup companies. Over the last 15 years, Herve has worked in the Education, Financial, Health Care, Management Consulting and Database Security sectors. He holds multiple certifications, including an MCDBA, MCSE, MCSD. He also holds an MBA from Indiana University. Herve is heavily involved with the South Florida SQL Server community, speaks at multiple venues, co-authored Pro SQL Azure and runs SQL Saturday events in South Florida. Herve is a SQL Azure MVP.


    0 0

    We are so excited to share today’s MVP Friday Five with you! We have a great line-up of articles from MVPs this week covering events MVPs attended, MVP favorite tools and great MVP tips on keeping your system safe. This is just a small sample of the great tips, insight and information MVPs contribute to the community every day.

     

    1. A Few of My Favorite HTML5 and CSS3 Online Tools

    By Silverlight: Development MVP Dan Wahlin |@DanWahlin

    Dan shares some of his favorite tools that simplify building HTML5/CSS3 sites and increase productivity in the process.

     

    2. Inner Circle, Spent the Night with Windows Phone!

    By Xbox MVP Daylon Furlough | @DeaconMVP

    Daylong shares details (including pictures) from his experience attending Microsoft’s Inner Circle event: Spend the Night with Windows Phone.

     

    3. Workflow and Fiska: SharePoint Observations from Sweden

    By SharePoint Server MVP Dan Holme | @danholme

    Dan shares his thoughts about the events of the week; a couple of observations and tips about SharePoint workflows; and a “soft side” note about his favorite Swedish tradition: fika.

     

    4. 10 Things You Do That Puts Your System at Risk of infection

    By Consumer Security MVP Linda Layton

    Linda shares 10 things you should do to plug the loopholes which malware creators love making use of, and the steps you can take to keep your system safe!

     

    5. Kinect Presentation at Chippewa Valley Code Camp

    By Silverlight MVP Michael Crump | @mbcrump

    Michael shares The Kinect for Windows SDK beta, a starter kit for applications developers that includes APIs, sample code, and drivers.

     

    We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!

     

     

     

     

     

     


    0 0

    Editor's Note: The Following MVP Monday post is by French Forefront: Architecture MVP Lionel Leperlier. This post is also available in English below.

    Introduction

    Lorsque l’on souhaite protéger son serveur Forefront TMG au travers de Microsoft System Center Data Protection Manager (DPM) 2010, l’on applique naturellement les ports requis listé sur l’article officiel suivant : http://technet.microsoft.com/en-us/library/ff399341.aspx. Cependant l’on rencontre l’erreur suivante lorsque l’on tente de rattacher au niveau du serveur DPM 2010 l’agent DPM installé au préalable sur le serveur Forefront TMG (http://technet.microsoft.com/en-us/library/bb870935.aspx) :

    Cette erreur veut simplement dire que des flux sont manquants au niveau de Forefront TMG, nous verrons dans cette article quels sont les différents objets à créer afin de réduire au maximum les ouverture de flux requis pour la protection par le serveur DPM de notre firewall.

    Prérequis

    Afin que le serveur DPM 2010 puisse accéder au fichier au travers des partages administratif il faudra vérifier sur la carte réseau rattachée au réseau interne que les options suivantes soient bien activées :

    • Client for Microsoft Networks
    • File and Printer Sharing for Microsoft Networks

    Protocoles

    Protocoles standard

    Afin de créer les règles d’accès les protocoles suivant devront être créés :

    Attention pour le protocole DPM Dynamic Ports il faudra s’assurer que sur le serveur DPM et Forefront TMG que ces derniers utilisent bien les ports RPC par défaut afin de s’en assurer la ligne de commande netsh int ipv4 show dynamicport tcp devrait renvoyer le résultat suivant :

    Protocols RPC

    Puis le protocole RPC spécifique à DPM suivant sera aussi nécessaire, les interfaces devront être ajoutées manuellement au niveau de l’assistant. De plus lors de l’ajout des différents Universally Unique Identifier (UUID) l’option Publish on a Dynamically Assigned Port devra être sélectionnée.

    Les différents UUID à rajouter dans notre protocole RPC nommé DPM UUID sont les suivants :

    Règles d’accès

    Afin d’autoriser les échanges entre le serveur DPM et notre serveur Forefront TMG 2010 à protéger les deux règles suivantes seront nécessaires, dans le cas présent l’objet DPM Servers est un objet de type Computer Set regroupant la ou les adresses IP des différents serveurs DPM :

    Configuration RPC

    Une fois les règles créées il faut savoir que le filtre RPC utilisés par Forefront TMG ne supporte pas totalement les appels DCOM, ce qui peut résulter à des refus de connexion par ce dernier. Nous allons donc contourner le problème en désactivant l’option Enforce Strict RPC Compliance au niveau de notre serveur Forefront TMG :

    Tout d’abord au niveau de la règle DPM – Inbound en sélectionnant Configure RPC protocol.

    Puis au niveau des règles système de Forefront TMG au niveau du nœud Active Directory qui se trouve dans le groupe Authentication Services.

    Tests et validation

    Après avoir appliqué la configuration au niveau de notre serveur Forefront TMG il est possible d’effectuer les tests suivant depuis le serveur DPM. Ces derniers permettront de vérifier que l’ajout du serveur Forefront TMG à protégé n’échouera plus :

    Attention : certaines de ces commandes ne fonctionnent qu’au travers d’une commande DOS et non sous PowerShell.

    Tout d’abord un ping vers le serveur Forefront TMG ne devrait pas retourner d’erreur.

    Afin de vérifier que l’accès aux partages administratifs est possible la commande net view \\tmg_FQDN devrait renvoyer le résultat suivant :

     

    Puis pour s’assurer que les différents appels RPC soient bien configurés la commande sc \\tmg_FQDN query  renvoie la liste des interfaces RPC en ecoute sur notre serveur Forefront TMG :

     

    Enfin l’on vérifie que les appels WMI fonctionnent avec la commande wmic /node :"TMG_FQDN" OS list brief qui renvoie un résumé d’information sur le système d’exploitation sur lequel se repose notre serveur Forefront TMG :

     

    Une fois tous ces tests passés avec succès le fait de rattacher l’agent DPM installé sur le serveur Forefront TMG ne doit plus renvoyer d’erreur au niveau de la console de gestion DPM, et notre serveur Forefront TMG sera désormais protégé.

    English Translation

    How DPM 2010 Could Protect Forefront TMG 2010 with a Minimum Opening of Feeds

    Introduction

    When we want to protect a Forefront TMG with Microsoft System Center Data Protection Manager (DPM) 2010, we naturally apply the following used ports listed on the following article: http://technet.microsoft.com/en-us/library/ff399341.aspx. However when we try to attach the DPM agent deployed on the Forefront TMG server (http://technet.microsoft.com/en-us/library/bb870935.aspx) the following error occur on the DPM console:

    This error mean that some steps on the Forefront TMG firewall are missing, we will see on the following article th required steps to be sure that the DPM communications to the agent installed on the Forefront TMG work correctly.

    Prerequisites

    To be sure that the DPM 2010 server could access to the administrative shares on the properties of the NIC connected to the internal network, the following options must be activated:

    • Client for Microsoft Networks
    • File and Printer Sharing for Microsoft Networks

    Protocols

    Standard protocols

    The following protocol has to be added to be used on our access rules:

    Note : for the DPM Dynamic Ports protocol we have to be sure that the DPM 2010 and Forefront TMG servers both used the default RPC range, the netsh int ipv4 show dynamicport tcp command line must display the following result:

    RPC protocols

    The specific DPM RPC protocol is also required, and on the RPC protocol wizard the interfaces have to be manually added. In addition when we add the Universally Unique Identifier (UUID) the Publish on a Dynamically Assigned Port option must be selected.

    The following UUID will be added to our custom RPC protocol named DPM UUID:

    Access rules

    In order to allow the communication between the DPM 2010 server and Forefront TMG to protect two access rules are required, here the DPM Servers object is a Computer Set containing the IP addresses of the DPM server(s):

    RPC configuration

    When the access rules are created a last step is required, indeed the RPC filter used by Forefront TMG don’t fully support DCOM call. A workaround is to disable the Enforce Strict RPC Compliance option in Forefront TMG:

    First we will do it on our DPM – Inbound by selecting Configure RPC protocol.

    Then on the System policy of the Forefront TMG on the Active Directory node located on Authentication Services.

    Tests and validation

    After applying the configuration on Forefront TMG it’s possible to test the communications from the DPM servers. These tests will validate that attaching the agent on the DPM console will not fail again:

    Warning: some command works only on the DOS command line and not on PowerShell.

    First of all a ping to Forefront TMG doesn’t raise any errors.

    In order to check the access to the shares we will use the net view \\tmg_FQDN command line <ith the following result:

    Then the RPC call could be verified with the sc \\tmg_FQDN query  command line which returns the RPC interfaces listening on our Forefront TMG server:

    Finally we test the WMI call with the wmic /node :"TMG_FQDN" OS list brief command line which return a short description of the operating system on the Forefront TMG server:

    If all these tests pass without any errors the attachment process of the DPM agent will not fail again on the DPM console, and our Forefront TMG server is now protected. 

    Author's Bio

    Lionel Leperlier has been a Security consultant since 2009 at ALSY division of Orange Business Services. He works on edge protection project with UAG, TMG and DirectAccess, internal networks with FPE, FPSP and FPSMC, and on AD CS and NPS specific needs. He provides community content through his blog (http://security.sakuranohana/) and Twitter (http://twitter.com/liontux).

     

    MVP Mondays

    The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them.


    0 0

    The following post is by NestorPortillo, director of Community and Online Support at Microsoft.

    In the last two months I’ve had the opportunity to attend many of the MVP Open Days around the world, as well as TechEd Brazil. What I saw in every visit is the strong community that MVPs are building among themselves. MVPs are key community leaders in our technical communities; however they are also part of a local MVP community and the MVP global community. And over the years, my personal connection to this community continues to grow with my understanding of its richness and variety. 

    During my visits I saw some interesting scenarios:

    • MVPs finally meeting in person after years of interactions in the forums
    • MVPs from the same city meeting and, by the end of Open Day, planning some local community activities together
    • MVPs helping local subsidiaries to shape major activities in order to ensure successful events
    • MVPs delivering presentations to other MVPs
    • MVPs challenging me about the program benefits, technology gaps and soccer.

    If I were to try and describe all my experiences I would need much more space than this blog, because each one has a great story.

    I’d like to highlight some experiences from my recent trips, though. One of the most memorable was being able to deliver in person 10-Year Commemorative Award rings to two MVPs in Brazil! This was a special moment for me because I started as an MVP lead (relationship manager) in Brazil. My successor was also able to attend the event. During the presentation I thought to myself that these two MVPs have more stories to share than me and the two leads that followed me, because they had been around through all of us. To make the moment unforgettable, their current Brazilian lead surprised all of us with a collage of pictures he had prepared showcasing these two veteran MVPs. The presentation was great fun—he asked the entire MVP audience what the photos had in common and it took us five or six pictures before we realized it was a tribute to these two MVPs. I was pleased to be there and be part of this recognition. 

    During the Argentinean MVP Open day, I met a new generation of MVPs. Their passion, drive and challenge to the status quo clearly define them and it is really great to see how technology is the glue that facilitates the interaction between them and the old guard. I think technology always will be generation-and profession-agnostic. 

    I also had the opportunity to attend the MVP Open Day in Japan. Years ago, the first time I met MVPs in Japan, they asked me what I was looking forward to doing after the Open Day and I answered that I wanted to visit the Tokyo Tower and try to have a ride on the Shinkansen (high speed train). They were surprised and asked me, why Tokyo tower? I said because my super hero Ultraman always saves the Tokyo Tower from big monsters that attack earth. During my recent trip a Japanese MVP saw a little Ultraman that always travel with me and it brought up memories for both of us about this super hero and my first visit to Japan. 

    This year has been a special one for traveling to various global regions because the program is celebrating 10 years as a formal award in China, Brazil, Argentina, Japan and, I believe, Australia (maybe some veteran MVPs from the region can set me straight). I was thinking about all our veteran MVPs because many of them had the opportunity to be a witness to and part of several product launches and major program transitions. Imagine the opportunity to see the evolution of MS-Dos 6.1 to Windows 7; MS Office 4 to MS Office 2010, SQL 6.5 to SQL 2008, etc.  I want to take this opportunity to express on behalf of Microsoft and the MVP Award our gratitude to veteran and new MVPs for their time, knowledge shared and feedback provided to our product groups, regional offices and the MVP Award team. 

    I really enjoyed each interaction and I’m looking forward to seeing and chatting again with many MVPs in February during the MVP Global Summit.

    Author's Bio

    Nestor oversees community influencers, social media and the Microsoft Most Valuable Professional Award strategy for Microsoft Corp.’s global Customer Service and Support organization. find can find him on twitter at @nportillo


    0 0

    Welcome to another MVP Friday Five. We've rounded up a great collection of articles written by five MVPs from the last couple of weeks. As always, they share their expert knowledge in the form of tips, how-to's and walkthrough's.  We know you'll enjoy this sampling of the contributions MVPs make to the tech community every week!

     

    1. InfoPath Form to Upload an Image to SharePoint (No Code)

    By InfoPath MVP S.Y.M. Wong-A-Ton

    S.Y.M. teaches you how to create an InfoPath form that can upload an image to SharePoint using a web service data connection and rules without code.

     

    2. Office 365 DirSync (x64) Installation Walkthrough

    By Exchange Server MVP Mike Crowley | @MikeTCrowley

    Mike looks under the hood of Microsoft’s new 64-bit version of DirSync.exe to verify that it is not installed or configured differently than its 32-bit predecessor and shares his experiences and insights along the way.

     

    3. Deployment of TCPIP Printer via GPO & GPP

    By Group Policy MVP Tan Chee

    Tan Chee explains how to deploy printers via GPO and GPP to more than 1000 Windows 7 machine under the same Domain

     

    4. Inventory Hyper-V Machine and Virtual Machine Using PowerShell

    By Virtual Machine MVP Yoong Seng Lai | @ericlaiys

    Yoong Seng shares how you can use PowerShell to get some information about Hyper-V Host and VM.

     

    5. Using MVVMLight, ItemsControl, Blend and Behaviors to Make a ‘Heads up Compass’

    By Windows Phone Development: Development MVP Joost van Schaik |@LocalJoost

    Joost shows how to use the technique of combine ItemsControl and behaviors to make a kind of heads up compass. He also sprinkles some ‘how to do things in Blend’ (like adding and configuring behaviors) throughout the article as well.

     

    We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!

     

     

     

     

     

     

     


    0 0

    Editor's Note: The Following MVP Monday post is by PowerPoint MVP Glenna Shaw.

     

    The challenge for every project manager is to keep their project on track, on time and on budget and the best way to accomplish this is to have up to date, reliable information and real time communications.  While Microsoft Project is a great tool for managing large projects, for those of us working on smaller projects of 30 tasks or less, a well-designed Excel spreadsheet combined with PowerPoint can be just as effective.  To that end, I’ve created an Excel Project Plan template that allows you to efficiently estimate time and costs, create the project schedule, monitor the schedule and budget and manage the resources and risks as well as document lessons learned.  The template also includes the graphs to create PowerPoint dashboards for your project team as well as your project client.

    The Project Plan

    Begin by downloading the Excel Project Plan template and opening it in Excel.  Once the spreadsheet is open, enter the Date of the Report in cell B4.  If you’d like the Date of the Report to always be the day you open the file, enter the formula =Today().  To create your project plan, click on the filter drop down for tasks.  Check the box for Select All and click OK to show all the available rows for entering your tasks including blank rows.

     

    Starting with cell A9, enter the tasks for your project and enter the assignees for each task.  To estimate your time and costs, enter (in hours) the Optimistic Estimate (OE), Most Likely Estimate (MLE), and Pessimistic Estimate (PE) and enter the hourly wage for each task.  Enter the Start Date for each task and the number of Workdays you want to allow for completion of each task.  Once you’ve entered all task elements, click the filter drop down for tasks again and uncheck the box for (Blanks) and click OK.  This will hide the blank rows in your project plan.  Then click on the drop down for Start Date and select Sort Oldest to Newest and click OK.

    Finally, you need to adjust the horizontal axis on the Project Schedule Performance chart to accurately display your project schedule.  Right click on the dates at the top of the chart and left click on Format Axis.  In the Axis Options, enter the first day of your project for the Minimum and the last day of your project for the Maximum and click close.

              

    Your project plan is now complete.  By entering the Actual % Complete and the Actual Hours for each task as the project progresses the spreadsheet will automatically calculate the performance of your project on any given day.  It is important that you do not make changes to the other cells on the spreadsheet as these cells contain the industry standard formulas for calculating your project’s schedule and performance.  Only make changes to cells with the light gray background.  It is also important to note that while a task may be on schedule it can also be over budget if it’s taking more hours than estimated and vice versa.  Negative values are displayed in (red).  Days
    ahead are displayed in green.

    Risk Management

    With any project it also important to plan your resources and risks effectively.  To plan for your project risks, click on the Risk worksheet tab at the bottom of the spreadsheet.  Enter your risks, the percentage of probability of the risk happening, the numbers of hours of impact if the risk does occur and your actions to mitigate the risk if it does occur.  The spreadsheet will automatically calculate the risk score showing you the number of hours your project may be impacted.  Once you have all your risks identified, click the drop filter for Risks and uncheck the box for (Blanks) to hide the blank rows.  You’ll note there’s a reminder on this worksheet to remember Reputation Risk.  While we all want to please our clients, there’s always the risk an unhappy client may totally trash you in a variety of venues or in the course of pleasing the client your product is not of a quality that you want associated with your name.  Since this can adversely impact future business it’s important that you acknowledge and plan for this risk.

    Resource Management

    Overloading yourself or a team member is one sure way of placing your project at risk of going over schedule or over budget or both.  The Excel template automatically calculates the percentage of time you’ve assigned to each assignee and provides an easy to use chart to see your resource commitments for the project at a glance.  Click on the HR worksheet tab at the bottom of the spreadsheet.  Do not make any entries in this worksheet.  All values are automatically pulled from your project plan.  The only thing you need to do on this worksheet is adjust your horizontal axis options to the same minimum and maximum settings as you did for the Project Schedule Performance chart in the instructions for the Project Plan.  To see the commitment for a resource, click the drop down filter for Assigned to and uncheck all the boxes except for the resource you want to see.  The chart will automatically show the commitment for that person for the duration of the project.

    Milestones

    The spreadsheet includes a worksheet for you to create a milestones chart especially for your client.  Click on the Milestones worksheet tab at the bottom of the spreadsheet.  Enter your project milestones, start date and number of workdays for each milestone.  Filter out blank rows and sort your milestone table by start date just as you did for the project plan table.  Adjust your horizontal axis options to the same minimum and maximum settings as you did for the Project Schedule Performance chart and the Resource Management chart.  You now have a chart that clearly displays milestones along a timeline.

          

    Holidays

    The project plan spreadsheet automatically accounts for U.S. Holidays through 12/31/2028.  If you do not want a holiday excluded from your project schedule, click on the Holidays worksheet tab at the bottom of the spreadsheet.  Delete the rows for any holidays you want to include as a workday, add rows for excluding additional holidays, etc.

    Communications

    As any good project manager will tell you, effective communications is the most important factor for the success of any project.  At any time you must be able to effectively communicate with all stakeholders of the project including your client and team members.  PowerPoint is the obvious choice for your communications allowing you to easily share relevant information with all parties.  With PowerPoint you can easily use the same presentation to present in person, email a slideshow or post your slides online.  By combining key elements of the project plan spreadsheet with PowerPoint you have an effective communication tool that can be kept up to date with a few clicks.  Open both your Project Plan spreadsheet and a new PowerPoint presentation.  Click New Slide to create a Content Slide in PowerPoint.  Go to Excel, click to select the Project Schedule Performance chart and click Copy on the Home tab.  Go to your PowerPoint slide, click to select the Content Placeholder, click Paste on the Home tab.  This will automatically paste the chart in your PowerPoint.  Click the Paste Options pop-up in the lower right corner of your chart and select Keep Source Formatting and Link Data.  Now your chart is linked to your spreadsheet.  For more about copying and pasting from Excel to PowerPoint, see this article on Office.com.

    Use this method to copy and link the data from the project plan spreadsheet for all the charts you want to include in your presentation.  You can also copy and link the data from any of the tables in your project plan spreadsheet. 

    To automatically update your PowerPoint slides, select any chart on any slide and click File, Info and on the right side of the window at the bottom, click Edit Links to Files.  Change all the links to update Automatic instead of Manual.  Now your PowerPoint will automatically update from any changes made to your project plan spreadsheet.

    Lessons Learned

    A key component of any project is documenting lessons learned.  The project plan spreadsheet includes a method for you to easily record your lessons learned and reference them for your next project.  Click on the Lessons Learned worksheet tab at the bottom of the spreadsheet.  Enter your Lessons Learned, the type (Positive or Negative) and your future plans for each lesson learned.  You can easily see at a glance which lessons learned are positive/negative for future reference.

    Conclusion

    The content of this article is derived from a session at The Presentation Summit titled Every Presentation is a Project.  Project Management is a complex subject to cover in one hour, but by combining a preconfigured Excel template and PowerPoint anyone can manage a project more effectively.  Experiment with the template as you see fit and find all the features that work best for your needs.  Don’t be afraid to make mistakes, you can always download a new copy of the file.  If you’re one of those folks who prefer to manage your projects “on the fly” the project plan template also makes an effective post-mortem tool.  By entering the values after you’ve completed your project you can easily determine how effective your “winging it” strategy works (or not.)

    Author's Bio 

    Glenna Shaw is a Most Valued Professional (MVP) for PowerPoint and the owner of the PPT Magic Web site and the Visualology blog. She is a Project Management Professional (PMP) and holds certificates in Accessible Information Technology, Graphic Design, Cloud Computing and Professional Technical Writing.

     

    MVP Mondays

    The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them.


    0 0

    The 2-day Tech Insights Southeast Asia 2011 kicked off with on November 16th – 17th. This technical community event was led and powered by a group of Southeast Asia MVPs and community influencers from across the globe including Indonesia, Malaysia, Singapore and Sri Lanka. At this two day event speakers (half of which were MVPs) delivered technical sessions and breakout tracks for 238 attendees!

    For two full days, Tech Insights Southeast Asia 2011 brought the technical community a step closer together. Attendees demonstrated strong camaraderie and volunteerism, inspiring and sharing technical expertise with one another! It was a truly open and engaging platform for like-minded individuals to learn and share about the latest Microsoft products and technologies to improve their work and lives.

    Special Thanks to MVPs who have contributed as organizers, speakers, and helpers in one way or another making this a superb event –

    Malaysia MVPs:

    Ervin Loh, Raymond Chou, Patrick Yong, Walter Wong, Chan Ming Man, Poo Chin Loong, Chiu Kiang Phua, Daqing Lee, Jabez Ming-Teik Gan, Kok Chiann, Ngan Seok Chern, Kwan Thean Keong, Lai Yoong Seng, Teh Wei King, Wei Min Chan, Yee Jie Ng

    Singapore MVP:

    Loke Kit Kai

    Sri Lanka MVPs:

    Dinesh Priyankara and PPG Dinesh Asanka


     

    Story Submitted By Clarisse Ng, MVP Program Specialist for Southeast Asia. Clarisse joined the team in late 2010 and has been active with the MVP community for one year. She loves working with the MVPs because these experts are highly inspiring and passionate, who selflessly dedicate their time to share knowledge and help the technical community.

     


    0 0

    This week’s MVP Friday Five is incredibly diverse with MVPs contributing from three different countries from four different expertise. Each of these recently published posts by MVPs includes valuable insight, tips and solutions MVPs are known for.  Enjoy this small sampling of the contributions MVPs make to the tech community every day!

    1. Why Woolworths Homeshop Needs a CRM (And Maybe You Do Too)

    By Dynamics CRM MVP Leon Tribe

    In this post Leon shares his experience home delivery from an Australian supermarket and how the issues could be resolved if this chain implemented a CRM.

     

    2. 31 Days of OData – Day 1 Background of OData

    By Data Platform Development: Architecture MVP Chris Woodruff

    Chris Woodruff covers the Background of OData in this first post of his thirty day series on OData.

     

    3. SSAS: Multiple SQL Queries in ROLAP Mode

    By SQL Server MVP Boyan Penev

    Boyan attempts to illustrate the consequences and offer a solution for the situation when in MOLAP mode, SSAS checks for mismatches during processing, but a partition is in ROLAP storage mode, so you don’t get a notification that anything is wrong.

     

    4. Temporary User Profiles

    By Windows Expert-IT Pro: Architecture MVP Helge Klein

    Helge outlines four common reasons why Windows would issue a temporary user profile.

     

    5. Installing Forefront TMG 2010 SP2 on Enterprise Arrays

    By Forefront MVP Richard Hicks

    Richard walks you through the correct sequence and process for intastalling Service Pack 2 (SP2) for Forefront TMG 20120.

    We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!

     

     

     

     

     

     

     


    0 0

    Editor's Note: The Following MVP Monday post is by French Canadian Visual C# MVP Jerome Laban and is available in both French and English.

    Programmation Asynchrone avec les Reactive Extensions (en attendant async/await)

    De nos jours, avec des applications qui utilisent de plus en plus de services dans le Cloud, ou qui tout simplement exécutent de longues actions que l’utilisateur peut ressentir, il est devenu indispensable de programmer de manière asynchrone.

    Mais nous, les développeurs, nous sentons à l’aise lorsque nous pensons séquentiellement. Nous préférons envoyer une requête ou exécuter une fonction, attendre la réponse, puis la traiter.

    Malheureusement pour nous, il n’est plus justifiable pour une application d’attendre de manière synchrone qu’un appel se termine. Cela parce que l’utilisateur s’attend à ce que son application continue de lui répondre, ou bien qu’il est nécessaire d’effectuer un bon nombre d’opérations simultanément pour obtenir une bonne performance.

    Des Frameworks hautement dépendants de l’interface utilisateur (comme Silverlight ou Silverlight pour Windows Phone) essayent de forcer la main du développeur vers la programmation asynchrone en enlevant les API synchrones. Cela laisse le développeur seul avec les patrons comme Begin/End, ou bien les simples évènements C#. Ces deux patrons ne sont pas flexibles, ne sont pas facilement composables, sont très souvent la cause des fuites mémoire, et sont relativement complexes à utiliser ou pire, à lire.

    C# 5.0 et async/await

    En donnant un coup d’œil rapide à un futur pas si lointain, Microsoft a pris l’importante décision d’augmenter le nouveau framework .NET 4.5 afin d’y inclure des API asynchrones. Plus particulièrement dans le cas de Windows Runtime (WinRT), il s’agit de restreindre certaines de ces API sous la seule forme asynchrone. Ces API sont basées sur la classe Task, et sont soutenues par des éléments présents dans les langages pour faciliter la programmation asynchrone.

    Dans l’implémentation C# 5.0 à venir, le patron async/await tente de gérer ce problème de l’asynchronisme en faisant en sorte que du code asynchrone prenne une apparence synchrone. Cela a pour objectif de rendre la programmation asynchrone plus familière aux développeurs.

    Si l’on prend cet exemple:

    Le code dans GetContentFromDatabase a une apparence synchrone, mais sous le capot, ce code est en fait coupé en deux (ou plus) là où le mot clé await est utilisé.

    Le compilateur applique une technique nommée « sucre syntaxique », qui est utilisée à de nombreuses reprises dans le langage C#. Le code est alors « étendu » vers une forme qui est bien moins lisible, mais qui est considéré comme de la plomberie difficile à écrire (surtout correctement) à chaque fois. Le mot clé using les itérateurs, ou plus récemment LINQ sont de très bons exemples d’utilisation de ce sucre syntaxique.

    En utilisant un bon vieux Thread Pool, le code ressemble plutôt à ceci, une fois le compilateur passé:

    Cet exemple est sensiblement plus complexe, et ne gère pas les exceptions proprement. Mais vous saisissez probablement le concept.

    Développer en Asynchrone dès Aujourd’hui

    Ceci étant, vous ne voudrez ou ne pourrez peut-être pas utiliser C# 5.0 de sitôt. Beaucoup de code utilise toujours .NET 3.5 ou même .NET 2.0, et des fonctionnalités comme async prennent du temps à être déployées sur le terrain. Alors même lorsque le Framework le propose depuis longtemps, une fonctionnalité exceptionnelle comme LINQ (depuis C# 3.0) est toujours en cours d’adoption et n’est pas très utilisée.

    Les Reactive Extensions (Rx pour les intimes) offrent un Framework qui est disponible à partir de .NET 3.5 et offrent une fonctionnalité similaire à C# 5.0, mais propose une approche différente à la programmation asynchrone, plus fonctionnelle. Plus fonctionnel veut dire moins de variables pour maintenir des états, et une manière de programmer plus déclarative.

    Mais ne prenez pas peur. Fonctionnel ne veut pas dire des concepts abstraits qui ne peuvent pas être utilisés par le développeur lambda. Cela veut dire (très grossièrement) que vous serez plus enclins à séparer les rôles en utilisant des fonctions plutôt que des classes.

    Mais regardons du code qui ressemble aux deux précédents exemples :

    Pour l’appelant (le Main), la méthode GetContentFromDatabase se comporte de la même manière qu’une Task .NET 4.5, et l’appel à Subscribe remplace la méthode ContinueWith.

    Cette approche simpliste est parfaite pour un exemple. Jusque ici, vous pourriez toujours choisir d’utiliser l’exemple qui se base the la classe ThreadPool, montré précédemment dans cet article.

    Un mot à propos IObservable

    Un IObservable est communément considéré comme un flot de données qui peut pousser à ses souscripteurs aucune ou plusieurs valeurs, et soit une erreur ou un message de fin. C’est un modèle connu sous le nom de Push permettant d’observer la source sans bloquer de Thread. Ce modèle est opposé au modèle Pull proposé par IEnumerable qui effectue une observation bloquante de la source de données. Une très bonne vidéo avec Erik Meijer explique ces concepts sur Channel 9.

    Pour se synchroniser avec le modèle de fonctionnement des Tasks de .NET 4.5, un IObservable doit fournir au maximum une valeur ou une erreur. C’est exactement ce que propose la méthode Observable.Start.

    Un exemple plus réaliste

    La plupart du temps, les scénarios effectuent plusieurs appels asynchrones de méthodes. Et si ils ne sont pas appelés simultanément puis rassemblés, ils sont effectués les uns après les autres.

    Voici un exemple qui effectue un chainage d’appels :

    L’opérateur SelectMany est un peu étrange lorsque utilisé avec la sémantique d’un IObservable qui se comporte comme une Task. Il peut alors être assimilé à l’opérateur ContinueWith. La méthode GetContentFromDatabase ne pousse qu’une seule valeur, faisant en sorte que la fonction lambda fournie à SelectMany n’est appelée qu’une seule fois.

    Prendre la route Async

    Un coup d’œil rapide à WinRT et la Conférence Build a fait apparaitre une règle très intéressant que Microsoft a appliquée lors de la migration version vers des API asynchrone partout dans le framework. Si un appel d’API prend de manière nominale plus de 50 millisecondes à s’exécuter, alors c’est une API asynchrone.

    Cette règle est très facilement applicable à .NET 3.5 et ultérieurs, en exposant des instances de IObservable qui fournissent au plus une seule valeur, de manière à simuler des Tasks .NET 4.5.

    Du coté architectural, c’est une manière de s’assurer que les consommateurs de l’API d’une couche de service ne seront moins tentés d’appeler les méthodes de manière synchrone. Tout cela dans le but de ne pas impacter la performance perçue ou réelle de l’application.

    Par exemple, un service de "Favoris" implémenté dans une application pourrait ressembler à ceci, en utilisant Rx :

    Toutes les opérations, incluant celle qui altèrent les données, sont exécutées de manière asynchrone. Il est toujours tentant de penser qu’une opération de sélection va prendre du temps, mais il est très facile d’oublier qu’une opération d’ajout peut prendre le même temps.

    Un mot à propos de Unit : Le nom proviens des langages fonctionnels, et représente le mot clé Void, littéralement. Une limitation profonde du CLR de .NET empêche l’utilisation de System.Void comme un paramètre de type générique, et pour pouvoir fournir une valeur de retour Void, Unit a été introduit.

    Conclusion

    Bien plus peut être obtenu grâce à Rx, mais pour commencer, l’utiliser comme un moyen d’effectuer des appels asynchrones de méthodes simples semble être un bon moyen pour apprendre à s’en servir.

    Aussi, pour les experts Rx, des raccourcis ont été pris pour expliquer les concepts dans leur forme la plus simple. Il y a beaucoup de petites techniques à connaitre pour utiliser Rx efficacement, tout particulièrement lorsqu’elles sont utilisées à la grandeur de l’application. L’omission du message Completed est un exemple de ces raccourcis.

    Enfin, expliquer la richesse des Reactive Extensions n’est pas une mince affaire. Même les magiciens de l’équipe de Rx ont aussi du mal… J’espère que cet article vous aidera à plonger dedans !

     

    Enlgish Translation

    Asynchronous Programming with the Reactive Extensions (while waiting for async/await)

    Nowadays, with applications that use more and more services that are in the cloud, or simply perform actions that take a user noticeable time to execute, it has become vital to program in an asynchronous way.

    But we, as developers, feel at home when thinking sequentially. We like to send a request or execute a method, wait for the response, and then process it.

    Unfortunately for us, an application just cannot wait synchronously for a call to end anymore. Reasons can be that the user expects the application to continue responding, or because the application joins the results of multiple operations, and it is necessary to perform all these operations simultaneously for good performance.

    Frameworks that are heavily UI dependent (like Silverlight or Silverlight for Windows Phone) are trying the force the developer's hand into programming asynchronously by removing all synchronous APIs. This leaves the developer alone with either the Begin/End pattern, or the plain old C# events. Both patterns are not flexible, not easily composable, often lead to memory leaks, and are just plain difficult to use or worse, to read.

    C# 5.0 async/await

    Taking a quick look at the not so distant future, Microsoft has taken the bold approach to augment its new .NET 4.5 to include asynchronous APIs and in the case of the Windows Runtime (WinRT), restrict some APIs to be asynchronous only. These are based on the Task class, and are backed by languages to ease asynchronous programming.

    In the upcoming C# 5.0 implementation, the async/await pattern is trying to handle this asynchrony problem by making asynchronous code look synchronous. It makes asynchronous programming more "familiar" to developers.

    If we take this example:

    The code in GetContentFromDatabase looks synchronous, but under the hood, it's actually split in half (or more) where the await keyword is used.

    The compiler is applying a technique used many times in the C# language, known as syntactic sugar. The code is expanded to a form that is less readable, but is more of a plumbing code that is painful to write – and get right – each time. The using statement, iterators and more recently LINQ are very good examples of that syntactic sugar.

    Using a plain old thread pool call, the code actually looks a lot more like this, once the compiler is done:

    This sample somewhat more complex, and does not properly handle exceptions. But you probably get the idea.

    Asynchronous Development now

    Nonetheless, you may not want or will be able to use C# 5.0 soon enough. A lot of people are still using .NET 3.5 or even .NET 2.0, and new features like async will take a while to be deployed in the field. Even when the framework has been offering it for a long time, the awesome LINQ (a C# 3.0 feature) is still being adopted and is not that widely used.

    The Reactive Extensions (Rx for friends) offer a framework that is available from .NET 3.5 and functionality similar to C# 5.0, but provide a different approach to asynchronous programming, more functional. More functional is meaning fewer variables to maintain states, and a more declarative approach to programming.

    But don't be scared. Functional does not mean abstract concepts that are not useful for the mainstream developer. It just means (very roughly) that you're going to be more inclined to separate your concerns using functions instead of classes.

    But let's dive into some code that is similar to the two previous examples:

    From the caller's perspective (the main), the GetContentFromDatabase method behaves almost the same way a .NET 4.5 Task would, and the Subscribe pretty much replaces the ContinueWith method.

    But this simplistic approach works well for an example. At this point, you could still choose to use the basic ThreadPool example shown earlier in this article.

    A word on IObservable

    An IObservable is generally considered as a stream of data that can push to its subscribers zero or more values, and either an error or completion message. This “Push” based model that allows the observation of a data source without blocking a thread. This is opposed to the Pull model provided by IEnumerable, which performs a blocking observation of a data source. A very good video with Erik Meijer explains these concepts on Channel 9.

    To match the .NET 4.5 Task model, an IObservable needs to provide at most one value, or an error, which is what the Observable.Start method is doing.

    A more realistic example

    Most of the time, scenarios include calls to multiple asynchronous methods. And if they're not called at the same time and joined, they're called one after the other.

    Here is an example that does task chaining:

    The SelectMany operator is a bit strange when it comes to the semantics of an IObservable that behaves like a Task. It can then be thought of a ContinueWith operator. The GetContentFromDatabase only pushes one value, meaning that the provided lambda for the SelectMany is only called once.

    Taking the Async route

    A peek at WinRT and the Build conference showed a very interesting rule used by Microsoft when moving to asynchronous API throughout the framework. If an API call nominally takes more than 50ms to execute, then it's an asynchronous API call.

    This rule is easily applicable to existing .NET 3.5 and later frameworks by exposing IObservable instances that provide at most one value, as a way to simulate a .NET 4.5 Task.

    Architecturally speaking, this is a way to enforce that the consumers of a service layer API will be less tempted to synchronously call methods and negatively impact the perceived or actual performance of an application.

    For instance, a "favorites" service implemented in an application could look like this, using Rx:

    All the operations, including ones that alter content, are executed asynchronously. It is always tempting to think a select operation will take time, but we easily forget that an Add operation could easily take the same amount of time.

    A word on unit: The name comes from functional languages, and represents the void keyword, literally. A deep .NET CLR limitation prevents the use of System.Void as a generic type parameter, and to be able to provide a void return value, Unit has been introduced.

    Wrap up

    Much more can be achieved with Rx but for starters, using it as a way to perform asynchronous single method call seems to be a good way to learn it.

    Also, a note to Rx experts, shortcuts have been taken to explain this in the most simple form, and sure there are many tips and tricks to know to use Rx effectively, particularly when it is used all across the board. The omission of the Completed event is one of them.

    Finally, explaining the richness of the Reactive Extensions is a tricky task. Even the smart guys of the Rx team have a hard time doing so... I hope this quick start will help you dive into it!

    Author's Bio

    Jérôme Laban has over 12 years of software development experience and is currently employed as a Software Architect by nventive in Montreal, Canada. He has been working with .NET technologies since the beginning (early 2000) from harden military devices and mobile devices to large enterprise solutions. He has trained new .NET developers at Epitech in Paris for three years. His recent focus is on Windows Phone, C# latest and greatest but also the Reactive Extensions. Jérôme is a Visual C# MVP and he attempts, when the time permits, to write about his findings on his blog at http://jaylee.org/. You can follow Jérôme on twitter at twitter.com/jlaban.

    Jérôme Laban a plus de 12 années d’expérience dans le développement logiciel et travaille pour nventive en tant que Architecte à Montréal, Canada. Il a travaillé avec les technologies .NET depuis leurs début (courant 2000) en passant par des applications pour ordinateurs militaires endurcis et appareils mobiles jusqu’aux larges applications d’entreprise. Il a formé de nouveaux développeurs .NET à Epitech Paris durant trois années. Il se concentre récemment sur Windows Phone, C# et ses dernières nouveautés ainsi que les Reactive Extensions. Jérôme est MVP Visual C# et tente, lorsque le temps lui permet, d’écrire à propos de ses découvertes sur son blog (http://jaylee.org/). Vous pouvez suivre Jérôme par twitter à twitter.com/jlaban.

    MVP Mondays

    The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them

     


    0 0

    We want to celebrate the recent publication of SQL Server MVP Deep Dives, Volume 2 which not only shares the real-world insights of a whopping 64 SQL Server MVPs, it helps deliver healthy smiles to children around the world. 

    The second volume of this highly-regarded book offers expert advice on topics ranging from testing and policy management to integration services, reporting, and performance optimization techniques. 

    Together, the 64 MVPs who wrote this book bring about 1,000 years of experience in SQL Server administration, development, training, and design! 

    Demonstrating their community leadership, the MVP contributors have pledged the proceeds from this book to Operation Smile, an international children's medical charity that heals children's smiles through a mobilized force of medical professionals who provide safe, effective reconstructive surgery for children born with facial deformities such as cleft lip and cleft palate.               

    Thank you to all the MVPs who participated in this initiative for setting such an amazing standard of thoughtful generosity.

     

    Editor's Note- December 9, 2011: We have been notified by a few MVPs that you can actaully purchase SQL Server MVP Deep Dives, Volume   directly from the publisher (here) to maximize the funds that go to charity. Thanks for letting us know!        


    0 0

    Thanks for joining us for another MVP Friday Five. This week we have collected five more great articles written by MVPs including how to’s, insights, feature overviews and a chapter by chapter book synopsis. MVPs contribute to the technology community every day, and our MVP Friday Five series serves up a sampling of these contributions by highlighting articles and blog posts written by MVPs each week. As always, this week’s articles are filled with the expert knowledge we have come to expect from Microsoft Most Valuable Professionals.

     

    1. How To: Automatically Add All Authenticated Users to SharePoint Security Group

    By SharePoint Server MVP Yaroslav Pentsarasky

    Yaroslav shows you how to create a custom security group with the Read permission level and how that group will automatically have All Authenticated Users reserved “user” added to it.

     

    2. The SharePoint 2010 Handbook – Guest Article by MVP John Timney

    By SharePoint Server MVP John Timney | @jtimney

    In this guest post John provides a brief synopsis of the chapters of “The SharePoint 2010 Handbook” which results in a great blow-by-blow overview of several key areas relating to SharePoint 20120.

     

    3. Using the New EWS Password Expiration Operation in Exchange 2010 SP2 in Powershell

    By Exchange Server MVP Glen Scales | @glenscales

    Glen shows you how to make the most of one of the new operations in the Exchange 20120 SP2 released this week: GetPasswordExpiration.

     

    4. Agenda or Table of Content, a Necessity in Presentation?

    By PowerPoint MVP Shawn Toh

    Many people will agree that it is good to have an agenda or table of contents in a presentation.  But are they really necessary? Find out more from PowerPoint MVP Shaw Toh.

     

    5. Powershell Module for Hpyer-V

    By Virtual Machine MVP Kuruwitage Susanta Silva

    In this blog post, MVP Susantha shows you how to install Powershell modules correctly into Windows 2008 R2 server

     

    We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!


    0 0

    Editor's Note: The following MVP Monday post is by French Windows Expert Consumer MVP Michel Martin and is available in both English and French.

    Empty the clipboard with a shortcut

    Windows clipboard is convenient for transfering data of any type within the same application or between applications. You can use the following keyboard shortcuts:

    • Ctrl + C to copy the selected item to the clipboard
    • Ctrl + X to delete the selected item and copy it in the clipboard
    • Ctrl + V to paste the contents of the clipboard into the current application

    Unfortunately, there is no shortcut to clear the clipboard. In this topic, we will see how to create a shortcut icon to do the job.

    Right-click on the desktop, point to New and click Shortcut.

    This action displays the Create Shortcut dialog box. In the Type the location of the item text box, type cmd /c "echo off | clip" and then click Next. Give a name to the shortcut and click Finish.

    Now, you just have to double-click this shortcut to empty the clipboard.

    A video is available for this topic: http://www.mediaforma.com/en/oneminuteaday/windows-7/empty-the-clipboard-with-a-shortcut.html

    Display a list of applications launched at computer startup

    To launch an application when Windows starts, you can use the Startup folder in the Start menu or Windows registry.

    WMIC, a program built into Windows 7, allows you to make a list of applications that runn at startup.

    Click Start, type cmd and click on cmd at the top of the Start menu.

    Type wmic and press the Enter key. The command prompt changes to "wmic:root\cli>".

    Type startup and press Enter. The list of applications that run at startup is immediately displayed.

     A video is available for this topic: http://www.mediaforma.com/en/oneminuteaday/windows-7/display-a-list-of-applications-launched-at-computer-startup.html

    Show file extensions in Windows Explorer

    By default, file extensions are not displayed in Windows Explorer. Yet they are very useful to quickly identify the type of files. Let us see how to enable the display of extensions.

    Click Start then Computer.

    Click Organize and then Folder and search options. This command displays the Folder Options dialog box. Switch to the View tab. Look for the checkbox Hide extensions for known file types. Untick this checkbox and confirm by clicking OK.

    As you can see, extensions are now displayed in Windows Explorer.

    A video is available for this topic: http://www.mediaforma.com/en/oneminuteaday/windows-7/show-file-extensions-in-windows-explorer.html

    What time is it?

    In this topic, you will learn how to ask your computer to tell you the hour … every new hour.

    Start by creating the following file:

    Save it as time.vbs in an easy to find folder: the Documents folder for example.

    Click Start, type Scheduler and click Task Scheduler, at the top of the Start menu. In the right pane of task scheduler, under Actions, click Create Task. Give the name "Time" to the new task. This task should run every new hour. Click Triggers then click New. In the New Trigger dialog box, set the full hour closest to the present time, check Repeat task every, choose 1 hour in the first drop-down list, and Indefinitely in the second. Confirm by clicking OK.

    Switch to the Actions tab and click New. In the New Action dialog box, make sure Start a program is selected in the Action drop-down list. Click Browse, select the time.vbs file created earlier and confirm by clicking OK.

    Click OK to close the Create Task dialog, then close the Task Scheduler window.

    From now on, a voice message indicating the hours will be issued each new hour. 

    A video is available for this topic: http://www.mediaforma.com/en/oneminuteaday/windows-7/what-time-is-it.html

    Play a sound when pressing a toggle key

    If sometimes you accidentally press the Caps Lock, Num Lock or Scroll Lock keys, you can ask Windows to emit beeps when one of these toggle keys is pressed.

    Click Start, type keyboard in the Search text box and click on Change how your keyboard works under Control Panel.

    Under Make it easier to type, tick the Turn on Toggle Keys checkbox and confirm by clicking OK.

    Now, a warning will be emited whenever you press a toggle key.

    A video is available for this topic: http://www.mediaforma.com/en/oneminuteaday/windows-7/play-a-sound-when-pressing-a-toggle-key.html

     

    Original in French

    Petites Astuces Windows 7

     

    Un raccourci pour vider le presse-papiers

    Le presse-papiers de Windows est très pratique pour transférer des données de tout type dans une même application ou entre deux applications. Vous utiliserez les raccourcis-clavier suivants :

    • Ctrl+C pour copier
      l'élément sélectionné dans le presse-papiers
    • Ctrl+X pour supprimer
      l'élément sélectionné et le placer dans le presse-papiers
    • Ctrl+V pour coller le
      contenu du presse-papiers dans l'application en avant-plan

    Malheureusement, il n'existe aucun raccourci pour vider le presse-papiers. Dans cette rubrique, je vous propose de créer une icône de raccourci sur Maquelle il suffira de double-cliquer pour vider le presse-papiers.

    Cliquez du bouton droit sur le Bureau, pointez Nouveau et cliquez sur Raccourci.

    Cette action affiche la boîte de dialogue Créer un raccourci. Dans la zone de texte Entrez l'emplacement de l'élément, tapez cmd /c "echo off | clip" puis cliquez sur Suivant. Donnez un nom au raccourci puis cliquez sur Terminer.

    Le raccourci est immédiatement opérationnel.

    Liste complète des applications lancées au démarrage de l'ordinateur

    Pour lancer une application au démarrage de Windows, vous pouvez utiliser le dossier Démarrage du menu Démarrer ou le Registre. Le programme WMIC, intégré à Windows 7, permet de dresser la liste des applications lancées au démarrage de l'ordinateur. 

    Cliquez sur Démarrer, tapez cmd puis cliquez sur cmd, dans la partie supérieure du menu Démarrer.

    Tapez wmic et appuyez sur la touche Entrée. L'invite de commandes  devient "wmic:root\cli>".

    Tapez startup et appuyez sur la touche Entrée. La liste des applications lancées au démarrage de l'ordinateur est immédiatement affichée.

    Afficher les extensions des fichiers dans l'Explorateur

    Par défaut, les extensions des fichiers ne sont pas affichées dans l'Explorateur Windows. Et pourtant, elles sont bien pratiques pour identifier d'un simple coup d'œil le type des fichiers. Voyons donc comment activer l'affichage des extensions.

    Lancez la commande Ordinateur dans le menu Démarrer.

    Cliquez sur Organiser puis sur Options des dossiers et de recherche. Cette commande affiche la boîte de dialogue Options des dossiers. Basculez sur l'onglet Affichage. Repérez la case Masquer les extensions dont le type est connu. Décochez-la et validez en cliquant sur OK.

    Comme vous pouvez le voir, les extensions des fichiers sont maintenant visibles dans l'Explorateur Windows.

    Message vocal toutes les heures

    Dans cette rubrique, vous allez apprendre à votre ordinateur à prononcer l'heure … toutes les heures pleines.

    Commencez par créer le fichier suivant :

    Sauvegardez-le sous le nom heure.vbs dans un dossier facile à retrouver : le dossier Documents par exemple.

    Cliquez sur Démarrer, tapez planificateur et cliquez sur Planificateur de tâches, dans la partie supérieure du menu Démarrer. Dans la partie droite de la fenêtre du planificateur de tâches, sous Actions, cliquez sur Créer une tâche. Donnez le nom "heure" à cette tâche et cliquez sur Suivant. Cette tâche doit s'exécuter toutes les heures pleines. Cliquez sur Déclencheur puis sur Nouveau. Dans la boîte de dialogue Nouveau déclencheur, définissez l'heure pleine la plus proche de l'heure actuelle, cochez la case Répéter la tâche toutes les, choisissez 1 heure dans la première liste déroulante, et Indéfiniment dans la deuxième. Validez en cliquant sur OK.

    Basculez sur l'onglet Actions et cliquez sur Nouveau. Dans la boîte de dialogue Nouvelle action, assurez-vous que la commande Démarrer un programme est sélectionnée dans la liste déroulante Action. Désignez le programme heure.vbs créé précédemment et validez en cliquant sur OK.

    Fermez la boîte de dialogue Créer une tâche en cliquant sur OK, puis le planificateur de tâches en cliquant sur sa case de fermeture.

    A partir de maintenant, un message vocal précisant l'heure sera émis à chaque changement d'heure.

    Emettre un son lors de l'appui sur une touche bascule

    S'il vous arrive par mégarde d'appuyer sur la touche Verr Maj, Verr Num ou Arrêt Defil, vous pouvez demander à Windows qu'il émette un signal sonore lorsqu'une de ces touches est pressée.

    Cliquez sur Démarrer, tapez clavier dans la zone de texte Rechercher et cliquez sur Modifier le fonctionnement de votre clavier sous Panneau de configuration. Sous Rendre la saisie plus facile, cochez la case Activer les touches bascules et validez en cliquant sur OK. Désormais, un avertissement sonore est émis chaque fois que vous appuyez sur une touche bascule.

     

    Author's Bio

    Michel is an engineer who trained at ESIEA, a French engineering school specializing in computers, electronics and robotics.

    In 1984, he published my first book and found his real vocation. Since then he has written and published numerous (more than 300) books in France, training CD-ROMs in the UK and eBooks (http://www.mediaforma.com/en/michel-martin-books-and-cds.php).

    A few months ago, he started a video series named "One minute a day" http://www.mediaforma.com/en. This will show you how to get the maximum from Windows 7, introducing you to many tips and tricks and best practices about your Operating System.  Michel has been an MVP since 2004.

    Author's Bio in French:

    Mon diplôme de l’ESIEA (Ecole Supérieure d’Electronique, Informatique, Automatique) en poche, j’ai publié mon premier livre en 1984, et j’ai trouvé ma vraie vocation. Depuis lors, j’ai écrit et publié de nombreux livres (plus de 300) en France ainsi que des CD de formation en Angleterre (http://www.mediaforma.com/livres-et-medias/).

    De 1984 à 2011, Microsoft a reconnu mon travail en me donnant le titre de “Most Valuable Professional” pour l'ensemble de mes travaux sur les produits Microsoft.

    Il y a quelques mois, j’ai lancé une formation vidéo sur Windows 7 : “Une minute par jour”. Toutes les vidéos sont disponibles gratuitement sur http://www.mediaforma.com. Venez me rendre visite : je vous montrerai comment obtenir le maximum de votre système Windows 7, en vidéo.

    MVP Mondays

    The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them


    0 0

    We have another great MVP Friday Five for you, offering up a small taste of the contributions MVPs make to the tech community every week. This week’s articles are filled with the tips, how to’s and expert knowledge that MVPs are known for.

     

    1. A T-SQL Tip: Working Calculations

    By SQL Server MVP Rob Farley | @rob_farley

    Rob shows you how to use CROSS APPLY for working columns in calculations using the example of calculating the exact age of a group of football players.

     

    2. Hiding & Disabling Ribbons Items in Project Server, Part II

    By Project MVP Alex Burton | @alexanderb

    Alex takes you through the steps of hiding buttons in the ribbon in Project Server.

     

    3. Tweaking Subtext with Hero Shots Next to Each Post

    By Windows Phone Development MVP Matt Hidinger | @matthidinger

    In this post Matt shows you how you can tweak a skin in VS 2010 to show “hero shots” next to each post. In other words,  when viewing a list of posts (the home page, a specific tag, the archives) this tweak will show an image that helps illustrate the topic and allow for easier scanning with the eye.

     

    4. Prepopulating EPT Custom Fields in Project Server 2010

    By Project: Training MVP Andrew Lavinsky | @Alavinsky

    Andrew answers the question “How do I prepopulate specific fields within an Enterprise Project Type?”

     

    5. Unicode Window Internals

    By Visual C++ MVP YoungJin Shin | @codemaru

    YoungJin describes Unicode Windows for rookie developers to avoid mistakes.

     

    We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!


    0 0

    Editor's Note: The following MVP Monday post is by French-Canadian SharePoint Server MVP Alain Lord and is available in both English and French.

    Introduction

    One of the most discussed topics in SharePoint community is certainly the concept of information architecture. A simple search request in Bing with “SharePoint information architecture” gives us more than 3.4 million hits. It has been demonstrated over and over that the lack of proper information architecture is one of the main failure causes in SharePoint deployment. This article will propose an information architecture approach in a SharePoint context by using mind maps. For this article, the XMind tool has been used but any mind map tool can be used. The idea is to focus on the approach used instead of the tool itself.

    Information Architect competency profile

    In order to be successful, an information architect must possess the following competencies:

    • Negotiation – Political skills – Given that the information architecture may have some political aspects, the information architect must be able to negotiate and acts as a mediator between the various stakeholders
    • Analytical and Technical skills – In order to ensure that the various needs are properly fulfilled by the appropriate SharePoint artefacts, the information architect must understand the technical implications of each option
    • Communicator and Facilitator – These skills are essential especially during the requirements gathering activities. The information architect should be able to influence others, win their confidence, challenge the requirements in a positive way and master the art of compromise

    Even if the information architect is the lead of the Information Architecture process and responsible for the final delivery of the Information Architecture, this activity is first and foremost a collaborative effort between various stakeholders:  Information Architect, SharePoint Architect, one or more Subject Matter Experts (SME) and Business Units representatives.

    Information Architecture Areas

    Most of the current information architecture practices are targeted at site structure, site navigation and labelling. However, other key areas are often neglected but they are essential to ensure a manageable implementation. A complete Information Architecture should cover these Information Areas (IA) as shown in the next figure:

    • Governance
    • Requirements Gathering
    • SharePoint Containment
    • SharePoint Containers
    • Visual Design

    Based on the scope and the extent of the target solution, it is possible that some areas may not be required and/or their level of details will not be the same. For each Information Architecture area, we indicate the stakeholders and the elements that will be covered in each area.

    Figure 1 – Global view of Information Architecture

    As you can see in this map, each Information Architecture area has its own map within a global IA workbook. We can also link specific items to their definition within the workbook. The next set of figures will show some of the key Information Areas maps.

    Governance – It is important to understand that there will be several governance plans based on the scope and the nature of the implementation. We usually have these governance plans:  Collaboration, Document management, Training, Infrastructure, Customization, Social Networking and Strategy. A good starting point for a governance plan can be found here at TechNet site.

    Requirements Gathering – This is the key area of every implementation; the requirements must be challenged to ensure that the proper artefacts will be used. We can also build some prototypes to help us during the requirements gathering activity. Several techniques can be used to gather these requirements. Mind map is a good approach and card sorting technique can also be useful especially for the taxonomy and classification aspects.

    SharePoint Containment – This area is related to the farm architecture and covers core SharePoint artefacts such as Web Application, Site Collection, Service Applications, Servers, Database, Managed Paths, Zones and the entire required configuration for these items. This area is usually completed once the requirements has been captured, analyzed and properly mapped to SharePoint artefacts. It is possible that this zone is already developed; in this situation, the information architect must know the details of the implementation.

    Figure 2 – SharePoint Containment map

    SharePoint Containers – Based on the requirements, best practices and your organization capabilities, we can now determine the type of containers (sites, libraries, lists, web parts, workflows, etc.) and build templates for some of these containers to ensure consistency, promote reusability and ease usability across the whole solution.

    Figure 3 – SharePoint Containers map

    Visual Design – This area aimed to ensure that navigation and branding are properly covered. It covers themes, branding, page layouts, master pages, CSS, etc. In order to assist you in your prototyping phase, there is a free web-based tool called Intranet Modeler. This tool allows you to quickly build and show a prototype based on the initial requirements.

    An Example

    This example shows a subset of Information Architecture areas for a simple solution. The main goal of this solution is to provide a collaborative environment with some basic document management facilities. One of the constraints is the use of SharePoint WSS 3.0 as the technology platform. Given the limited scope of this solution, it was not required to complete every IA areas; the following IA areas performed are: SharePoint Containment, SharePoint Containers and Governance. For this article, we show the SharePoint Containers map. Color code and markers are used to show the various SharePoint artefacts.

    Figure 4 – SharePoint Containers map

    By looking at this mind map, we can already see that:

    • We need five (5) document libraries. Some of them are standard and others will be delivered as templates:
      • Working Documents – A custom document library to manage all the work-in-progress documents
      • Reference – A custom document library to manage reference documents
      • Communications – A custom document library to manage communications items such as presentation, memos, internal notes, etc.
      • Gallery – The standard Picture library to support images used within the site and sub-sites
      • Scripts – A standard document library to manage the various scripts used in other parts of the site and sub-sites.
    • We need three (3) lists templates:
      • Taxonomy – A custom list that will contain the key terms of our taxonomy and their definition
      • Our News  - A basic Announcement list for group news
      • Events – A basic calendar for the group event
    • We need five (5) sites templates:
      • Governance Center – This team site will be used by the governance teams to publish their deliverables (governance plans) and can also act as a reference site for your global SharePoint implementation
      • CollaPedia – A basic Wiki site (or wiki pages library with Foundation) that act as your internal Wikipedia with a strong emphasis on collaboration
      • The Collaborator – A blog site to post various articles about collaboration and to promote discussions and sharing
      • Departmental Site– A basic team site targeted at business units and departments; it is pre-populated with the document libraries and lists templates
      • Project Site – A basic team site targeted at projects; it is pre-populated with the document libraries and lists template
    • We need one (1) web part named Site Administration. This is a basic CEWP used to publish the name of the site owner and site co-owner with mailto hyperlinks on the home page of every single site.

      Our custom libraries are further detailed in a linked map describing our required content types as shown below.

      Figure 5 – Content Types mind map

      This mind map is used to define our content types. We can see that we have a basic Document content type and that other document content types inherit this basic content type. We have also created a Contacts content type with minimal contact information. Some of the key columns are described within another linked map as shown below.

      Figure 6 – Site Columns mind map

      This map shows the various site columns required to support our information architecture. We can also list the value set and the default value is shown in bold.

      Finally, we also have a specific map to show the required site templates as shown below.

      Figure 7 – Site templates mind map

      As you can see, we are reusing all the artefacts that have been previously defined. This ensures consistency, promote reusability and increase the usability of the implementation. If we have fulfilled the notes section of every item, the map can also be used to start the provisioning of the common artefacts such as templates and the global elements such as site columns. By using the Visual Design map, we can then provision the complete site structure.

      Conclusion

      Given that a mind map tool allows us to create relationships between various concepts, the SharePoint information architect can easily:

      • Collect and classify the business needs
      • Start the definition of the farm architecture
      • Identify potential common elements such as content types, managed terms, templates (sites, lists, libraries)
      • Prototype some of the artefacts to ensure that business needs are properly met
      • Start the documentation process of the information architecture through the export function of the mind map tool that allows the creation of document such as PDF or Word

      I hope that you will be able to use some of these concepts in your next Information Architecture exercise. The key message here is to show that the use of a mind map tool can really help you to build a global Information Architecture that will help you to deliver a solid and viable SharePoint solution.

       

      Original Version in French 

      Architecture d’Information dans un contexte SharePoint

      Introduction

      Un des sujets les plus discutés dans la communauté SharePoint est certainement le concept d’architecture d’information. Une simple recherche via Bing en utilisant l’expression “SharePoint information architecture” nous retourne plus de 3.4 millions de résultats. Il a été démontré maintes et maintes fois qu’une architecture d’information inappropriée, ou même l’absence d’architecture d’information, est l’une des causes principales d’échecs dans les projets et implantations SharePoint. Cet article propose une approche d’architecture d’information dans un contexte SharePoint qui est basée sur l’utilisation des cartes heuristiques, mieux connues sous le nom de mind maps. Pour cet article, j’utilise l’outil XMind mais tout outil peut faire l’affaire; l’idée principale étant de considérer l’approche et non pas l’outil en soi.

      Profil de compétences de l’architecte d’information

      Afin de maximiser ses chances de succès, l’architecte d’information devrait posséder les compétences suivantes :

      • Sens politique et Négociation– Étant donné que l’architecture d’information prend parfois une tournure politique, l’architecte d’information doit être en mesure de négocier et d’agir en médiateur entre les divers représentants impliqués autant au niveau technique qu’au niveau affaires
      • Habiletés analytiques et techniques – Afin de s’assurer que les divers besoins sont adéquatement supportés par les bons artefacts SharePoint, l’architecte d’information doit comprendre les implications fonctionnelles et techniques de chaque option et être en mesure d’expliquer les choix proposés
      • Communicateur et facilitateur – Ces habiletés sont essentielles durant la phase de collecte des besoins. L’architecte d’information doit être en mesure d’influencer les autres, de gagner leur confiance, de remettre en question les besoins d’une façon positive et surtout de maîtriser l’art du compromis

      Même si l’architecte d’information est celui qui gère le processus d’architecture d’information et qui est responsable de produire l’architecture d’information, cette activité est d’abord et avant tout un effort de collaboration entre les divers intervenants : l’architecte d’information, l’architecte SharePoint, un ou plusieurs ressources expertes (SME) et un ou des représentants des unités d’affaires impliquées.

      Zones de l’Architecture d’Information

      La majorité des pratiques actuelles en architecture d’information dans un contexte SharePoint sont ciblées vers les éléments physiques tels la structure du site, la navigation et le design graphique. Cependant, d’autres zones clés sont souvent négligées mais elles sont essentielles pour permettre une implantation flexible et gérable. Une architecture d’information complète devrait donc couvrir les zones d’architecture d’information suivantes :

      • Gouvernance
      • Collecte des besoins
      • Hiérarchie du contenu
      • Conteneurs SharePoint
      • Design visuel

      En fonction de la portée et de l’étendue de la solution ciblée, il est possible que certaines de ces zones ne soient pas nécessaires ou que leur niveau de détails soit limité. Pour chaque zone de l’architecture d’information, nous indiquons les intervenants ainsi que les éléments qui doivent être couverts, tel qu’illustré dans la figure suivante.

      Figure 1 – Vue globale – Zones de l’architecture d’information

      Comme on peut le voir dans cette carte heuristique, chaque zone de l’architecture d’information dispose de sa propre carte heuristique à l’intérieur d’une carte globale. On peut aussi créer des liens entre des items spécifiques et leurs définitions à l’intérieur d’une carte. Les figures qui suivent vont illustrer le contenu des cartes de certaines zones de l’architecture d’information.

      Gouvernance – Il est important de comprendre qu’il y aura plusieurs plans de gouvernance en fonction de la portée et de l’étendue de la solution ciblée. On retrouve habituellement les plans de gouvernance suivants: Collaboration, Gestion de documents, Formation, Infrastructure, Personnalisation, Réseau social et Stratégie. Un bon point de part pour un plan de gouvernance se trouve sur TechNet via ce lien.

      Collecte des besoins – C’est la zone d’architecture la plus importante de toute implantation; les besoins doivent être remis en questions pour s’assurer que les bons artéfacts seront utilisés. Par exemple, il faut que l’architecte d’information soit en mesure d’expliquer la différence entre un blogue et un wiki. Il peut être utile à ce stade de construire quelques prototypes pour solidifier et confirmer la compréhension et les besoins. Plusieurs techniques peuvent être utilisées pour faciliter la collecte de besoins. Les cartes heuristiques sont l’une de ces techniques et la technique nommée card sorting peut être aussi très utile pour le volet de taxonomie et de classification de l’information.

      Hiérarchie SharePoint– Cette zone est liée à l’architecture de la ferme et couvre les artéfacts SharePoint tels les Applications Web, les Collections de Sites, les Applications de Services, les Serveurs, les Bases de Données, les zones, etc. ainsi que tout élément de configuration lié à ces artéfacts. On complète habituellement cette zone lorsque tous les besoins ont été collectés, analysés et liés aux divers artéfacts SharePoint. Dans d’autres cas, il se peut que ce travail soit déjà réalisé; l’architecte d’information doit alors en connaître les détails.

      Figure 2 – Carte – Hiérarchie SharePoint

      Structure des contenants SharePoint – En se basant sur les besoins, les meilleures pratiques et les capacités organisationnelles, nous pouvons maintenant définir les types de contenant SharePoint (sites, bibliothèques, listes, web parts, flux de travail, types de contenus, etc.) qui sont nécessaires. On peut aussi bâtir des modèles et gabarits de ces contenants pour assurer une certaine consistance au niveau de l’utilisation,  promouvoir la réutilisation et augmenter le niveau d’usabilité de la solution.

      Figure 3 – Carte – Contenants SharePoint

      Design Visuel – Cette zone vise à s’assurer que la navigation et l’habillage graphique sont couverts adéquatement. Cela inclut donc les thèmes, les éléments ASP comme les pages layout, les master pages, le CSS, etc. Pour faciliter le travail au niveau du prototypage initial d’une solution, il existe un outil Web gratuit nommé Intranet Modeler qui permet de bâtir rapidement et de démontrer un prototype de solution dans une enveloppe visuelle SharePoint 2010.

      Un Exemple

      Cet exemple montre un sous-ensemble d’une architecture d’information pour une solution simple. Le but de cette solution est d’offrir un environnement collaboratif avec quelques fonctionnalités de gestion documentaire. Une des contraintes est l’utilisation de WSS 3.0 comme plateforme technologique. Étant donné la portée limitée de cette solution, il n’a donc pas été nécessaire de compléter chaque zone de l’architecture d’information; les zones suivantes ont été réalisées : Hiérarchie SharePoint (partielle car la ferme existait déjà), Contenants SharePoint et Gouvernance. La figure suivante présente le résultat du travail pour la zone Contenants SharePoint. Un code de couleurs et des marqueurs ont été utilisé pour classifier les différents artéfacts SharePoint.

      Figure 4 – Carte – Contenants SharePoint pour une solution de collaboration

      En regardant cette carte, on peut déjà constater que :

      • Nous avons besoins de cinq (5) bibliothèques de documents. Quelques-unes sont basées les modèles standards de SharePoint et d’autres seront livrées comme gabarits personnalisés :
        • Documents de Travail (Working Documents) – Une bibliothèque personnalisée pour gérer les versions initiales et les versions de travail de tout type de document
        • Reference– Une bibliothèque personnalisée pour gérer les documents de référence qui proviennent de l’extérieur de l’organisation
        • Communications – Une bibliothèque personnalisée pour gérer les éléments de communication comme les présentations, les mémos et notes internes, etc.
        • Galerie (Gallery) – Une bibliothèque standard de type Images pour gérer les images utilisées dans le site et les sous-sites.
        • Scripts – Une bibliothèque standard de documents pour gérer les scripts et autres éléments (fichiers JS, etc.) qui sont utilisés dans le site et les sous-sites
      • Nous avons besoin de trois(3) listes:

        • Taxonomie (Taxonomy) – Une liste personnalisée qui contient les termes clés de notre taxonomie ainsi que la définition de chaque terme. La liste n’a donc que deux colonnes (Titre, Description)
        • Nos Nouvelles (Our News)  - Une liste base sur le modèle de liste Annonces du groupe
        • Évènements (Events) – Une liste de type Calendrier pour gérer les évènements du groupe
      • Nous avons besoin de cinq (5) sites::

        • Centre de Gouvernance (Governance Center) – Ce site d’équipe sera utilise pour les equips de gouvernance afin de gérer et publier les livrables (plans de gouvernance); ce site peut aussi être utilisé comme un site global de référence pour le volet SharePoint dans votre organisation
        • CollaPedia – A site Wiki de base (ou une bibliothèque de pages Wiki avec Foundation)  qui agit comme un Wikipedia interne avec une emphase forte sur la collaboration
        • Le Collaborateur (The Collaborator) – Un site de type Blogue pour publier divers articles sur la collaboration afin de promouvoir le partage et les discussions
        • Site Départemental (Departmental Site)– Un site d’équipe destiné aux unités d’affaires et aux départements de l’organisation; ce site doit être personnalisé en le construisant avec certains éléments réutilisables (bibliothèques de documents, listes)
        • Site de projet (Project Site) – A site d’équipe de base destine aux équipes de projets; ce site doit être personnalisé en le construisant avec certains éléments réutilisables (bibliothèques de documents, listes, etc.)
      • Nous avons besoin d’une (1) Web Part nommé Administration du Site (Site Administration). On utilise une Web Part de type Éditeur de contenu pour publier en page d’accueil, les coordonnées (nom, hyperlien de type mailto, etc.) des propriétaires du site.

      Nos bibliothèques personnalisées sont détaillées dans une carte liée qui décrit les types de contenus requis tel que démontré dans cette figure.

      Figure 5 – Carte – Types de Contenu

      On utilise une carte spécifique pour définir nos types de contenu. On voit ici qu’il y a un type de contenu de base nommé Document-Base et que tous les autres types de contenu document héritent de ce type maître. Nous avons aussi créé un type de contenu Contacts qui représente en fait une version allégée du type de contenu standard de SharePoint. On voit aussi qu’à l’intérieur de nos types de contenu, nous avons certaines colonnes de site qui sont décrites dans une carte liée.

      Figure 6 – Carte – Colonnes de site

      Cette carte montre les diverses colonnes de site requises pour supporter notre architecture d’information. On y détaille aussi les domaines de valeur ainsi que la valeur par défaut qui est visible en gras.

      Finalement, nous avons aussi une carte spécifique qui nous montre les modèles de site requis pour supporter notre architecture d’information.

      Figure 7 – Carte – Modèles de Site

      On constate que nous réutilisons tous les artefacts définis précédemment. Cela permet une consistance au niveau de l’utilisation et favorise grandement la réutilisation. Dans certains outils de cartes heuristiques, on peut utiliser la section Notes de chaque élément pour définir plus précisément ces éléments. L’ensemble des cartes peut alors servir à démarrer l’approvisionnement des artéfacts communs tels les gabarits et les éléments globaux. En utilisant la carte de la zone Design visuel, on peut aussi débuter la structure du site.

      Conclusion

      Étant donné qu’un outil de cartes heuristiques nous permet de créer des relations entre divers concepts, l’architecte d’information peut donc facilement:

      • Collecter et classifier les besoins d’affaires
      • Démarrer la définition de l’architecture de la ferme
      • Identifier rapidement les éléments communs tels les types de contenu, les gabarits (listes, sites, bibliothèques, etc.)
      • Prototyper rapidement certains des artéfacts pour solidifier et confirmer les besoins d’affaires
      • Démarrer le processus de documentation de l’architecture d’information via les facilités d’exportation des outils (création de documents PPT, PDF ou Word)

      J’espère que serez en mesure d’utiliser certains des concepts présentés ici dans votre prochaine architecture d’information. Le message clé ici est de démontrer que l’utilisation d’outil de cartes heuristiques peut vraiment aider l’architecte d’information à livrer une solution SharePoint solide et viable.

      Author’s Bio

      Alain Lord is a Most Valuable Professional (MVP) for SharePoint Server since 2009 and the lead of the Groupe d’Usagers SharePoint Québec, a French-Canadian community of users, developers, architects and managers who share their experience with SharePoint technology within the province of Québec.  He is also on the board of directors for the SharePoint Summit event. He provides community content mostly through the Groupe d’Usagers SharePoint Québec blog  and through their LinkedIn group site. He is an enterprise architect in a large financial company where he leads the various initiatives revolving around collaboration and enterprise content management. His Twitter account is: @djlordee

      Biographie

      Alain Lord est MVP) SharePoint Server depuis 2009 et aussi président et membre fondateur du Groupe d’Usagers SharePoint Québec, une communauté québécoise d’utilisateurs, de développeurs, d’architectes et de gestionnaires qui partagent leurs expériences avec la technologie SharePoint.  Il est aussi sur le comité de direction de l’évènement annuel SharePoint Summit. Il publie du contenu pour la communauté principalement sur le blogue du Groupe d’Usagers SharePoint Québec ainsi que sur le site LinkedIn du groupe. Il est architecte TI dans une grande organisation financière où il réalise des initiatives axées principalement sur la collaboration et la gestion de contenu d’entreprise. Vous pouvez le rejoindre via Twitter : @djlordee

      MVP Mondays

      The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them



       


      0 0

      This week we are presenting a twist on our typical MVP Friday Five. As this year comes to a close we’re taking a look back at some of our top viewed and commented stories for 2011. Whether its Nestor’s story of delivering 10 year commemorative award rings to MVPs in Brazil, advice from MVPs to aspiring MVPs, or the efforts of MVPs to restore communications after the 2011 earthquake and tsunami in Japan, what these stories all have in common is their demonstration of the passion that MVPs have for their communities.

      Visiting MVPs Around the World

      Originally published: November 22, 2011

      In this guest post by Director of Community and Online Support at Microsoft, Nestor Portillo describes his experience attending Open Days around the world and shares some of the highlights from his time with the MVP Community.

       

      MVPs Provide Great Advice During MVP Twitter Chat

      Originally published: October 20, 2011

      We asked MVPs questions about what they’ve experienced as a result of being an MVP, advice someone would give to aspiring MVPs, the best ways to network and more during our October 2011 Twitter Chat. This post offers a sampling of some of the incredible answers MVPs provided.

       

      New Book Brings Together More than a Dozen MVPs

      Originally published: September 9, 2011

      We share details about a collaborative project that brought 15 MVPs together.

       

      With the Help of MVPs, Microsoft Beats Out Apple in Customer Support

      Originally published: May 27, 2011

      We share the results of Business Insider’s head-to-head comparison between Microsoft’s and Apple’s web-based customer support and the important role that MVPs played.

       

      Behind the Scenes in Japan, Windows Azure MVPs Help Drive Vital Communications

      Originally published: April 5, 2011

      In this guest post, Mayumi Susuki describes the efforts of MVPs and others following the Tohoku Earthquake and Tsunami to shore up emergency communications.

       

      MVP Builds Kiosk for the New Microsoft Store

      Originally published: January 4, 2011

      In this guest post by Silverlight MVP David Kelley talks about the on-demand software kiosk that he and his team created for the Bellevue Microsoft retail store and how they worked to create a great user centric experience to gain user adoption.

       

      Check us out on Monday, December 26, 2011 when we highlight the top viewed and commented on MVP Mondays stories from 2011!


      0 0

      Every Monday, MVPs contribute guest posts filled with their expert knowledge to our blog. The result is our most popular series: MVP Mondays.  As the year comes to a close, we wanted to take a look back at some of our top viewed and most commented on stories from 2011. 

       

      MVPs for Windows Phone 7: Quick Tips

      By Windows Phone Development MVP Kevin Wolf | @ByteMaster

      Originally Published: March 14, 2011

       

      MVPs for SharePoint 2010: Office 365 – Enhance Productivity through SharePoint Online & Exchange Online

      By SharePoint Server MVP Razi bin Rais | @razibinrais

      Originally Published: May 9, 2011

       

      MVPs for SharePoint 2010: Modifying Ribbon Fonts and Styles for Publishing Page HTML Field Controls

      By SharePoint Server MVP Becky Bertram | @beckybertram

      Originally Published: May 16, 2011

       

      MVPs for SharePoint 2010: Debugging Techniques for SharePoint Online Applications

      By SharePoint Server MVP Corey Roth |@coreyroth

      Originally Published: May 31, 2011

       

      MVPs for SharePoint 2010: Office 365: SharePoint Online & Instant Extranets

      By SharePoint Server MVP Kris Wagner | @sharepointkris

      Originally Published: June 6, 2011

       

      MVPs for Office 365: SharePoint Designer Workflow Tasks and InfoPath 2010

      By SharePoint Server MVP Laura Rogers | @WonderLaura

      Originally Published: July 18, 2011

       

      MVPs for Microsoft Dynamics: Microsoft Dynamics CRM – Building Consistency into Free Form Text Fields

      By Dynamics CRM MVP Jerry Weinstock | @crminnovation

      Originally Published: August 15, 2011

       

      Using MVC as a REST Service that is Accessed by jQuery/JavaScript

      By ASP.NET/IIS MVP John Petersen | @johnvpetersen

      Originally Published: September 12, 2011

       

      Automated Build-Deploy-Test using TFS 2010

      By Visual Studio ALM MVP Anuj Chaudhary

      Originally Published: October 17, 2011

       

      Thanks to all of our MVP Monday contributors and Happy Holidays from the MVP Award Program Team!

      MVP Monday

      The MVP Monday Series is created by Melissa Travers. In this series we work to provide readers with a guest post from an MVP every Monday. Melissa is a Community Program Manager for Dynamics, Excel, Office 365, Platforms and SharePoint in the United States. She has been working with MVPs since her early days as Microsoft Exchange Support Engineer when MVPs would answer all the questions in the old newsgroups before she could get to them


      0 0

      Thanks for joining us for our final MVP Friday Five of 2011. In today’s post we have five articles that all show you how to make the most of Microsoft technologies. MVPs make many contributions every day to the tech community, and this is a small sampling of their great work. Each of these articles is filled with the expert knowledge that we have come to expect from the MVP community.

       

      1. Enabling Developer Dashboard in SharePoint 2010

      By SharePoint Server MVP Joy Rathnayake| @jrathnayake

      Joy shows us how to use Developer Dashboard in SharePoint 2010 which helps developers to be comfortable when they see an error in the browser.

       

      2.  Loading and Using Custom Dictionaries in PowerPoint 2010

      By PowerPoint MVP
      Geetesh Bajaj | @geetesh

      Geetesh takes you through the steps of loading a custom dictionary to PowerPoint 2010 which will increase the vocabulary of your PowerPoint spellcheck to counter the problem of “misspelled” words that are actually correct.

       

      3. Setting Default Paragraph Spacing in Word 2010

      By Word MVP Herb Tyson |@herbtyson

      Herb takes you through the simple steps to changing the Word 2010 default paragraph spacing.

       

      4. Group Resources for Effective Reports!

      By Project MVP Sam Huffman | @Sam_Huffman

      Sam shares a hot tip that I find useful on every project that utilizes resources. He shows you how, in just four steps, the Resource Sheet view can becomes a powerhouse report showing resource costs by a category defined in the Group field.

       

      5. EF: Why Include Method is an Anti-Pattern IMHO?

      By Data Platform
      Development MVP Matthieu Mezil | @MatthieuMEZIL

      In this four part series Matthieu discusses why Include method is an anti-pattern IMHO

       

      We are always looking for more MVP stories for our Friday Five series. If you’re an MVP and would like your blog posts considered for our MVP Friday Five, please provide your URL in the comments section below or reach out to your MVP Lead!

       

       

       

       

       

       

       


      0 0

      Today 975 exemplary community leaders around the world were notified that they have received the MVP Award—and 144 are new awardees!  These individuals were chosen because they have demonstrated their deep commitment to helping others make the most of their technology, voluntarily sharing their passion and real-world knowledge of Microsoft products with the community.

      While there are more than 100 million social and technical community members, only a small portion are selected to be recognized as MVPs. Each year, around 4,000 MVPs are honored. They are nominated by Microsoft, other community individuals, or in some cases themselves. Candidates are rigorously evaluated for their technical expertise, community leadership, and voluntary community contributions for the previous year. They come from more than 90 countries, speak over 40 different languages, and are awarded in more than 90 Microsoft technologies. Together, they  answer more than 10 million questions a year!

      MVPs are recognized each quarter for this annual award, which continues to grow and evolve to reflect the development of Microsoft technologies. This quarter, MVPs were recognized in the new expertise, Bing Maps Development.

      Congratulations to the new MVPs, and welcome back to renewed MVPs. We are very excited to recognize your amazing accomplishments!

      Please visit our nomination page to nominate a community leader to be considered for an MVP Award.

      Interested in staying connected with us and hearing about some of the exciting things MVPs and the MVP Award Program are doing? Stay connected with us on Twitter, Facebook and YouTube and join the conversation with #mvpbuzz.


    older | 1 | .... | 9 | 10 | (Page 11) | 12 | 13 | .... | 40 | newer