For a Rich Text Box control to bind to an XML element that is returned from a Web service, the Rich Text Box control must contain XHTML content. The element must have the following XML schema:

        <xsd:element name="[elementname]">

          <xsd:complexType mixed="true">

            <xsd:sequence>

              <xsd:any namespace="http://www.w3.org/1999/xhtml" processContents="lax"

               minOccurs="0" maxOccurs="unbounded"/>

            </xsd:sequence>

          </xsd:complexType>

        </xsd:element>

The <elementname> is the name of the XML element that is returned from the Web service.

InfoPath can automatically detect if an element is an XHTML element by querying the element for a sample value when InfoPath connects to the Web service data source for the first time. This article describes how to create a Web service that returns valid XHTML. This article also describes how to display the XHTML that is returned from the Web service in a Rich Text Box control on an InfoPath form.

Create the Web service

        [WebMethod]

        public System.Xml.XmlNode GetXHTMLRichText()

        {

         //Create a temporary XmlDocument object to generate nodes.

         System.Xml.XmlDocument tempDocument = new System.Xml.XmlDocument();

         //Create a wrapper node for the data.  This is necessary so InfoPath

         //correctly detects the XHTML content

         System.Xml.XmlElement theNode = (System.Xml.XmlElement)tempDocument.CreateNode(

            System.Xml.XmlNodeType.Element, "theNode", "http://somearbitrarynamespace/" );

         //Create a "font" element in the xhtml namespace.

         System.Xml.XmlElement theFontNode = (System.Xml.XmlElement)tempDocument.CreateNode(

            System.Xml.XmlNodeType.Element, "font", "http://www.w3.org/1999/xhtml" );

         theFontNode.InnerText= "Red Text";

         //Add a color attribute.

         System.Xml.XmlAttribute colorAttribute = tempDocument.CreateAttribute(

            "color" );

         colorAttribute.Value = "#ff0000";

         theFontNode.Attributes.Append( colorAttribute );

         //Append the font node to the wrapper node

         theNode.AppendChild( theFontNode );

         //Return the wrapper element.

         return theNode;

        }

Create the InfoPath form

In InfoPath 2003

In InfoPath 2007

Try it out

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

When you run the Permission Calculator in Microsoft Visual Studio 2008, the Permission Calculator may add exaggerated permissions or overly restrictive permissions to the application.

CAUSE

This problem occurs when the Permission Calculator cache files are not installed on the computer that is running Visual Studio 2008.

WORKAROUND

To work around this problem, use one of the following methods.

Method 1

In Visual Studio 2008, turn on the Exception Assistant. When you debug the application, the Exception Assistant is displayed. You can use the Exception Assistant to grant specific permissions for the application. This process is required for each permission.

To turn on the Exception Assistant in Visual Studio 2008, follow these steps:

Method 2

Go directly to the Security tab of the project options, and then manually review the permissions. To do this, follow these steps:

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

MORE INFORMATION

For more information about how to determine the permissions for a ClickOnce application, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/91z17fc9(VS.90).aspx (http://msdn2.microsoft.com/en-us/library/91z17fc9(VS.90).aspx)

For more information about the Exception Assistant, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/197c1fsc.aspx (http://msdn2.microsoft.com/en-us/library/197c1fsc.aspx)

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

CAUSE

This problem is the result of the Resource Editor not correctly assigning new IDs to resource names when you try to give a resource a new name. The Resource Editor actually is trying to assign the new resource name an integer ID that is already used by another resource. This will cause the resource ID collision.

RESOLUTION

After you have duplicated your resources and before you start to rename them, take the following steps to ensure that your resource names have unique integer identifiers:

You can now rename your resources using the symbols you created without worrying about whether the symbol has already been defined.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the “Applies to” section.

MORE INFORMATION

Steps to reproduce the problem

APPLIES TO

To use remote debugging with Microsoft Visual Studio .NET or with Microsoft Visual Studio 2005 on a computer that is running Microsoft Windows XP Service Pack 2 and later versions, the Microsoft Windows firewall on both the local computer and on the remote computer have to be configured correctly. The DebuggerFirewall configuration utility performs most of the configuration automatically to permit debugging.

MORE INFORMATION

The configuration utility is an HTML application (.hta) file. Download the configuration utility and then run the configuration utility on both the local computer and the remote computer that is running Windows XP Service Pack 2. Do this after you have installed the Visual Studio Remote Debugger and the remote debugger components. The following file is available for download from the Microsoft Download Center:
Download the Debuggerfirewallconfiguration.exe package now. (http://download.microsoft.com/download/8/5/7/857e38ca-34f2-47e8-8300-56405f85fc4c/debuggerfirewallconfiguration.exe)

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

The configuration utility automatically configures the Windows firewall as needed to permit remote debugging. You have to be an Administrator on the computer that you are using to run the utility.

The configuration utility does not do the following:

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

  LRESULT CALLBACK

 _AfxActivationWndProc(HWND hWnd, UINT nMsg, WPARAM wParam, LPARAM lParam)

 {

    WNDPROC oldWndProc = (WNDPROC)::GetProp(hWnd, szAfxOldWndProc);

    ASSERT(oldWndProc != NULL);  // <----- assert occurs here

    .

    .

    .

 }

The assertion occurs on line 385 with Visual C++ versions 4.2 and 4.2b, on line 384 with Visual C++ version 4.1, line 392 with Visual C++ version 5.0, and on line 389 with Visual C++ 6.0.

CAUSE

MFC subclasses all non-MFC created windows to handle specific activation issues. While subclassing a non-MFC created window, the old window procedure is stored in the properties of the window. Logging off of an Windows NT session causes the atoms used to identify the properties to be destroyed and the property cannot be retrieved. This causes the assertion to occur.

MFC was not designed for Windows NT services. As a result, if an MFC application is spawned from a Windows NT service, minimized, and then a user logs-off, then the assertion will occur.

Also keep in mind that there are other problems to consider when spawning an MFC application from a service or as a service. The OnEndSession() message handler for the main frame window closes out the CDocument object. So the WM_ENDSESSION message must be handled to prevent this from happening.

RESOLUTION

You can do one of the following things:

MFC subclasses non-MFC windows to generally handle obscure window activation issues. For example, it ensures proper activation of toplevel windows when doing in-place OLE activation. It also ensures that the last active popup is activated when a user clicks on a disabled window that is part of the application. Normally, if you have a main window that owns a modal dialog box and some other popup window like a floating toolbar, and you switch activation to another application, and click on the toolbar that was disabled by the modal dialog box, Windows beeps and does not activate the application. MFC ensures that the modal dialog box is brought to the top when you click on the toolbar. Note that MFC handles all of these activation issues for MFC-created windows and non-MFC created Windows. The old window procedure is stored as a property associated with the window only for non-MFC windows. If you unsubclass the non-MFC windows (as the first technique suggests above), you still get these activation features for any windows that were created as MFC CWnd-derived objects.

Unsubclassing the non-MFC Windows

The first technique listed above may be an easy workaround for developers who have already written an application and don’t want to rework their design, rebuild the MFC libraries, or don’t need to handle the activation issues MFC handles.

You can unsubclass non-MFC Windows in the WM_ENDSESSION handler of your main frame window. The following sample code demonstrates how to enumerate all of the windows for your process and unsubclass them: For Visual C++ 4.x and Visual C++ 5.0:

    static const TCHAR szAfxOldWndProc[] = _T("AfxOldWndProc");

For Visual C++ 6.0:

    static const TCHAR szAfxOldWndProc[] = _T("AfxOldWndProc423");  // Visual C++ 6.0

And add the functions:

    BOOL CALLBACK EnumProc( HWND hWnd, LPARAM lParam)

 {

    //check for property and unsubclass if necessary

    WNDPROC oldWndProc = (WNDPROC)::GetProp(hWnd, szAfxOldWndProc);

    if (oldWndProc!=NULL)

    {

       SetWindowLong(hWnd, GWL_WNDPROC, (DWORD)oldWndProc);

       RemoveProp(hWnd, szAfxOldWndProc);

    }

    return TRUE;

 }

 void CMainFrame::OnEndSession(BOOL bEnding)

 {

    // unsubclass the non-MFC windows which MFC has subclassed

    DWORD dwProcessId;

    DWORD dwThreadId= GetWindowThreadProcessId(m_hWnd,&dwProcessId);

    EnumThreadWindows(dwThreadId, EnumProc,(LPARAM) dwThreadId);

 }

Note In Microsoft Visual C++ .NET and in Microsoft Visual C++ 2005, the nonstatic identifiers do not appear either.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Sample Code to Demonstrate Problem

   // Main.cpp

   #include <StdIo.h>

   ...

   static int nGlobalStaticInt;  // Will not show up in Globals Folder

   int        nGlobalInt;        // Will show up in Globals Folder

   ...

   void main(void)

   {

   }

CVPACK : fatal error CK1017: cannot find precompiled types file; relink with file.obj
LINK : warning LNK4027: CVPACK error

With the 32-bit edition, the LINK utility may generate the following error message:

LINK : fatal error LNK1211: precompiled type information not found; “<filename>” not linked or overwritten

Note If you build a static library in a Visual Studio .NET version with precompiled header file, and you use the compiler debug switches /ZI or /Zi, you may not receive the errors that are listed in this article, but you may see either of the following two problems while debugging your application and trying to view any variables from the library in the Watch window:

The resolution for this debugging problem is the same as is described in the “Resolution” section of this article.

CAUSE

When you specify the /Yc and /Z7 options on the compiler command line, Microsoft C/C++ generates a precompiled header file that contains CodeView debugging information. The error occurs only when you store the precompiled header in a library, use the library to build an object module, and the source code does not refer to any of the functions the precompiled header file defines.

RESOLUTION

There are two methods to work around this situation, as follows:

STATUS

This behavior is by design.

MORE INFORMATION

When you compile a module with the /Yc and /Yl<symbol_name> option switches using the 32-bit edition, the compiler creates a symbol similar to __@@_PchSym_@00@…@<symbol_name>, where the ellipsis (…) represents a linker generated character string, and stores it in the object module. Any source file that you compile with this precompiled header refers to the specified symbol, which causes the linker to include the object module and its debugging information from the library.

The following code example demonstrates the problem.

Sample code

   /*

    * To demonstrate this problem, perform the following five steps:

    *

    * 1. Compile TEST1.C as follows: cl /Yctest.h /Z7 /c TEST1.C

    * 2. Compile TEST2.C as follows: cl /Yutest.h /Z7 /c TEST2.C

    * 3. Build a library that contains TEST1.OBJ and TEST2.OBJ as

    *    follows: lib /out:test.lib test1.obj test2.obj

    * 4. Compile TEST3.C as follows: cl /Yutest.h /Z7 /c TEST3.C

    * 5. Link the application as follows:

    *       link /debugtype:cv /debug:notmapped,full test3.obj test.lib

    *

    * To correct this problem, do one of the following:

    *

    *   1. 32-bit only)  Compile TEST1.C in step 1 as follows:

    *        cl /Yctest.h /YlAnyName /Z7 /c TEST1.C

    *      Then, repeat step 2 through 5.

    *

    *   2. Repeat steps 1 through 5, adding the /Yd command line option

    *      to steps 1, 2, and 4.

    */

TEST.H

   #include <stdio.h>

TEST1.C

   #include "test.h"

TEST2.C

   #include "test.h"

   void test2func(void)

   {

      printf("inside TEST2FUNC...\n");

   }

TEST3.C

   #include "test.h"

   void test2func(void);

   void main(void)

   {

      printf("inside MAIN...\n");

   }

Change the app.config or machine.config when the application that uses them is running.

Result

The application will not be able to read these changes, and the new changes made to the .config files will not be reflected in the application.

Cause

.NET Framework will read the .config file once at application startup and then not read them again during that session.

Resolution

Restart the application so it can read these changes.

More Information

App.Config reloading (http://blogs.msdn.com/junfeng/archive/2005/02/20/376880.aspx)
Machine.Configuration Files (http://msdn2.microsoft.com/en-us/library/ms229697.aspx)

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks