Designing an org chart in Edraw Max software. When you finish creating your organizational chart, only one click on the upper tool bar will transfer the image into MS PowerPoint. More PowerPoint Organizational Chart Templates The following PowerPoint organizational chart templates were created in Edraw Max. Click the icons to download them. With more than 6000 built-in vector symbols, drawing could not be easier! Create professional quality organizational charts based on free examples and templates while working in an intuitive and familiar Microsoft Office-style environment. Relative Resource. Office 2010 includes an optional Org Chart module in its installer. You can access it this way: • Close all Office programs. • In Windows, click on the Start button, then on Control Panel. • Select Programs, then Programs and Features. ![]() • Right-click on Microsoft Office 2010 and choose Change. • Select Add or Remove Features, then click on Continue. • Expand the Microsoft PowerPoint section, then click on Organizational Chart Add-in for Microsoft Office programs and choose Run from the computer. • Click on Continue. Allow the process to complete, then restart your computer. You can also create better-looking org charts using SmartArt. In PowerPoint, if you click on File>New, then enter org chart in the Search Office.com for templates field, you'll see a dozen templates from MS. Googling org chart template also reveals many more. Brandwares - Bespoke template services to the graphic design industry and select corporations. Apparently this is a common problem, and the crashing makes chart templates, supposedly a big timesaver, useless. I could empty the chart template folder and add the. Relying heavily volunteers, Non-Profits face unique challenges managing their workforce. OrgChart Platinum includes a prebuilt template for Non-Profit organizations. Here we see a basic organizational layout of a Non Profit organization identifying the Staff and the Volunteers positions that make up the. Use Microsoft Word to create a professional org chart in a matter of minutes with this step-by-step guide. Way to create, update and distribute your organizational chart, Microsoft Word comes equipped with a tool that automatically generates hierarchical diagrams. Most Word templates have three boxes on this branch. The organizational chart of Microsoft displays its 724 main executives including John Thompson, Amy Hood, Jeff Weiner and Preston McAfee. John Korchok, Production Manager [email protected]. ![]()
0 Comments
How to create appointment or meeting template in Outlook? It is no doubt that sometimes you need to repeatedly create appointment or meeting with same subject and body in your calendar folder in Outlook. It is time-consuming to type the same subject and body every time when you create this kind of appointment or meeting. To avoid repeatedly typing, in this article we will show you methods of quickly creating appointment or meeting template in Outlook. With the template of appointment or meeting, create appointment or meeting with same subject and body won’t be a time-consuming job anymore. : 20+ New Advanced Tools for Outlook.: Enable Tabbed Editing and Browsing in Office, Just Like Chrome, Firefox, IE 8/9/10.: Bring Old Menus and Toolbars Back to Office 2007, 2010, 2013 and 2016. Create appointment or meeting template by publishing a form in Outlook In Outlook, you can create and publish a personal form with the detail information of the appointment and meeting. And then use this form as the appointment or meeting template. Please do as follows. Firstly you need to enable the Developer tab in Outlook. If you cannot see the Developer tab showing on the ribbon, please click to show the Developer tab. Shift to the Calendar view and create a new appointment or meeting. In the Appointment or Meeting window, fill in the Subject, Location and body which you need for future use. Then click Developer > Design This Form. See screenshot: 4. Then click Publish > Publish Form under Developer tab. In the Publish Form As dialog box, select Personal Forms Library in the Look In drop-down list; type a name for the form in the Display name box, and finally click the Publish button. ![]() ![]() Microsoft Excel helps you to create schedules. To Do List Template For Excel. To do list template in excel with a reminder software is fairly popular. See screenshot: 6. Then close the Appointment or Meeting window without saving. For using the created form, in the main interface of Outlook 2010 and 2013, please click Developer > Choose Form. In Outlook 2007, click File > New > Choose Form. In the Choose Form dialog box, select Personal Forms Library in the Look In drop-down list, and select the form you want to use, then click the Open button. See screenshot: And your new created template will be opened, you just need to modify the items to your request. Create meeting template by creating quick steps With the Quick Steps function in Outlook, you can easily create meeting template and use it. In Outlook 2010 and 2013, click Create New in the Quick Steps group under Home tab, See screenshot: Note: The Quick Steps feature doesn’t exist in Outlook 2007. In the Edit Quick Step dialog box, select New Meeting in the Choose an Action drop-down list, then click Show Options. See screenshot: Note: You can change the name of quick step in the Name box if you need. Fill in the Subject, Location and Text boxes, then click the Finish button. See screenshot: 4. Now the new quick step is successfully created and shown on the Quick Steps group under Home tab. When you need to create a meeting with those information, please just click this quick step in the Quick Steps group to enable it. 20+ Powerful Tools and Features for Outlook 2010 / 2013 / 2016 / Office 365: Compatible with Outlook 2010 / 2013 / 2016 / Office 365 (32/64); Compatible with Windows XP, Windows Vista, Windows 7 / 8 / 10, Windows Server 2003/2008, Citrix System and Windows Terminal (Remote Desktop) Server; Free trial without feature limitation in 45 days!||. Hi Cory, By template, I am assuming you mean custom form? What should get you up and running would be to publish your custom Appointment form and then associate it to the shared Calendar folder. - Publish the Appointment form to the shared Calendar folder - After publishing the form, right click on shared Calendar and click Properties. Click dropdown next to 'When posting to this folder, use:' and select the custom Appointment form in the list. This will make it so that when a new item is created in the shared Calendar it uses the custom form you've made. Another point to consider is updating the current Appointment items in the shared Calendar to the custom form. You basically just need to change the message class of the existing Appointments to the message class of the new form. Here's an old article that will give you a few methods that can be used. -- OL2002: How to Update Existing Items to Use a New Custom Form One more thing, you'll need to account for users dragging and dropping appointments from their Calendar into the shared Calendar. The Appointments they drag drop will not be updated automatically to the custom Appointment form. If you have additional questions concerns regarding custom Outlook forms, I'd suggest the following: -- How to determine where to publish a custom Outlook form -- Tutorial for Outlook 2003 forms - Sue Mosher's OutlookCode site is fantastic! --Overview of forms in Outlook 2007 Hope that helps! Most new computers today come with Microsoft Works already installed. Although made by Microsoft, Works is a scaled down version Microsoft Office. Works looks and feels different than Office, but it can do many of the same things. The confusing thing is Works Word Processor is NOT the same as Microsoft Word, although it is comparable. Most people don't notice the differences in the Word processor until they run into a situation where they need the full version of Microsoft Word for a project. One of these situations is trying to use the label Templates provided on Avery's web site. If you're not familiar with Avery's site, they provide free templates for you to download and use with their products. But these templates only work with Microsoft Word. NOT Works Word Processor. Good news is that Works has its own label features which allow you to create your labels and then print them onto Avery label sheets. The first step is to create a new database to store your addresses in. You can create different mailing lists (or databases). For example, you can create a list for Christmas cards, and another for book club. Create as many different lists as you'd like. To create a new list, follow the steps below: • Open Works Task Launcher • Click Database to create a new one • Enter information • Save list Once the list is created, you can use it to make address labels. Most people use Avery Template #8160 for their address labels. This gives you 30 labels per sheet. To make labels, follow the steps below. • Open Works Task Launcher • Click Return Address Labels button • Click the Mailing Labels button (last one) and then OK • Select 8160 -Addresses in the box and then click NEW DOCUMENT • Click “ Merge information from another file type”. • Then select database (or list) you’d like to use • Insert appropriate fields being sure to hit ENTER as needed • Close the “insert Fields” window. • Select FILE and then PRINT PREVIEW to check labels before printing (use scroll bar to see top pages. • Click Print when ready. ![]() ![]() ![]() Click inside of the first postcard on the template. Click the 'Insert' menu, select 'Picture' and choose 'Clip Art' to add an image from the Clip Art Gallery, or select 'From File' to add an image from your computer. Jan 14, 2010 How to Make Address Labels using Microsoft. But these templates only work with Microsoft Word. NOT Works Word Processor. Most people use Avery. Microsoft Works Business Card Template windows 7 best price full. Works.Use Avery templates in Word. If you use Avery paper. In Works Suite/Word Processor. Microsoft works business card template - microsoft works word processor templates microsoft works 9 oem. Microsoft works business card template business card. Microsoft works business card template - best of image of avery business card template word business cards. Microsoft works business card template 100. Modifying a Card Template Step Launch Word. Microsoft Word 2013 automatically shows you a list of templates. If you don't see the templates, select 'New' from the File menu. Instead of selecting a blank document, scroll down and select 'Thank You Cards.' May 26, 2010 A wide selection of free Microsoft Office greeting card templates can be found on the web, either via Office Online (where there is an amazingly broad. You can customize this template to create a card for any event. To find a card that you don't have to edit much, type a description, like 'anniversary cards' or 'birthday cards,' in the Search field and then download any free template you wish. Step Click 'Create.' The template opens as a new document. Note that the SmartArt graphic for the Thank You Cards template is on the right and duplicated so you can print it on letter-sized paper, cut it in half and fold two cards. Step Find any image you want to use for the cover in File Explorer. For best results, select an image that is taller than it is wide. ![]() ![]() ![]() Right-click that file and select 'Copy.' Right click the image in the card and select 'Paste.' Because you're pasting the image into a Smart Object, your new image automatically fills the space used by the original image. You can resize the image by dragging the anchors that appear on the border or by clicking the image and then selecting the 'Format' tab under the Picture Tools section. ![]() The Format options include cropping the image, adding a border or adding picture effects. Step Double-click the text below the image and type your own greeting in its place. To change the text formatting, highlight the text and select the 'Format' tab in the SmartArt Tools section. Options include font size, style and color. Step Scroll down to the second SmartArt graphic on the page. Drag the cursor across the entire graphic and press 'Delete' to remove the image, the text and the table containing them. If you're printing only one card, leave the bottom of the page blank to save yourself some printer ink. If you are printing more than one card, select it by pressing 'Ctrl-A' and copy it by pressing 'Ctrl-C.' Click anywhere on the bottom of the page and press 'Ctrl-V' to paste a copy of your graphic below the original. Adding an Inside Message Step Click any blank area at the bottom of the card's page. Click the 'Insert' tab, select 'Pages,' then 'Blank Page.' Use this second page to write a message inside the card. Step Select 'Text Box' from the Insert tab. Note the available text box styles and select any style you want. Drag the text box so it's on the right side of the page and in line with the graphic on the first page. To align the text box more easily, make Word's Ruler visible by clicking the 'View' menu and then clicking the 'Ruler' check box. Step Remove the border from a plain text box by clicking the 'Format' tab under Drawing Tools, selecting 'Shape Outline' and then clicking the 'White' outline color. While the Format tab is open, change the style by selecting 'Quick Styles.' Step Highlight the text in the text box and type your own text in its place. To customize the formatting, highlight the text and then right-click it. From the context menu that opens, you can change the font and color as desired. Step Drag the 'Zoom' slider to the left to take a good look at your card's layout. The text box should be centered beneath the cover graphic. The text box doesn't have to be perfectly centered vertically. In fact, putting it slightly above center will give you room to add a handwritten note and signature below the words. Printing Your Card Step Place a sheet of letter-sized card stock in your printer's manual feed. Putting card stock on a paper tray may jam the printer and ruin the sheet. Step Press 'Ctrl-P' while the greeting card is open in Word. Select your printer and click the 'Print' button. Step Cut the card stock in half along the longest edge. For a straight cut, it's best to use a paper cutter. If you're using scissors, measure and mark each edge with a pencil and ruler, then use the ruler to draw a light, straight line to guide your cut. Step Make a mark at the top and bottom edge of each card using a pencil and ruler. Place the ruler over both marks and then drag a letter opener or butter knife down the middle of the card. This creases the card stock so you can easily fold it. Erase the pencil marks before signing and handing out your homemade card. ![]() Standard operating procedure format is an standard operating procedure template that shows standard operating procedure style and standard operating procedure design in the standard operating procedure example. Standard operating procedure format types When designing standard operating procedure format, it is important to consider standard operating procedure format objectives and format applications as it will determine your standard operating procedure format style and structure. There are different types of procedure format, is a standard operating procedure sample that shows standard operating procedure format and standard operating procedure layout. For example,how to write a standard operating procedure template, free standard operating procedure template, standard operating procedure template free, free standard operating procedure template word 2010,standard operating procedure outline,standard operating procedure word,standard operating procedure example,standard operating procedure format. ![]() Standard operating procedure format There are different types of tools to design your standard operating procedure format, for example, Microsoft Word and Microsoft Excel are common design tools. There are different types of procedure template, is a procedure example that shows procedure format and procedure outline. The following are key steps when designing your standard operating procedure format using Microsoft Word. The first step in standard operating procedure format is to open Microsoft Word and create a new document. After the new Word document is created, You need to consider the standard operating procedure format style such as font size, font type, margin. You may also insert graphical pictures and your business logo etc. The second step in standard operating procedure format design is to create header section. In the section, you need to give basic information such as the purpose and objectives, the notes of using the standard operating procedure format. The third step in your standard operating procedure format is to create the main section. In the main section, you need to consider the standard operating procedure format specifics and building blocks. You may also additional additional blank space for the user to fill out in the future. The last step is to save your standard operating procedure format in Microsoft Word. It is important to save the document as a template file so that you can use the standard operating procedure format in the future. The final functionality of the tool permitted the results of the certification test to be fed into the text-based system security plan. As the certification test was conducted, the minimum security baseline assessment was automatically updated with the results. This set of Microsoft Word-based templates included the risk. This Software Testing Template pack includes 50 MS Word and 27 Excel templates. You can use these templates to save time when creating test forms. ![]() ![]() ![]() Templates Microsoft Excel templates for the tables used in the planning guide are available for. Here's a list of table templates for each section. Whether it is a personal goal, a business goal or an academic goal, you need a game plan to accomplish it successfully. Absence of a strategy can easily allow you to lack motivation and accept defeat. Once you have figured out what you want to do or achieve, a goal setting template will allow you to create a strategy on paper. Setting your goals will be useless if you don’t know what to do with them and how to pursue them. These are fail-proof, straightforward goal setting templates that can help in achieving your goals. Business Goal Setting Template. ![]() ![]() A roundup of the top Microsoft templates for Excel, Word and PowerPoint. Marketing templates, budget planning, invoices, calendars, agendas and more. Microsoft says these are the company's 3 most important goals. This is not your father’s Microsoft. The tech titan has been radically changing its game plan. Aug 30, 2011 I still feel puzzled with this objective on Managing Templates for Word Expert 2007. The objective is that it may include but is not limited to: attaching a. A template to help you document organizational goals & objectives. ![]() File Format • PDF Size: 24.6KB Cover Page versus Cover Letter Some people think that a cover page is the same as a cover letter. They may have the same first word, but their functions are entirely different. A cover page is used as the primary or front most page that holds the title and important details that a writer wants to put in a specific document or writing. On the other hand, a cover letter is a document used for job applications which shows the intent of an applicant to be a part of the company where he or she is applying. It is attached together with an applicant’s resume and usually contain the skills and professional experiences of the applicant, which will benefit his or her target employer. Significance of an Appropriately Made Cover Page A cover page serves as an implication of what the entire document is all about. It draws the attention of the readers. ![]() ![]() ![]() A well-curated cover page lets the common public know that the design being used in its creation is intended for a specific set of readers. It allows them to already decide whether they are a part of that target group and whether they would be of interest to what the document is all about. Aside from cover pages, you can download the and samples from our website. Fax Cover Page Template. File Format • Doc • Docx Size: 50.2KB A Cover Page Format Since a cover page is used in various purposes, it may also vary in terms of formatting. A few uses of a cover page can be seen on the following: • Academic researches and other purposes • Books and other literary pieces • Formal documents Now, the format will depend on how you are supposed to present a document. • If it will be used in the field of education, professors usually provide a format already for the uniformity of all the academic documents to be passed. Design Your Own Cover Page. Microsoft Word templates are a time-saving solution. By buying the products we recommend, you help keep the lights on at MakeUseOf. Featured templates. 3D PowerPoint presentation (Hubble Telescope model) PowerPoint Classroom Timers (Clock) PowerPoint Weekly Meal Planner Excel PivotTable tutorial Excel. Posts about make your own cover page in microsoft word written by Maurice. As you can see in the images my template holds about 15 cover pages to choose from. The details, font size per detail, and how it should look like is most likely to be specified. • For books and other kinds of literature, you can actually veer away from the normal black-and-white cover page. You may use your creativity and add items and design materials that would make your cover page more interesting. • For formal documents, strict implementations on the professional look of your cover page must be followed. The format and overall look of a cover page may vary depending on the company you work. A cover page is truly an essential part of any document. Aside from our available cover pages for download, you may also take a look at our samples. Advertisement It’s all about first impressions. But how much care do you put into dressing up your documents? Is it all title, headings, subheadings, bullets and paragraphs, or do you put some more thought into the documents you create in Microsoft Word? There are a lot of things that go into a This guide examines the elements of a professional report and reviews the structuring, styling, and finalizing of your document in Microsoft Word. But we are talking about first impressions here. So, let’s take on the first thing our eyes fall on – the cover page. The cover page is the very first page of your document. Its purpose right at the beginning is to give the reader the “Big Idea” about the document. The why and wherefore is communicated through a specific title, the author name, date, a one-liner on the subject and any other bit of important information that you think is important for the reader. What Does a Vanilla Cover Page Look Like? You might have spotted monochromatic and simple cover pages on and school essays. They are dictated by style guides like the Chicago Manual of Style. The title page takes a minimalist approach to cover page design. For instance, the title or topic of the study is centered one-third of the way down the page. Open a new Word document. Click on the Insert menu on the ribbon. The dropdown for Cover Page is the first feature you will spot on the menu (under Pages). Click on tiny arrow next to it and open the inbuilt gallery of templates. Pick one from the 16 pre-formatted templates and three more on Office.com. Select the one you like and click on it. The cover page appears at the beginning of the document by default. But to place it in any other location, right click on the cover page thumbnail in the gallery and select from the options given. Though, am not sure why you would want to! Customize Individual Fields Click on each pre-formatted field (the square brackets) and the whole thing gets highlighted with a blue field label on top. Type in your version for the given field. The author name might appear by default if the Office installation is in your name. Place the common information in and you don’t have to bother with typing them again and again. Change the date fields with the drop-down arrow and select a date from a calendar. You can format all fields just like normal text. You can easily edit graphical cover page elements like any other image. Just click on the graphic to display the Drawing Tools and Picture Tools menus on the Ribbon. Change the Design on the Fly Customizing a pre-formatted cover page is a piece of cake. The templates consist of formatted controls and graphic boxes that come in different color themes. So, you can change any part of the template on the fly. Notice a picture on the cover page template? Maybe, you would like to swap it out with a logo or another more appropriate image. Just right click on the picture and click Change Picture in the context menu. Changed your mind about the entire cover page? While working on one cover page, you can change it for another cover page by selecting a new template from the drop-down. The new template retains the field entries. Note: To replace a cover page created in an older version of Word, you must delete the first cover page manually, and then add a new design from the cover page gallery. Click on Save to finalize the cover page as a document. If you would like to save the cover page for later use in another document, select the entire cover page. Click on Insert > Cover Page > Save Selection to Cover Page Gallery. You can use the same menu to remove a selected cover page from the gallery. Design Your Own Cover Page Microsoft Word templates are a time-saving solution, but they don’t allow your personality to shine through. To add a personal touch, you should put in a bit more effort and make a thoughtfully designed cover page from scratch. You have all the at your disposal. When you can, a cover page is less of a chore. Borrow or steal ideas from the process. The screenshot below displays a cover page I created in Microsoft Word from scratch. I used a few basic to create the design and formatted them with color. Save Your Custom Template Complete your design on a fresh Microsoft Word document. Save this document as a Microsoft Word template ( File > Save As > Microsoft Word Template) in a location of your choice. Now, the next steps are about adding your own cover page to the default choices under the Insert menu. Follow these steps: Press CTRL + A to select the entire page. Add these selections to the Quick Parts gallery. Go to Ribbon > Insert > Quick Parts (the Text Group). Select Save Selection to Quick Part Gallery from the drop-down. Enter the details in the dialog for a new Building Block. Building blocks are reusable Microsoft Word elements that you can add to any of the galleries available in Word. This is what the dialog box looks like: • Name: Give the cover page a Name. • Gallery: Choose “Cover Pages” from the dropdown. • Category: Choose a category. For better organization, make a new category. • Save in: Save it in your template or in the building block. When saved as a building block, you can use it in any Word document without opening the template. Click OK and close the Building Block dialog box. Go to the Insert menu and check your new cover page template. Add Some Style with a Cover Page A cover page is one of the best ways to stylize your document. But is it one of the more Are you overlooking some of Microsoft Word's most useful features? This application features a surprising number of underused tools and options. We have unearthed seven and will show you how to use them.? A Word document is often bland. So, do consider the merits • A cover page gives the reader a quick visual of the content inside. • Save and re-use a generic company-wide cover page in the gallery. • Convert a document with a cover page to PDF with one button and send to any device. Most of us don’t commonly employ a cover page with a document. Let us know the benefits you find in inserting a well-designed cover page. Image Credit: faisalsk007 via Wikimedia Commons. ![]() 10.01.18 Home > Multimedia > Desktop Publishing > Microsoft Publisher Tips flyer templates that can be downloaded for free. Use our golf poster templates and be. Create great looking golf posters. Promote your tournament. Customizing a video template OR creating a video design from. Hosting a golf-related fundraiser? Offering professional golf lessons? No matter your specific need, one of the Microsoft Publisher golf template brochures listed here is sure to meet your requirements. Golf Tournament & Golf Scramble Flyer Template MyCreativeShop.com. Golf brochure template. Golf Instructor & Course Flyer & Ad – Word Template & Publisher Golf Tournament Flyer Free Golf Flyer Templates. Golf Flyer Template Microsoft Word. Events flyers print templates sports golf event flyer template Success. Charitable Golf Tournament Ticket Publisher Template is for sports. This template is a Microsoft Publisher template designed by Godserv to be edited with Microsoft. Try Microsoft Edge A fast and secure browser that's designed for Windows 10 No thanks Get started. No results; 0. Templates Support Buy Office 365. ![]() • • • • • Microsoft Word 2013 is an excellent book writing tool -- as long as you stick to typing text for the book's chapters. It's less than stellar at handling jobs such as editing cover images and positioning objects to precise page locations quickly. Don't let those limitations stop you, because you can actually use Word to write a book, if you don't have other desktop publishing programs to help you. Microsoft packed a surprising number of tools into it's word processing application that simplify your writing task and help you create a book you'll be proud to share with the world. Basic Tools You’ll Use Frequently Authors often have target word counts and Word's word counter displays that important number on its status bar as you type. If you need the word count for a specific block of text, highlight it to view that number. Although you probably won't use a dozen fonts to create your book, Word lets you apply any font on your computer to text you select. After you select text, you can make it bold, italic or underline it quickly by clicking the appropriate button on the pop-up menu that appears. Most books aren't 8.5 by 11 inches, the default page size you see in Word. You can switch to a new size from the Page Layout tab. This tab also has controls that adjust margins, indentation and spacing between paragraphs. These are critical properties you'll need to adjust to create a professional looking book. Launch Word 2013 and type 'booklet' into the main splash screen search box. Although Word doesn't have a specific template for a recipe book, you can transform. Get started with basic Office tasks in e-book format. Templates Support Buy. Downloadable e-book versions of Microsoft Office help articles as a training book. More Microsoft Word Textbook Template images. ![]() Identify Your Chapters Critical book elements, such as chapter headings, are just a few clicks away when you create a book using Word. Add a chapter heading by highlighting text, clicking 'Home' and selecting a heading style you like. If you don't like any you see, click 'Create a Style' to create one. You can also change a heading's font size instantly from the Font Size menu. Find Needles in the Haystack Regardless of the type of book you're writing, you'll probably need to search for specific text one day. Word's powerful Fine and Replace tools help you find all occurrences of a word or phrase quickly and replace them with new text, if you like. For example, if you decide to change the name of one of your characters from 'Jennifer' to 'Jennifer Lou,' you can do that instantly using the Replace feature. Say It With Style Word's grammar checker is an invaluable aid for checking your book for spelling and grammar errors. ![]() When you adjust the Proofing settings correctly, the program even checks your book for style issues and computes a readability score that shows how readable your book is. You can also adjust AutoCorrect Options that enable Word to correct mistakes as you type. Don't Forget the Intricate Details Many books contain other elements besides text and photos. A children's book, for instance, may have stars and other small shapes. Add them anywhere by selecting one from Word's Insert tab. This tab also has a button that enables you to insert tables and SmartArt. Review some of the Shape and SmartArt samples, because they may inspire you to add them to parts of your book. Dazzle Them With Your Cover In a world where some people really do judge a book by its cover, it's important to create an impressive one. You can do that by adding a photo to a page and overlaying it with the book's title, your name and other text you'd like to appear there. Add text by inserting text boxes on top of your image and typing your text there. Adjust the text's horizontal position by clicking one of the alignment tools in the ribbon's Paragraph section. Word's image-editing capabilities are limited. However, formatting tools such as Shadow, Glow, Reflection, 3-D Rotation and Artistic Effects help you turn ordinary pictures into spectacular ones that can make your book cover stand out. ![]() Track Changes: Your Built-in Safety Net You don't have to worry about losing that excellent section you wrote previously, if you use Word's Track Changes feature. It keeps track of all changes and enables you to revert to any previous document state at any time. For instance, if you delete a sentence, one day, you can put it back another if you like. You'll also find this feature helpful if more than one person works on the book, or when you are working with an editor. Track Changes can show you who made updates to the text. Give Me a Break Word also helps you save time by inserting page breaks for you when your text exceeds the page you're on and when you are ending a chapter. You can also insert page breaks manually. You may also find column breaks useful if your book needs to display text in columns. Section breaks help you separate information on a single page. Each break can have its own footers and headers. Other Essential Word Tools If your book needs cross references and an index, Word can build them for you. It also inserts page numbers automatically and helps you create a bibliography containing reference material you used to write the book. One of the most important elements in a book is the table of contents. Word helps you build one when you add heading styles to your text. The program finds those headings and uses them to create your table of contents. Begin With a Building Block You don't have to start from scratch when writing your book. Many vendors offer book templates that can help you get started. Choose one that already has margins, sizes, spacing and other properties already set, and all you have to do is insert content and tweak it to suit your vision. You can also search for book templates from within Word. E-books for Microsoft Office. Downloadable e-book versions of Microsoft Office help articles as a training book that won’t close while. Basic Tasks in Word 2010. • • • • • Before aspiring chefs can produce their culinary masterpieces, they need a bit of direction. Provide your own kitchen creations through a Microsoft Word recipe book. With Word's preset templates, you're ready to start slicing and dicing your recipes without having to worry about page setup and layout. Every part of the Word recipe book template is customizable, meaning you can go from fast food to comfort food to complete gourmet, and everything in between, as quickly as you can type it. Step Launch Word 2013 and type 'booklet' into the main splash screen search box. Although Word doesn't have a specific template for a recipe book, you can transform a template quickly. Double-click the first template to appear in the search results, 'Booklet.' In a few moments, the book opens. Scroll through the pages to get an idea of the layout and what you'll want to change. Step Click into the 'Title of your Booklet' bracket on the first page. Type your recipe book's title. To format the title, or any other text throughout the cookbook, click the Home tab and use the options in the Font, Font Color, Size and font formatting sections. Step Right-click the generic image on the template's cover. Choose 'Change Picture' to open the 'Insert Pictures' window. If you already have images for the recipe book, click 'From a file,' browse to the photographs or illustrations, and double-click one to add to the cover. Otherwise, click the 'Office.com Clip Art' option and type something related to the image you'd like to see, such as 'apple pie' or 'lamb shank.' Step Repeat the process for each of the generic placeholder images included in the booklet. You can also do this as an as-you-go process and change the pictures as you place the text. To add an image at any time, click the 'Insert' tab. Click either 'Pictures' to add your own or the 'Online Pictures' button to browse clip art. Step Move to the first section of text in the booklet. Highlight the placeholder text. Type your own or copy and paste from another source. You can do this in bulk by highlighting and copying all of the text in the booklet, or doing it piecemeal. Adding it piece by piece retains the Word formatting and layout. Step Add a new page to the recipe book by positioning the cursor to the right of where you want the page break and pressing the 'Ctrl-Enter' keys. Add page elements either by copying and pasting from the existing book pages, then updating them, or adding them from the Insert tab. Click 'Text Box' and select 'Simple Text Box' to add a new area for text on the page. Drag the cursor until your preferred text box size appears, then click inside to type. Step Click the 'Design' tab for options to update the recipe book from the template to your preferred styles. Click the 'Colors' button on the ribbon and choose from the drop-down menu of color blocks to overhaul the entire theme of shades used in the cookbook. Click the 'Page Color' button on the ribbon to change from the basic white in the template to a full page color background. Experiment with fonts, borders and theme changes until satisfied. Step Update the back page of the recipe book, which is actually on the left side of the first page of the Word document. Replace any of the generic content as desired, such as the chef's contact information, fundraising details, a biography of the cooks and more. To delete any unwanted text, simply highlight it and press the 'Delete' key. Step Scroll back to the Table of Contents and update it to reflect your new recipe titles and page numbers. You can also delete this table and add your own, using the header styles on the Home tab and the Table of Contents builder on the References tab. Step Save the recipe book to the Cloud (new for 2013/365) or your preferred computer location. If you plan to distribute the cookbook electronically, choose 'PDF' from the 'Save as type' menu and save both a PDF and a Word copy. Step Click 'File' and 'Print.' Most home printers will not print double-sided, so you'll need to do two sets of printing and assemble the book. 2/20/2018 0 Comments Microsoft .net Active Template Library Atl Module: full version free software download![]() Nov 04, 2013 Special Microsoft files are required on runtime. Visual C++ runtime libraries and the Microsoft.NET Active Template Library (ATL) module. Windows Template Library: Still Alive and Kicking. Library was Microsoft's most successful attempt at providing a C++. The newer Active Template Library. The Active Template Library (ATL) in Microsoft Visual Studio.NET 2003 SP1. This module exploits a memory corruption vulnerability within versions 10 and 11 of the Office Web Component Spreadsheet ActiveX control. This module was. NET DLL memory technique by Alexander Sotirov and Mark Dowd and should. The latest version of this topic can be found at Active Template Library. A new feature in Visual C++.NET. Discusses the module classes new for ATL 7.0. To simplify COM development, Microsoft introduced ATL (Active Template Library) for C++ developers. ATL provides for a higher-level COM development paradigm. It also shields COM client application developers from the need to directly maintain reference counting, by providing smart pointer objects. Other libraries and. ![]() Hi, In our organization, we are planning to upgrade Powerbuilder12.6 to Appeon Powerbuilder 2017 on Window 2008 R2 machines. Can someone please help with below info - • Which is the stable Powerbuilder 2017 version which should be used/installed? As per Appeon site the latest available for PB is Build 1681. • When Powerbuilder 2017 R2 will be getting released? As per keynote presentation, it was scheduled for release around Mid Jan 2018, does anyone have exact details about the same? • In the Appeon 2017 installation guide, under Visual C++ Runtime and the Active Template Library, it's mentioned that - When you deploy the core PowerBuilder runtime files, make sure the msvcr100.dll and msvcp100.dll Microsoft Visual C++ runtime libraries and the Microsoft.NET Active Template Library (ATL) module, atl80.dll, are present on the user’s computer or server. Whereas in Powerbuilder manuals, I found below - When you deploy the core PowerBuilder runtime files, make sure the msvcr100.dll and msvcp100.dll Microsoft Visual C++ runtime libraries and the Microsoft.NET Active Template Library (ATL) module, atl100.dll, are present on the user’s computer or server. Is it really required to have atl80.dll for PB 2017 installation or atl100.dll will suffice? If atl80.dll is required then does it needs to be installed separately or comes as part of PB 2017 runtime packager itself? Microsoft visual studio 2010 is already installed on the machines which contains msvcr100.dll, msvcp100.dll and atl100.dll Regards, Abhijit Question Tags: • •. Hi The PB Help was a little confusing in PB 2017. However, Appeon have clarified this in the PB2017R2 release, as follows (from the R2 Help): When you deploy the core PowerBuilder runtime files, you must also deploy the msvcr80.dll (for 32-bit only), msvcp80.dll (for 32-bit only), msvcr100.dll, and msvcp100.dll Microsoft Visual C++ runtime libraries and the Microsoft.NET Active Template Library (ATL) module, atl80.dll (for 32-bit only) and atl100.dll, if they are not present on the user's computer. The PowerBuilder runtime files have a runtime dependency on these files HTH Regards. Hello, On Tuesday 28 July we released guidance and updates to assist developers using our Active Template Library (ATL) to prevent creating controls or components with potential security vulnerabilities. Vulnerabilities in libraries are a rare, but industry wide issue, that requires broad collaboration and action by the community at large to effectively resolve. Developers who have built controls using the ATL should take immediate action to review their control to identify if it is vulnerable and take appropriate action to rebuild their control using the updated ATL library and distribute a non-vulnerable version of their control to their customers. If you develop any controls with ATL then please take a look at the detailing the steps required to identify and address affected controls. Also, we cover the issue in a. Thanks Damien Visual C++. Hello The recent ATL Security Update targets two different customer scenarios: 1) end-users and 2) developers. Here an “end-user” can be categorized as anyone who has the VC Redistribute package installed in a standard location (see note below) and which can be installed directly by a user or as a result of installing another product. A “developer” is anyone who has Visual Studio installed. Here is a quick synopsis of what gets installed for each scenario: *End-user experience* a.A new version of atlXX.dll (where XX matches a specific version number) is installed in the Fusion Cache (a.k.a. Windows SxS folder) WindowsWinSxS*atl* Developer experience a. A new vcredist.exe – that contains: 1) the latest version of the CRT, ATL, MFC and OpenMP libraries 2) Matching pdbs for the new libraries that support multiple architectures (X86, X64, IA64) 3) And for completeness/correctness, some headers from CRT, ATL, MFC, and import libs 4) New CRT, ATL, MFC, OpenMP libraries in the Fusion Cache (this is different to the end-user experience – see above) *Why?* In these scenarios the end-user experience is as small as possible while the developer experience is as compete as possible. Thanks George and Damien Please note: The standard location can vary based on your operating system but its exact location is immaterial to this description. Hello David Thanks for taking the time to send us your comment/question. My first question to you would be “why would you want to?” Assuming you deploy the referenced version of the CRT with your application (which is our strong recommendation) then the relevant CRT version would therefore be on the target machine? That said, you can work around it if you want (caveat emptor), see here for one example of how to do that: Just for completeness I should point out that VS2005 and VS2008 have different semantics when binding to CRTs, see this post from George for more details: (these may also be of interest too: and ). Thanks Damien. I think you can replace #define _BIND_TO_CURRENT_VCLIBS_VERSION 1 with #define _BIND_TO_CURRENT_ATL_VERSION 1 #define _CRT_ASSEMBLY_VERSION '9.0.30729.1' #define _MFC_ASSEMBLY_VERSION '9.0.30729.1' #define __OPENMP_ASSEMBLY_VERSION '9.0.21022.8' to use the latest version of the ATL DLL and explicitly reference the previous versions of the other DLLs (on my machine there is no SP1 version of the OpenMP DLL, only the RTM version). It’s better to put the equivalent definitions in your project preprocessor settings than in a header file. I don’t think any of this is supported by Microsoft though and I haven’t actually tried it myself. Why do I always have to learn something new when some idiots make a new version of the software? Is it not easy enough to copy everything from the previous working version and LET IT BE as it is! Just improve what is needed but don’t alter anything because the work to learn everything again is making everybody angry. We have here already hands full of work with our own programs. We don’t want to have anything additional just to use some new version of software! And learn lot of unnessesary changes only because the developers are idiots! KEEP IT STABLE! What would you think of a car that had to be driven backwards only because some team of idiots want to make changes!?! Nobody would want to use that car! Car manufacturers just change a bit the way the new model looks but keep it the same otherwise. Is it too much to ask to do less and be better! Hello Janne Thanks for your feedback and sorry for the inconvenience we have caused you. So in general the model here should be relatively straight forward, whenever you build/rebuild your software, you need to ship your binaries (exes/dlls) and the redistributable for the libraries you are built against (i.e. This is the reason we have/ship the VC Redistributable and this has not changed recently. We have made changes in how libraries are found on the disc (fusion/sytem32) or which version you target by default (RTM/Current) but the same guidance/process – ship the redistributable for the libraries you are built – stays the same. Is there an issue with this design that does not work in your situation? Thanks Damien. Our process involves checkin driven automatic builds of ~100 Visual Studio project files. We have another ~20 projects that are built on demand due to their large size and infrequent modification. Finally, we have prebuilt 3rd party libraries and DLLs that are integrated into the code. We don’t have source code to those modules; in fact, we would be hard pressed to convince some of the vendors to give us a hotfix (let alone a new build). Modifying every source file over this large of a project (including open source projects) is not feasible. Using 4053 and 762 at same time does not appear possible either (there are reports saying that having them in the same manifest is bad and should be fixed). Getting new versions of libs and dlls from vendors (more than 20 in several different countries) is also not something that can be done terribly quickly (especially when you’re minimizing change during late stage development). Upgrading the runtime library will require a complete new release cycle/test which will delay the release by at minimum a month. We do NOT use ATL/MFC anywhere but are forced to do this because the CRT runtime is also upgraded. We have automatic updates disabled and have not applied the patch given the impact. It is also worth noting that some of our developers have had trouble getting the patch to install as it crashes due to missing.msp files. Is there a way to install the patch without all the.msp files or original media? Beyond this, what is the most reasonable way to deploy a patch like this on such a large project? It doesn’t look like there are many options without the uber-recompile. We use VS2005 sp1 with InstallAnywhere (no MSI) with the msv*.dll files and *.manifest files in our directory. Rgreen – at – voxeo.com. This bit me yesterday. I was making one of the final builds of a new version of the application that is running inside one of our lighting control systems. Suddenly, our beta testers around the world started to complain that the new build didn’t even start on their computers and lighting control boards! (And since you just get the useless 'Invalid configuration' error message, it doesn’t give you much of a hint.) I almost paniced because we are supposed to go public with this version on Friday this week. After hours of seeking, I realized that there must have been some automatic update on my development machine that replaced the libraries. When making the new build, VS2005 silently started to refer to the new library. Our testers and our XPEmbedded control systems didn’t have the update (of course) so they couldn’t run. I find the whole idea of silently changing to a new library version horrible. This happened during the very last days of our beta testing. Even if I know what happened now, I cannot simply throw in a completely new version of the core runtime libraries in the very last minute (looking at the change in the build number, there must be a lot of changes). This needs to go through heavy testing before we can start using the new library in a mission-critical system! It seems like you have little experience in how things are used in the field. Rob Green (above) seems to have pretty much the same experience as I do but on a larger scale. I am sure that there are lots of frustrated users out the now. Also, I still haven’t been able to force the compiler into using the old 762 build of the DLLs. I have tried the various tricks that have been suggested. Could I just uninstall the patch? Quote: 'Thanks for taking the time to send us your comment/question. My first question to you would be “why would you want to?” ' 1. Echoing others, we have a set of third party libs built against SP1 that we don’t want to recompile right now. We want to do this at an appropriate point in the release cycle. For example, in Trunk, not on a stable Branch the day before a release. Currently, our build machines have not had the windows update applied, yet most of our development machines have. You could argue that this is wrong, but I’m sure this is not unusual. All machines have VS2008 SP1 of course. I really think that this should have been part of a Visual Studio service pack allowing us more control whether to adopt the new CRT. Regards, David. I’m having a different problem but one that is related. After patching our build machines with the security update (VS 2005) we started having trouble with the setups for our products (generated by InstallShield). Even after I made sure InstallShield was using the updated merge modules for MFC, ATL, etc., when I run the installer it does *not* install the 4053 assemblies (and our applications will not launch). However, after I run the vcredist on the target system the 4053 versions are installed and the application works fine. This may be more of an InstallShield bug than anything. But how is it that merge modules provided by Microsoft don’t seem to be actually gathering in the correct DLLs when the setup is compiled? Hello David Thanks for taking the time to send me more information – it definitely helps us understand your scenario better. Let me walk through your two points to see if I understand them as I still have (yet more) questions: Re: your point 1) you do not have to have these third party binaries recompiled if you do not want to – you can just keep using the versions you have. [A couple of sub-points however:] 1) If they have the security issue that the update addresses and are potentially vulnerable then you may want to have them recompiled – but since I do know the specifics I would not know if this would be an issue 2) Regardless of point 1, the third party binaries will probably be rolled forward to running on the new libraries anyhow, if they run on an end-user machines with them installed (via auto-update for example), but this should be no issue. Are the end-user machines some type of dedicated machines without automatic updating? [End of sub-points.] Re: your point 2) building on different configurations to those you develop on is again your choice (and given a large organization with many developers occasionally seems inevitable to some degree) – but I am not sure I see the issue here, if the build machines are consistent then they will reference only one version of the libraries and if you ship the redistributable with your application then it will all work – the only issue here I see here is if you do not to ship the redistributable – and that is definitely not a supported scenario. I should just clarify too, when I say 'ship the redistributable', you have a few ways to do this – VC Redistributable, MSMs, app-local and even static linking (although there are some issue with static linking) but all will get the new libraries on to the end-user system. Let me know if am getting closer to understanding the scenario here? Thanks George and Damien. Hello Anders Your situation (or at least the questions I would ask about it) seem similar to those I asked David but I suspect you will have some different answers (since your end-user systems may be closed box dedicated machines if I read your situation correctly.) Personally I am less familiar with the XPEmbedded scenarios so I may have a few more question for you however. Re: your comment: Our testers and our XPEmbedded control systems didn’t have the update (of course) so they couldn’t run. So I assume you are saying that it does not make sense for you to (and therefore you do not) ship the VC Redistributable (or the new version of it) with your application to these systems? Is that because you have “closed-box” system with the XPEmbedded control systems? If the answer is yes and yes then it may not make sense to have your development machine auto-updating if this will move them out of sync with your target platforms. Would that sound correct? Do your target systems ever update our libraries then? And if so how? > Could I just uninstall the patch? Our general advice is to never uninstall Security Update but if you provide a “closed-system” device that does not have access to auto-updating and is sealed then you may be able to determine that an uninstall is safe for you but you need more information than just this to make a decision. Thanks George and Damien. Hello Rob If you have automatic updates turned off on your developer/build machines then you will not see the new CRT (therefore your binaries will not reference it) and all your end-users will just work (many of your end-users will be auto-updated but regardless nothing will break.) There is no way to install the update without the msp. Not sure why you are seeing an issue installing the patches, is there anything “different” about your setup? (We have tested the install on VS2005 to verify it and it is definitely working for us.) Unfortunately, if you need the Security Update then you probably need the “uber-recompile”. Feel free to follow up directly if you want, my email is my_first_name at you_know_where (and this is Damien typing ) Thanks George and Damien. Hello George and Damien I think I meet the same problem with David. I have built something.exe before install this package, and have copied microsoft.vc90.crt.manifest, microsoft.vc90.mfc.manifest, mfc90.dll, mfc90u.dll, mfcm90.dll, mfcm90u.dll, msvcm90.dll, msvcp90.dll, msvcr90.dll to the same directory with something.exe, and put all of them to a custom’s pc with neither VC redistributable package nor service pack installed. Something.exe works! I open the something.exe with UltraEdit, and cound find that both the CRT and the mfc version which were referenced are 9.0.30729.1 in the assembly information. Of course I have defined #define _BIND_TO_CURRENT_VCLIBS_VERSION 1. BUT NOW, after installed this update, the new version 9.0. CRT, MFC and so on have been installed in to WinSXS. After I re-build the something.exe, I will reference CRT 9.0.30729.1 and reference MFC 9.0. And Dependency CRT 9.0. And something.exe won’t work in the custem’s pc. I have try to overwrite the CRT, MFC files with the new version 9.0., but no effect. Sorry for my poor english, any question please let me know. Please advise me how to do, thank you very much! Nicholas Wang. Our story and comment. Months of beta testing and everything is going smooth, the day before going to duplication. One minor change is made to program and recompiled and released for internal testing. User emailing to R & D that program won’t come up. Look into Vista event log shows side by side conflict. Where did version 4053 come from Hunting. Find culprit security updateDuplicator is asking for final release. End user must install release by 8/26/09 or application stops working. What do we do? Not enough time to try suggested changes. The fear of un-installing. Head ache of dealing with a patient with knife pulled out and trying to sew them back together. Scratching our head what to do to beat the deadline. Looked under desk. Found old computer taken offline one year ago. No security update installed with VS 2005 SP1. Got the program compiled. Build final release and hand off to duplicator. Ready for FedEx pickup to go to customer. Blood pressure comes down Since 2006 8.0.50727.762 was untouched and sent out with our program. Then comes thru a backdoor is a security update that everyone loads due to fear of virus attack and changes our compiler and runtimes. This should have come down thru a service pack and not a security update. People would have been more cautious to load a service pack. Giving others time install it learn about the conflicts and warn other programmer about this. Instead of just blasting it out to the masses in a security update. Now we think twice about installing those security updates. Hi, Ted Thank you for your information! My EXE is a very simple, I don’t think so there is any library included by it. BUT I have resolved this issue after the following change: in the file 'C:Program FilesMicrosoft Visual Studio 9.0VCincludecrtassem.h' ——————- #ifndef _CRT_ASSEMBLY_VERSION #if _BIND_TO_CURRENT_CRT_VERSION //#define _CRT_ASSEMBLY_VERSION '9.0.30729.1' // to be commented #define _CRT_ASSEMBLY_VERSION '9.0.' // to be added #else #define _CRT_ASSEMBLY_VERSION '9.0.21022.8' #endif #endif ———————- Rebuild the exe, and copy CRT & MFC runtime files with 4148 to the same dir with exe, It seems all things work. > So I take it from your comments that you do not ship the “VC Redistributable” with your application – can I ask why not? And what is your process to see that the correct runtimes get on to end-user machines? I think you’re missing the point. The problems are that: 1) People didn’t know that they needed to deploy a new version of the CRT, because they reasonably expected that an ATL security update only updates ATL, and because they don’t equate 'I want to protect my machine against security threats' with 'I want to be forced to deploy a new version of the CRT and ATL right now.' This update installed silently on machines and then left people scratching their heads as to why other people suddenly couldn’t run their builds, but they still could. 2) You can’t expect everyone to instantly switch dependencies and deployment to a new version. Many reasons have been given already for this, including testing, need to obtain updated libs or installer packages from vendors, need to start a new regression testing cycle, restrictions in patch deployment to end users, etc. Nobody wants to take a dependency change the day before they ship. In addition, the tools for diagnosing this problem are lacking. The error message displayed to the user on XP systems — 'the application configuration is incorrect' — is very poor. I spent some time tracking down CRT mixups today and the only way I was able to track down the offender was to run 'strings' on each lib and grep the output. This could have been mitigated if: – The security update were installed separately from part of the update that affects build processes. – The part that affects build processes were an optional update. – The ATL update was labeled to also indicate a CRT update. – The VC++ Team Blog had a warning about the update BEFORE the portion affecting builds was pushed out. – The Visual Studio IDE displayed an indicator on the next startup that deployment requirements had changed. – The linker or manifest tool issued a warning when the merged application manifest references more than one version of the same DLL. – There were greater awareness as to the manifest mechanism, the symptoms and tools for diagnosing manifest-based load errors, and the CRT rebinding mechanisms. > So I take it from your comments that you do not ship the “VC Redistributable” with your application – can I ask why not? We do not ship VCRedist* with our application either – rather we use the merge modules. We do this due to the advice on this very blog that the 'VC Redistributable' should only be used for ClickOnce deployment: ‘“Click Once” will use a custom built installer package called “VCRedist_.exe” to install the libraries for you. DO NOT use the VCRedist_.exe installer packages for any other purpose.’ [] Does this statement no longer apply? Hello Paul Thanks for your posting. My first point here is that when I say 'ship the redistributable' (or something similar), I am not advising using one particular method over the others; this from previously in this thread where I said: I should just clarify too, when I say 'ship the redistributable', you have a few ways to do this – VC Redistributable, MSMs, app-local and even static linking (although there are some issue with static linking) but all will get the new libraries on to the end-user system. All means of “shipping the redistributable” have advantages and disadvantages, my meta-point here is that just that you should ship it one way or another with your application. I will look at the other post when I get in to work and see what guidance we gave there (and why specifically). Thanks for your follow-up and question – will get back to you as soon as I can. Thanks Damien. Hello Paul Once again, thanks for your question and pointing me to the previous post. I read what Ben said on the previous post and have two general comments. Firstly, in sprit I think Ben’s post is still consistent with the major piece of advice we have stated here and that is that you always need to deploy/ship the “VC runtime libraries” you depend on with your application and doing this is your first/best means to ensure your application runs successfully on end-user machines (and surely this is the ultimate goal). (Un-)Fortunately you have a couple of mechanisms to do this and need to choose one. My comments on this current post are generally about trying to find reasons why people prefer not to (or cannot) follow this guidance (and to be clear I am sure there are valid reasons, I just want to capture them and their scale, I am not saying that such reasons would never exist.) Secondly, as you can see form the other posting, Ben’s (and therefore our) guidance at the time was to prefer one method (MSMs) over others but again he speaks of advantages and disadvantages of all the different methods provided. You can also see on the thread that Stephan replied said that he preferred a different method to Ben (and I see Phaeron and others replied too with different opinions – nice to see Phaeron is still active on our blog.) The decision needs to be made by individual developers based on their application’s/user’s requirements/configurations – and I think that is really the best/only advice. Now to be clear (and for those who want me to take a stand), my personal preference, which I guess subliminally comes through when I post through the terminology I use, is definitely for VCRedist as the default, but of course I would not claim that this is the best/only solution in all cases. Redistribution issues aside, I think Michael’s post on August 21 and Phaeron’s post on August 26 hit the nail on the head. In my industry, development environments and tools versions are under strict configuration management and control. The prospect that our compilers can be updated at any time without our knowledge or consent creates a configuration management nightmare. Although I have Windows Automatic Updates disabled on my PC, our IT department forces anything labeled as a security patch through Landesk. The decision to deploy these fixes as a Windows Update instead of a Visual Studio Service pack was an unfortunate one. Nevertheless, we are where we are. Could you please advise as to how I can prevent these silent updates from taking place in future. Thanks and regards. Hello Frank > This currently keeps us from delivering service packs for our product, since InstallShield does not provide an updated merge module. Thanks for sending this question on to us. I assume there may be a typo in the sentence above, InstallShield does not provide the updated MSMs, we (VC) do. And the update does provide these, the location on your machine should be something like: C:Program Files (x86)Common FilesMerge Modules Let me know if they do not exist after you install. Thanks Damien. This update causes major problems for those who have distributed applications based on the merge modules and wish to later patch their application. Once an application is distributed, you must obey the rules required for a minor update (no product code change), and this does not allow for installation redesign. Normally, you don’t care to devote time to installation restructuring and testing in minor updates as well (which means you typically don’t want to move to vcredist). Therefore, you need to be able to specify the version of the CRT in your build so that the installation package can continue to use the original merge modules and allow the automatic updating to get the newer versions installed. Therefore, it may not be that you want to use the old CRT, but rather that you have to use it for expediency. Alternatively, you could conceptually merge all merge modules (e.g., RTM, SP1, and updated versions) into the installer for your minor upgrade as this would not violate any minor upgrade rules since it only adds new components from the new merge module. This would keep the previous compiler versions on the system after an upgrade is made but would remove them when the last referencing application is uninstalled. However, due to a problem in the VC++ merge modules that is trivial to fix (see ), this cannot be done either. This actually would be a good solution to this problem if this fix was made. Hello Thanks for the great feedback and comments. Just one further personal observation, I am not sure how much you gain (if you gain anything at all actually) by reverting the runtime libraries on your dev/test machines if you then deploy your binaries to customers who have machines accessing the internet or on which customers are installing other products. I am adding my comment only because I as yet do not see any responses from this blog’s authors that represent an understanding of the issue. There is a fundamental difference between applying security fixes to software and changing development environments. It is unacceptable that a security patch updates other applications development environments. I found reading this blog entry and the nonresponse to the central issue very frustrating. I would like to read that Microsoft understands their mistake and that they will never do this again. Bottom line Microsoft now has a trust issue. Until I hear Microsoft acknowledge this and pledge to change, the only alternative is to disable Windows Update to protect against these damaging updates. Make no mistake changes that invalidate testing, cause support issues, wasted time researching, reading and responding to blogs, and the delayed releases, etc. That have mentioned in this blog it is obviously a damaging update. Does Microsoft get that? I will echo the previous posters in that the blog’s authors do not seem to understand the issue. We are ONE DAY away from releasing our next version of software, and quietly, unexpectedly, and sneakily, Microsoft go and mess with our development environment behind our backs. Suddenly a build that worked perfectly a few days ago is filled with errors and worse, we can’t explain why. Please do not ever do this again. You simply cause trust issues – we will now be deactivating automatic updates across all machines simply to avoid this issue ever happening again. Is that really the response you wanted? Is that really how you want your critical updates viewed? Have you perhaps forgotten that people need to update installers as well to fix this mess, and that doesn’t happen by magic? Just to follow up on this specific reply 'Re: your point 2) building on different configurations to those you develop on is again your choice (and given a large organization with many developers occasionally seems inevitable to some degree) – but I am not sure I see the issue here, if the build machines are consistent' They aren’t in all cases. Large software projects inevitably pull in plenty of third party (sometimes internal) libraries that were built for VS2005 RTM or SP1 and cannot be rebuilt at a whim (major costs involved). Thanks to this update, Visual Studio then proceeds to embed a default manifest referring to both CRTs/MFCs, which certainly seems incorrect (please say if it is correct, because there’s advice out there to the contrary), and the entire thing occurred with no warning until our automated tests broke because we had no idea that we needed new redistributables! I’d be the first person to say I appreciate bugfixes and updates in older products, but the lack of proper communication over this is completely unacceptable. Phaeron hit it on the head with his list of failures so I won’t repeat them. I think Visual Studio needs to be prepared before those updates can take place without hassle: 1) Make the runtime selectable from the project settings, graphically, e.g. A combobox, not only by defines which nobody finds if one does not know they exist. A runtime security patch should never ever change that project setting. So only the project owner decides if any newer runtime should be used. 2) For being able to target different runtimes and create setups for and with those runtimes the VS setup and patches should allow 'side by side runtimes' (libs, dlls, pdbs, merge modules and vcredist) so that on each machine you always have all versions of the runtime available, not only the latest. So I would expect each set of runtime files to be put in its own redist subdirectory, so no newer runtime replaces an older one – I do not talk about windowsWinSxS but about the VS files under programfiles. 3) With the above 'versioned' runtime directories the built in setup projects could find their correct runtime merge modules as well, so neither new builds nor new setups cause any change in runtime distribution. With the above prerequisites I would not mind too much to get new runtimes installed by windows update. 'Large software projects inevitably pull in plenty of third party (sometimes internal) libraries that were built for VS2005 RTM or SP1 ' to add to JeffH’s reply, I can give a real world example: ActivePDF, which provides ISVs with PDF capability for their apps, ships a redistributable DLL that is hard linked (in the DLL’s manifest) into the 762 versions of VC2005SP1. With policy redirection, etc, it should be ok (can’t be 100% sure though), but I obviously don’t like having mixed references across binaries in a shipping app. Yet another dissatisfied customer. 1) My app is linked against the installed VS CRT. I ship the installed VS CRT. My exe requires, and is distributed with, 3rd party DLLs which are built by the supplier. The 3rd party DLLs reference a specific CRT verision which is supposed (!!!) to match my VS2005SP1 CRT. If the CRT version silently changes then I have two problems: (a) I’m shipping DLLs whose manifests require a different CRT version from my exe, (b) I’m only shipping one CRT version but I now have a dependency on 2 versions. 2) I do not expect an automatic security update to silently break my build deliverables. And I have just been bitten by this a second time in a month. Once again my beta testers are complaining of broken builds. Somehow the update is back even after I disabled autoupdates, perhaps some OneCare issue? Hello JeffH and others Thanks for your input and your feedback. Many of us are reading the replies here and we do take your comments very seriously when reviewing our procedures and processes. In order to provide our feedback I wanted to state that, at this stage, I see nothing here that will cause us to make any changes to our processes for handling VC runtime library security updates going forward. This means that if we find high priority potential security vulnerability in one of our libraries we will update the libraries and release update(s). We feel we have a paramount duty here to protect users and those who ask for updates (either manually or automatically) will receive them – this is generally our highest priority. This action will normally not affect binaries currently running on end-user machines – these binaries will run on updated VC libraries but we strive for no “breaking changes”, as we achieved with the ATL Update, and everything should just work for existing binaries. Yes, we may make a mistake with this from time to time but if so please let us know and we will fix it if at all possible. Of course sometimes the Update may force a breaking change – but again if that is the only way to address a security issue then that may be what we have to do. If anyone did get broken in this scenario with the ATL Update (their already deployed applications broke) then we are sorry and we would like to know about it. The other salient point is for binaries built after the update with the new VC runtime libraries had been applied to a development machine, here I want to restate that we only support a model where the libraries on the development/test/end-user machines are synchronized. Here synchronized can mean that downstream you can have later versions but you must ensure that at a minimum they are all the same version. You can achieve this a number of ways (different mechanisms come with different requirements and risks) but you must ensure that this condition is satisfied. Our general recommendation that is you deploy the VC runtime libraries that you build your binaries with alongside those binaries– in this case you should always be fully protected. With regards to the ATL Update case, the update to developers’ machine should only have trigged warnings/errors if you have code which potentially exposed the vulnerability. If you got build breaks then you were at risk. Sorry if you got caught in the last few days of development but I think it could have been worse. Testing/deployment breaks can only occur if you build on an updated version of the runtime libraries but did not synchronize them on to your test/end-user machines. Again if you followed our recommendations we believe you would have been fine in this scenario too however if you have experienced an issue then please let us know. With security updates we do follow a set of procedures related to disclosure. We do have to balance exposing the issue (to both the good and bad guys), along with the current level of exploitation of the issue, along with the risk of the exploit being publicly exposed by a third party. Without going into the details we followed our normal process here of issuing an Advanced Notification three working days before deployment in this case. On the day of issuing the Security Update we released numerous online details about the update (blogs, videos, etc. – the links are throughout the thread here.) As always, please post any follow up comments you may have here and we will read them. Thanks Damien. > In order to provide our feedback I wanted to state that, at this stage, I see nothing here that will cause us to make any changes to our processes for handling VC runtime library security updates going forward. I strongly urge you to reconsider your position. By distributing a critical security patch and installing a redirect to that version you would have already accomplished the goal of protecting users. All you have done by forcing a dependency upgrade during the compile process is break builds across the globe. Doing this is directly counter to your stated goal of protecting users because (a) you have convinced people that accepting automatic updates is an unacceptable risk and (b) you have made the statically linked version of the runtime libraries a more attractive option, which you cannot service. Hello Ross Thanks for the feedback – again sorry that this causing you such pain, it is definitely not our intention. For issue 1, if you ship the latest VC Runtime Libraries with your application you should be fine; all the libraries your application depends on will be rolled forward to the latest minor version for all dependencies. (See my somewhat related previous comment: “Installing any later/higher minor version of a major version of the VC runtime libraries, either by MS doing an update or customers installing another product (or by customers just installing a later vc_redist* themselves too), will cause your application to run on the later/higher minor runtimes (regardless of what you build/tested against.)”). Again if you break with the latest version then please let us know, we aim for no breaking changes when we do updates but we can make mistakes. For issue 2, the VC Runtime Libraries you build against (or a later version of the same) need to be installed on the test/end-user machines for deployment to work. This is the only model we support. If you deployed the relevant version with your application and it fails then we would like to know. Thanks Damien. Hello Phaeron I really do appreciate you taking the time to raise your comments/concerns and as I said we are discussing this internally and value your feedback and input. By the way, I did not mean to imply that anything I say is absolutely final. I just wanted to be clear that at this stage we were not changing the process – I think we also need to be transparent and give you direct feedback – but do not take that as we will never change the process. Obviously many of you feel quite passionately about this. Thanks Damien. Hi Damien Thanks for your attention. I’m going to put aside my opinions of your management of this issue and try to help you understand my requirements. I ship an exe bundled with 3rd party DLLs. As I understand it, all exe+dll manifests need to reference the same crt version. At the moment, the way I achieve this is to use the correct version of MSVC (in my case 2005sp1) to build my exe. Until this update, using my versioning method of using the correct MSVC version gave the desired effect (my exe referenced msvcrt 8.0.50727.762). After the update, my exe msvcrt versioning was broken. A basic fact of my use-case (and many others) is that I do not have the ability to determine the msvcrt version referenced by the 3rd party dlls I use. Since (afaik) the SxS mechanism requires all dlls+exes to reference the same msvcrt version, I need a way to achieve this goal. — more to the point, I need MSVC to allow me to specify what version of the crt I use. This update breaks the previous widespread assumption that installing a specific MSVC version (including specific service packs) would give me msvcrt manifest compatibility with other dlls built elsewhere based on the same MSVC version. With your update I need to use 3rd party DLLs referencing VC2005Sp1+kb971090 (which don’t exist). I think one possible solution for this issue would be for MSVC to support multiple side-by-side installed crt versions for development (multiple.libs etc) instead of just one version which gets blown away with each update. That way I would have the option of referencing a specific msvcrt version in my builds if needed (or just using the latest version by default). I think this would be an improvement over your current approach and one I would like you to seriously consider for the future. I notice you reference this blog post above: Is this method documented in any Microsoft documentation? It seems like it might partially solve my problem. From what you say, if I make my exe manifest reference msvcrt 8.0.50727.762 using this method, but ship 8.0. Then I should be ok. Is that correct? Can I use that method even if msvc links my exe against 4035? Hello Ross So George and I had a look at this again today and wondered if your deployment scenario hits one of these configurations (or a variant thereof): Scenario 1: You are using AppLocal deployment of the CRT and there are no installations of the CRT in WinSxS (for example on a clean machine.) App.exe manifest references CRT V9.0.1 Abc.dll manifest references CRT V9.0.2 In this scenario the question is which version of the CRT can be deployed AppLocal? The solution here is to use a config file for the files with the lower versions to redirect to the newer version (config file causes app.exe to be redirected to CRTV9.0.2) Scenario 2: You are using WinSxS deployment of the CRT via payload MSMs (these have the actual dlls) without the policy redirection MSMs (these are the redirection xml config files) – these are separate files. App.exe manifest references CRT V9.0.1 Abc.dll manifest references CRT V9.0.2 In this scenario the question is which version of the CRT can be deployed to the WinSxS? The solutions here are 1) install the later version of the MSMs along with their corresponding redirection MSMs or 2) to install both versions of the CRT via the two payload MSMs (not preferred – be careful as you end up with two versions of the CRT loaded in your process.) Of course you may not be using AppLocal or MSMs. George and I would be happy to have a call with you on this. You can email me at my_first_name at Microsoft dot com and we can set up a time. Thanks Damien. Just wanted to note that I’ve been hit too. -Build a setup some days ago and customer installed it on his machine. -Customer reported a bug, which could be easily fixed. -Installed the critical update. -Fixed the bug just recompiled the specific DLL and told the customer that he can just replace the DLL and doesn’t need to do the setup again, since our setup requires rebeoot Bang! Looking and trying to find the cause. Looking, looking, looking Since I’m sort of old school guy I opened the old and the new version of the dll in hexviewer and saw they are referencing different CRT versions! Please don’t change my headers/lib behind my back without telling me. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2018
Categories |