in

mscommunity.net

Interactive mscommunity.net online activities

DamirDobric

srpanj 2009 - Posts

  • About Windows 7 releases, upgrades etc.

    According to this Windows Team Blog posting, Volume License (VL) customers with an existing Software Assurance (SA) license will be able to download Windows 7 RTM in English starting August 7, 2009 via the Volume License Service Center (VLSC). The rest of the languages for Windows 7 RTM should be available within a couple of weeks following the English release. For IT professionals who are not part of the VL program, if you have a TechNet subscription, you will be able to download Windows 7 RTM in English on August 6, 2009, and the remaining languages by October 1, 2009. Evaluation versions of Windows 7 Professional for IT professionals will be made available via the Springboard Series shortly after RTM.

    Unsupported Upgrade Scenarios

    · Upgrades to Windows 7 from the following operating systems are not supported:

    · Windows 95, Windows 98, Windows Millennium Edition, Windows XP, Windows Vista® RTM, Windows Vista Starter, Windows 7 M3, Windows 7 Beta, Windows 7 RC, or Windows 7 IDS

    · Windows NT® Server 4.0, Windows 2000 Server, Windows Server® 2003, Windows Server 2008, or Windows Server 2008 R2

    · Cross-architecture in-place upgrades (for example, x86 to x64) are not supported.

    · Cross-language in-place upgrades (for example, en-us to de-de) are not supported.

    · Cross-SKU upgrades (for example, Windows 7 N to Windows 7 K) are not supported.

    · Upgrades from Windows Vista to Windows N, Windows K, Windows KN, or Windows E are not supported.

    · Cross-build type in-place upgrades (for example, fre to chk) are not supported.

    · Pre-release in-place upgrades across milestones (for example, Windows 7 RC to Windows 7 RTM) are not supported.

     

    Supported Upgrade Scenarios

    From Windows Vista (SP1, SP2)

    Upgrade to Windows 7

    Business

    Professional, Enterprise, Ultimate

    Enterprise

    Enterprise

    Home Basic

    Home Basic, Home Premium, Ultimate

    Home Premium

    Home Premium, Ultimate

    Ultimate

    Ultimate

    From Windows 7

    Upgrade to Windows 7

    Enterprise

    Enterprise

    Home Basic

    Home Basic

    Home Premium

    Home Premium

    Professional

    Professional

    Starter (x86 only)

    Starter (x86)

    Ultimate

    Ultimate

    From Windows 7

    Anytime Upgrade to Windows 7

    Home Basic

    Home Premium, Professional, Ultimate

    Home Premium

    Professional, Ultimate

    Professional

    Ultimate

    Starter

    Home Premium, Professional, Ultimate

  • Command-line proxy generation for SIlverlight 3

    In Silverlight 2 Add Service Reference as part of Visual Studio was the only way to generate proxies for Silverlight clients. 
    Now in Silverlight 3 there is a command-line tool called slsvcutil.exe, which allows customized command-line proxy generation tool called SLSVCUTIL.EXE.

  • Multi-Touch for Silverlight 3 and Windows 7

    For all friends of multi-touch capabilities Silverlight 3 has a build in support for multi-touch.
    However, to support it, your app has to be running on Windows 7. For this reason it will be quite difficult provide interoperable SL-applications for different platforms.
    On the other side, If I design Windows 7 application, in most cases, I would probably think to build it on WPF rather than on SIlverlight. If I need support for multiple platforms then my application cannot rely on features of Windows 7 only.
    So, whatever the future brings on the table, following code demonstrate how you can provide support for multi-touch within Silverligth 3.
    Note, that you have to have devices which support this technology if you want to be able to set the breakpoint inside of handler. If you don’t have them, the code will compile and run.

    using System;
    using System.Collections.Generic;
    using System.Linq;
    using System.Net;
    using System.Windows;
    using System.Windows.Controls;
    using System.Windows.Documents;
    using System.Windows.Input;
    using System.Windows.Media;
    using System.Windows.Media.Animation;
    using System.Windows.Shapes;

    namespace SilverlightApplication2
    {
        public partial class MainPage : UserControl
        {
            public MainPage()
            {
                InitializeComponent();

                Touch.FrameReported +=
                  new TouchFrameEventHandler(Touch_FrameReported);
            }

            void Touch_FrameReported(object sender, TouchFrameEventArgs e)
            {
                TouchPointCollection points = e.GetTouchPoints(null);
                TouchPoint point = e.GetPrimaryTouchPoint(null);

                if (point != null)
                {
                    if (point.Action == TouchAction.Down)
                        e.SuspendMousePromotionUntilTouchUp();

                    Point p = point.Position;

                    switch (point.Action)
                    {
                        case TouchAction.Move:
                           
                            break;

                        case TouchAction.Down:
                          
                            break;

                        case TouchAction.Up:
                          
                            break;

                    }
                }
            }
        }
    }



  • Office 2010

    Microsoft stellt ab sofort einem ausgewählten Benutzerkreis Microsoft Office 2010, Microsoft SharePoint Server 2010, Microsoft Visio 2010 und Microsoft Project 2010 als Technical Preview zur Verfügung. Sie können sich frühzeitig über die Neuerungen und Verbesserungen auf der Office 2010-Website informieren. Nach dem Launch von Exchange 2010 werden Office 2010 und damit verwandte Produkte in der ersten Jahreshälfte 2010 allgemein verfügbar sein.

    Hierzu gehören unter anderem:

    clip_image001

    Office-Webanwendungen von Word, Excel, PowerPoint und OneNote, die Sie mit einem Webbrowser aufrufen. Damit nutzen Sie Ihre Dokumente überall, geräteunabhängig und in stets gleichem Aussehen.

    clip_image001

    Die gemeinsame Texterstellung mit Word, PowerPoint und OneNote.

    clip_image001

    Neue Möglichkeiten für E-Mail-Verwaltung und Kalendereinträge.

    clip_image001

    Innovative Video-, Bildbearbeitungs- und Audiofunktionen von PowerPoint.

    Für mehr Transparenz sorgen die auf fünf reduzierten, nachfolgend aufgelisteten Office 2010-Editionen, die verglichen mit den aktuellen Office-Editionen teilweise zusätzliche Produkte enthalten:

    Für Enterprise-Kunden:

    clip_image001

    Office Standard mit den Produkten Word, PowerPoint, Excel, OneNote, Outlook und Publisher.

    clip_image001

    Office Professional Plus mit zusätzlich: OneNote und SharePoint Workspace.

    Für Endkunden und mittelständische Unternehmen:

    clip_image001

    Office Professional, das Premiumprodukt für den privaten Haushalt und kleine Unternehmen.

    clip_image001

    Office Home and Student mit Word, PowerPoint, Excel, OneNote.

    clip_image001

    NEU ist die Office Home and Business Edition mit Word, PowerPoint, Excel, OneNote und Outlook. Sie ersetzt die Office Small Business Edition.

    Für die Nutzung der Office-Webanwendungen stehen Ihnen und Ihren Kunden drei Wege offen:

    clip_image001

    Kostenfrei mit unserem Windows Live-Angebot, das bereits mehr als 400 Millionen Anwender nutzen.

    clip_image001

    Auf eigenen Servern eines Unternehmens mit jährlicher Zahlungsweise.

    clip_image001

    Im Rahmen der Microsoft Online Services, mit denen Kunden ein Abonnement-Angebot bestellen können.

  • How to Export Word 2007 document to PDF and/or XPS?

    If you are sick of exporting of PDF by using of Print driver you can try this solution. The sample below shows how to export word 2007 document to PDF and.or XPS.
    Please note that prerequisites for this sample are 2007 Microsoft Office Add-in: Microsoft Save as PDF and 2007 Microsoft Office Add-in: Microsoft Save as XPS or booth in once: http://www.microsoft.com/downloads/thankyou.aspx?familyId=4d951911-3e7e-4ae6-b059-a2e79ed87041&displayLang=en (installe Office 2007 and package behind this link before you start with the sample below).
    The sample shown below is based on Word Automation (not Open XML!) and makes  usage of Microsoft Word 12.0 Object Library to access the Word 2007 objects.
    Export is based on method Document.ExportAsFixedFormat method and enumeration WdExportFormat.

     

    /// <summary>
    ///
    Exparts word document to PDF or XPS.
    /// </summary>
    private static void exportWordDoc2Pdf()
    {
                Microsoft.Office.Interop.Word.ApplicationClass word = new Microsoft.Office.Interop.Word.ApplicationClass();

                object fileName =@"Quick Guide.docx";
                object falseValue = false;
                object trueValue = true;
                object missing = Type.Missing;
                word.Visible = true;

                //
                // Loads an existing word document.
                Microsoft.Office.Interop.Word.Document doc =
                word.Documents.Open(ref fileName,
                ref missing, ref trueValue, ref missing, ref missing,
                ref missing, ref missing, ref missing, ref missing,
                ref missing, ref missing, ref missing, ref missing,
                ref missing, ref missing, ref missing);


                // Sets export format. Another possiblity: wdExportFormatXPS
                Microsoft.Office.Interop.Word.WdExportFormat paramExportFormat =
                     
                Microsoft.Office.Interop.Word.WdExportFormat.wdExportFormatPDF;
                bool paramOpenAfterExport = false;
                Microsoft.Office.Interop.Word.WdExportOptimizeFor
                paramExportOptimizeFor =  
               

            Microsoft.Office.Interop.Word.WdExportOptimizeFor.wdExportOptimizeForPrint
            Microsoft.Office.Interop.Word.WdExportRange paramExportRange =
                     
             Microsoft.Office.Interop.Word.WdExportRange.wdExportAllDocument;
                int paramStartPage = 0;
                int paramEndPage = 0;
                Microsoft.Office.Interop.Word.WdExportItem paramExportItem =
                
             Microsoft.Office.Interop.Word.WdExportItem.wdExportDocumentContent;
                bool paramIncludeDocProps = true;
                bool paramKeepIRM = true;
                Microsoft.Office.Interop.Word.WdExportCreateBookmarks
               
    paramCreateBookmarks =  
               Microsoft.Office.Interop.Word.WdExportCreateBookmarks.wdExportCreateWordBookmarks;
                bool paramDocStructureTags = true;
                bool paramBitmapMissingFonts = true;
                bool paramUseISO19005_1 = false;
                string newFileName = "c:\\Temp\\test.pdf";

                //
                // Export the file to PDF.
                doc.ExportAsFixedFormat(newFileName,
              paramExportFormat, paramOpenAfterExport,
              paramExportOptimizeFor, paramExportRange, paramStartPage,
              paramEndPage, paramExportItem, paramIncludeDocProps,
              paramKeepIRM, paramCreateBookmarks, paramDocStructureTags,
              paramBitmapMissingFonts, paramUseISO19005_1,
              ref missing);

                doc.Close(ref missing, ref missing, ref missing);

                doc = null;

                word.Quit(ref missing, ref missing, ref missing);

                GC.Collect();
                GC.WaitForPendingFinalizers();
                GC.Collect();
                GC.WaitForPendingFinalizers();
    }

     

    For more information about this take a look on this MSDN article: http://msdn.microsoft.com/en-us/library/bb412305.aspx

  • Application Evolution with App Server – “Dublin”

    Dublin – upcoming Application Server should fundamentally address two issues by leveraging of existing applications: Scaling and Process visibiliy.
    However, Dublin could slightly change architecture and implementation details of a typical .NET application.
    To understand the idea behind this let’s take a look on typical sales scenario.
    image

    The salesman (second form left) enters the customer data in a web app CRM and web app Biling application.
    Nothing special. To make this a bit better you will have to implement by yourself web services which will talk to
    existing apps as they would be back end. Additionally you will implement some king of fancy front end, which will consume these services.
    This is shown on the next picture.

    image
    In fact such application would have a service( or just an API) which simply call three services as shown below:

    image

    This is much, much better architecture, because it can be endless tuned. For example, if one call fails in this scenario
    the user in front end will be possibly frustrated. To avoid this, you will build now the durable workflow service.
    This service will receive the message and notify the user that the request has been received.
    Then the service (I mean workflow) will behind the scene perform the task shown at the next picture:

    image

    The big picture of the final solution looks like:

    image

    Now it is obvious that durable workflow services visualize big picture and business relevant process steps.
    Considering Scale of the processes we could now implement application which would replace the salesman.

     image
    Last, but not least, here is the probably final architecture picture of Application Server Dublin:

    image

    Material used in this post has been provided by Dan Eshner, who is Product Unit Manager at App Server team.

  • WCF Service:The remote server returned an error: (401) Unauthorized.

     

    By connecting to WCF WebService with configuration shown bellow you may notice that the client could get sometimes in trouble.
    That is the exception can be thrown while invoking of some service operation: The remote server returned an error: (401) Unauthorized.

    <endpoint address="basiccredentialsendpoint"
                    binding="basicHttpBinding"
                    bindingConfiguration="BasicAuthenticationBinding"
                    contract="IService"/>

     

    If authentication settings of the service in IIS looks like shown at the picture below, you will get the error shown above.

    image
    If you for example disable the WindowsAuthentication, the client will authenticate successfully by using of
    Basic-Transport-Authentication.

    image

    However if you enable BasicAuthetication in IIS only but you enable both in WCF
    you will also get an error: InternalServer Error 500: Client found response content type of '', but expected 'text/xml'.

     

    <endpoint address="windowscredentialsendpoint"
                    binding="basicHttpBinding"
                    bindingConfiguration="WindowsCredentialsViaTransport"
                    contract="Eads.AdoTrans.ServiceLayer.ITrackingService"/>

    <endpoint address="basiccredentialsendpoint"
                    binding="basicHttpBinding"
                    bindingConfiguration="BasicAuthenticationBinding"
                    contract="IService"/>
  • Advanced Developers Conference (ADC 09)

    Vom 07.-08. Oktober 2009 ist es soweit, und die Advanced Developers Conference 2009 öffnet in der Beethovenhalle in Bonn ihre Pforten für Sie. Holen Sie sich hier Ihr persönliches Update! An nur zwei Tagen erwarten Sie 2.535 Minuten technologisch besonders tiefgreifender Content, Best Practices, spezielle Tipps und Tricks sowie viel Neues zu Softwarearchitektur, Visual Studio 2010, Windows 7 und Green IT. Top-Sprecher wie Bernd Marquardt, Ralf Westphal, Michael Stal, Christian Nagel, Holger Schwichtenberg oder Neno Loje sowie das elektrobetriebene Hightech-Gefährt „Segway“ sind unter anderem für Sie vor Ort. Sichern Sie sich am besten bereits heute Ihre Teilnahme und seien auch Sie dabei!
    Infos und Anmeldung unter www.ADC09.de

Powered by Community Server (Commercial Edition), by Telligent Systems