<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="www.w3.org/2005/Atom" xmlns:sy="purl.org/rss/1.0/modules/syndication/" xmlns:dc="purl.org/dc/elements/1.1/" xmlns:content="purl.org/rss/1.0/modules/content/" xmlns:wfw="wellformedweb.org/CommentAPI/" xmlns:slash="purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Windows Developer 101</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/dswl/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/dswl/feed.xml</link>
    <description />
    <lastBuildDate>Tue, 16 Apr 2019 05:05:51 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Make Device Emulator connected to Internet</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/make-device-emulator-connected-to-internet</link>
      <pubDate>Wed, 14 Apr 2010 04:50:43 GMT</pubDate>
      <dc:creator><![CDATA[Terry Wei]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/04/14/make-device-emulator-connected-to-internet/</guid>
      <description><![CDATA[This a post about how we can surf the Internet on Device Emulator. I do a little summary and hope...]]></description>
      <content:encoded><![CDATA[<p>This a post about how we can surf the Internet on Device Emulator. I do a little summary and hope the information below is helpful.</p>  <p>Download the Windows Mobile SDK first, you can download the needed version SDK from <a href="https://www.microsoft.com/downloads/en/default.aspx">Microsoft Download Center</a>.</p>  <h5>1. Virtual Machine Network Services</h5>  <p>Make sure Virtual Machine Network Services is installed on your machine. If not, please install virtual PC first. If you don’t want to install VPC but still want the service, usually what I do, is to get the installation files from VPC installation program.</p>  <p>On device emulator, click File –&gt; Configure… –&gt; Network, toggle the option “Enable NE2000 PCMCIA network adapter and bind to:”. Then click OK.</p>  <p>Wait for a while, you can see the network connection notification appeared on Windows Mobile device emulator.</p>  <p>&#160;</p>  <h5>2. ActiveSync or WMDC (Windows Mobile Device Center)</h5>  <p>I will take ActiveSync for example. Open ActiveSync, click File –&gt; Connection Settings…. Make sure “Allow connections to one of the following:” is toggled. Select the down list with “DMA”. Then click OK.</p>  <p>Open Device Emulator Manager under C:\Program Files\Microsoft Device Emulator\1.0\dvcemumanager.exe, find your device emulator instance and right click your mouse. Select “Cradle” item on the context menu. </p>  <p>Wait until ActiveSync is connected. </p>  <p>&#160;</p>  <h5>3. Using Cellular Emulator</h5>  <p>First, make device emulator and cellular emulator connected, you can refer to my post here: <a href="https://blogs.msdn.com/dswl/archive/2010/04/04/make-device-emulator-and-cellular-emulator-connected.aspx">Make Device Emulator and Cellular Emulator connected</a>.</p>  <p>Then, create a GPRS connection on device emulator. Open IE and view a website, the GPRS connection will automatically be connected.</p>  <p>&#160;</p>  <p>If you have any other useful tips, please feel free to share with me. Any comment is welcome.</p>]]></content:encoded>
    </item>
    <item>
      <title>How to copy files to Windows Mobile device</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/how-to-copy-files-to-windows-mobile-device</link>
      <pubDate>Sat, 10 Apr 2010 01:00:52 GMT</pubDate>
      <dc:creator><![CDATA[Terry Wei]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/04/10/how-to-copy-files-to-windows-mobile-device/</guid>
      <description><![CDATA[When I first used Windows Mobile device, I just wonder how I could copy files to this small device....]]></description>
      <content:encoded><![CDATA[<p>When I first used Windows Mobile device, I just wonder how I could copy files to this small device. It is really a annoying thing. I think many beginners may have the same experience. At this post, I just make a little summary about different ways of copy files to WM device.</p>  <p>&#160;</p>  <h5>1. Storage Card</h5>  <p>If your Windows Mobile device support storage card, copy what you want to storage card first and put the card into Windows Mobile device slot. Then you can view the files from file explorer on Windows Mobile device.</p>  <p>&#160;</p>  <h5>2. ActiveSync or WMDC (Windows Mobile Device Center)</h5>  <p>Download the latest software (ActiveSync or WMDC) from <a href="https://www.microsoft.com/downloads/en/default.aspx" target="_blank">Microsoft Download Center</a>. Then make your Windows Mobile device connected with PC via Bluetooth, USB or IR port. When ActiveSync or WMDC connected, open file explorer on PC side and you can view the file system on Windows Mobile device. Then copy, paste files to Windows Mobile device just like operations on PC folders.</p>  <p>&#160;</p>  <h5>3. Beem files</h5>  <p>Beem files from/to Windows Mobile device via Bluetooth or IRDA. This way can be used for file transfer between devices or PCs.</p>  <p>&#160;</p>  <h5>4. USB mass storage mode</h5>  <p>When connect Windows Mobile device to PC, make your Windows Mobile device a USB mass storage device. Then copy files to Windows Mobile device just like a USB flash.</p>  <p>&#160;</p>  <p>If you have any other ways, it is welcome to post here. Enjoy.</p>]]></content:encoded>
    </item>
    <item>
      <title>Make Device Emulator and Cellular Emulator connected</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/make-device-emulator-and-cellular-emulator-connected</link>
      <pubDate>Sun, 04 Apr 2010 02:28:14 GMT</pubDate>
      <dc:creator><![CDATA[Terry Wei]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/04/04/make-device-emulator-and-cellular-emulator-connected/</guid>
      <description><![CDATA[Cellular Emulator is a very useful tool to simulate the phone functions. Then how to connect it with...]]></description>
      <content:encoded><![CDATA[<p>Cellular Emulator is a very useful tool to simulate the phone functions. Then how to connect it with device emulator? Here we go!</p>  <p>&#160;</p>  <p>1. Install the Windows Mobile 6 SDK, you can download it from <a title="www.microsoft.com/downloads/en/default.aspx" href="https://www.microsoft.com/downloads/en/default.aspx">www.microsoft.com/downloads/en/default.aspx</a>.</p>  <p>2. Launch the Cellular Emulator and Device Emulator. </p>  <p>3. Double check the Cellular Emulator and remember the string at the lower left corner, like “DE: COM3”.</p>  <p>4. Click the menu at Device Emulator, File –&gt; Configure… –&gt; Peripherals, then put the string information got from step 3 into “Serial port 0:”, like “COM3”. And click OK.</p>  <p>5. Soft reset the Device Emulator by clicking File –&gt; Reset –&gt; Soft.</p>  <p>6. Open the Cellular Emulator, in the AT log window, you can see lots of AT logs. It shows that you have made Device Emulator and Cellular Emulator connected!</p>  <p>&#160;</p>  <p>Some other guys may ask the question “when I generate a image using Platform Builder, why this did not work any more?”, now here I could give some suggestions:</p>  <p>1. Make sure the following environment variables are set before you run the command MAKEIMG.</p>  <p>SET IMGEMP=1</p>  <p>SET IMGDUALPORTRIL=1</p>  <p>SET IMGFAKERIL=</p>  <p>2. When you reboot the device emulator at step 5, please also reset Cellular Emulator connection by clicking Configuration –&gt; Reset.</p>  <p>&#160;</p>  <p>Try use it and make a good use of Cellular Emulator. It is a good simulation environment to test some applications on device emulator. For some phone function testing scenarios, this test environment may not probably accurate. But this is still an easy, quick test tool and worth a try!</p>]]></content:encoded>
    </item>
    <item>
      <title>Getting Start with Windows Phone 7</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/getting-start-with-windows-phone-7</link>
      <pubDate>Sun, 21 Mar 2010 00:37:10 GMT</pubDate>
      <dc:creator><![CDATA[Terry Wei]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/03/21/getting-start-with-windows-phone-7/</guid>
      <description><![CDATA[Hello everybody! Now here we come Windows Phone 7!  This post list some useful resources for all...]]></description>
      <content:encoded><![CDATA[<p>Hello everybody! Now here we come Windows Phone 7!</p>  <p>This post list some useful resources for all WPers. Enjoy!</p>  <p>&#160;</p>  <p>Windows Phone 7 Series:&#160; <a href="www.windowsphone7series.com/" target="_blank">Go!</a></p>  <p>Windows Phone for Developers:&#160; <a href="developer.windowsphone.com/Default.aspx" target="_blank">Go!</a></p>  <p>Windows Phone Developer Tools CTP:&#160; <a href="https://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=2338b5d1-79d8-46af-b828-380b0f854203" target="_blank">Go!</a></p>  <p>Windows Phone 7 Training Kit for Developers:&#160; <a href="https://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=ca23285f-bab8-47fa-b364-11553e076a9a" target="_blank">Go!</a></p>  <p>OData Client Library for Windows Phone 7 Series CTP:&#160; <a href="https://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=b251b247-70ca-4887-bab6-dccdec192f8d" target="_blank">Go!</a></p>  <p>&#160;</p>  <p>Here’s a list of key forums you can visit: </p>  <p>&#160;</p>  <p>General Windows Phone developer support:&#160; <a href="https://social.msdn.microsoft.com/Forums/en-US/category/windowsphone">Go!</a></p>  <p>Silverlight for Windows Phone: <a href="forums.silverlight.net/forums/63.aspx">Go!</a></p>  <p>XNA for Windows Phone: <a href="forums.xna.com/forums/default.aspx?GroupID=6">Go!</a></p>  <p>Stackoverflow.com:&#160; <a href="stackoverflow.com">Go!</a></p>  <p>&#160;</p>  <p>Let's ROCK IT!</p>]]></content:encoded>
    </item>
    <item>
      <title>How to capture network traffic on Windows Embedded CE 6.0</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/how-to-capture-network-traffic-on-windows-embedded-ce-6-0</link>
      <pubDate>Tue, 02 Mar 2010 08:35:05 GMT</pubDate>
      <dc:creator><![CDATA[Terry Wei]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/03/02/how-to-capture-network-traffic-on-windows-embedded-ce-6-0/</guid>
      <description><![CDATA[As we know, when we investigate network related issues, we can capture the network monitor log on PC...]]></description>
      <content:encoded><![CDATA[As we know, when we investigate network related issues, we can capture the network monitor log on PC side. Just as Emma said <a href="https://blogs.msdn.com/dswl/archive/2010/01/05/how-to-capture-network-traffic-with-microsoft-network-monitor.aspx" target="_blank">here</a>. But on CE side, we also have a tool to capture the network traffic. People can use this tool to capture the network traffic on CE side and copy the log file to PC, then use the Microsoft Network Monitor to view the log.   <p>OK. Let me show something about how to ………</p>  <p>&#160;</p>  <p>&#160;</p>  <h5>1. Make sure the netlogctl.exe and netlog.dll are in your image.</h5>  <p>Before you build the whole solution, please make the “NDIS Packet Capturing DLL” item selected in your OS design.</p>  <p>Opps…People may forget to add this item to OS design and they don’t want to rebuild the whole solution since it is much time consuming…Never mind buddies. We have one method to generate the needed modules to our FRD.</p>  <p>&#160;</p>  <p>a. Open a command line window by clicking Build –&gt; Open Release Directory in Build Window.</p>  <p>b. Type “SET WINCEREL=1”, then click enter.</p>  <p>c. Type “sysgen –p common netlog”, then click enter to generate the netlog.dll module.</p>  <p>d. Type “sysgen –p common netlogctl”, then click enter to generate the netlogctl.exe module.</p>  <p>e. Finally, you can find the two modules under your solution’s FRD.</p>  <p>&#160;</p>  <p>&#160;</p>  <h5>2.&#160; Type commands in target control window.</h5>  <p>This tool is a command line tool. Hence, I use it in the target control window (This situation is under KITL enabled scenario).</p>  <p>Type command as below to start the capturing:</p>  <p><strong>s netlogctl load</strong></p>  <p><strong>s netlogctl start</strong>&#160;</p>  <p>&#160;</p>  <p>Type command as below to stop the capturing:</p>  <p><strong>s netlogctl stop</strong></p>  <p><strong>s netlogctl unload</strong></p>  <p><strong></strong></p>  <p>Then the log files can be found under the root directory. </p>  <p>For more information about the command line, please refer to the <a href="https://msdn.microsoft.com/en-us/library/aa926774.aspx" target="_blank">MSDN Netlogctl</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>How to capture a Process Monitor trace</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/how-to-capture-a-process-monitor-trace</link>
      <pubDate>Sun, 10 Jan 2010 00:29:33 GMT</pubDate>
      <dc:creator><![CDATA[Emma Mou]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/01/10/how-to-capture-a-process-monitor-trace/</guid>
      <description><![CDATA[When working with Microsoft technical support on a service request, you might be asked to capture a...]]></description>
      <content:encoded><![CDATA[<p>When working with Microsoft technical support on a service request, you might be asked to capture a Process Monitor(ProcMon)&#160; trace. Process monitor can capture real-time file system, registry and process/thread activity, including the target object path, the access type, the name of the process that takes the action and its identity, the operation result, etc. This trace is especially useful to troubleshoot problems like file/registry-entry missing or access denied. </p>  <p>To capture a ProcMon trace you can go</p>  <ol>   <li>Download Process Monitor tool from <a href="https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx">here</a>, then install it on the machine being traced. </li>    <li>Double-click to launch the tool (Note on Vista or Windows 2008 OS this tool runs with elevated privileges. ), data collection starts automatically and you will see new records adding into the main form. </li>    <li>Now you operate on the&#160; machine to reproduce the problem to be traced. </li>    <li>When all data is collected, press Ctrl+E to stop tracing. </li>    <li>Go File-&gt;Save, then save the trace into a .pml file. </li> </ol>  <p>Tips:</p>  <ul>   <li>By default procmon data collection is backed up by page files before the data is saved into a file on the disk. Yet if the collection will go for a long time, or you want to save the page files for other applications, go to “File”-&gt;”Backing File” and change the storage to a file on local disk. </li>    <li>Process monitor supports many kinds of filters for both collecting and data analyzing. My suggestion is when collecting data you use the default filter set , then choose “all events” when saving data—unless you know clearly that only a special part of the data is being interested. </li>    <li>Process monitor keeps the filter set used in last time. So before any collection starts, go “Filter”-&gt;”Reset Filter” to restore the default filter set. </li> </ul>  <p>Reading &amp; analyzing a procmon trace is not covered in this post. You can find a lot in the “Additional Resources” part in the procmon download page;</p>]]></content:encoded>
    </item>
    <item>
      <title>How to capture network traffic with Microsoft Network Monitor</title>
      <link>https://docs.microsoft.com/archive/blogs/dswl/how-to-capture-network-traffic-with-microsoft-network-monitor</link>
      <pubDate>Tue, 05 Jan 2010 02:16:56 GMT</pubDate>
      <dc:creator><![CDATA[Emma Mou]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/dswl/2010/01/05/how-to-capture-network-traffic-with-microsoft-network-monitor/</guid>
      <description><![CDATA[When investigating network related problems, you can use Microsoft Network Monitor tool to capture,...]]></description>
      <content:encoded><![CDATA[<p>When investigating network related problems, you can use Microsoft Network Monitor tool to capture, view and analyze network traffic. It is a powerful protocol analyzer.&#160; This post is based on the latest release : Network Monitor 3.3. </p>  <ol>   <li>Download the tool from <a href="https://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&amp;displaylang=en">here</a> , install it on the machine that you want to run the capture—it should be a partner in the network conversation. Double-click to run the tool; </li>    <li>In the left-upper side panel, click on “Create: New capture tab…”. A new capture tab opens; </li>    <li>In the right-hand “Select Networks” view, select the network adaptor that you want to capture on;&#160; This can be a multiple choice. </li>    <li>Now click the “start” icon on the tool bar, or press F5 to start capture. You can see the “Frame Summary” view being populated with new frames. </li>    <li>When the interested data is collected, stop tracing by clicking the “Stop” icon in the tool bar , or click F7. </li>    <li>Go to File-&gt;SaveAs to save the captured frames. Besides the file path, you can also define what to be saved by using the the “Frame selection” list . </li> </ol>  <p>Tips:</p>  <ul>   <li>How to view and analyze the network monitor trace is not covered by this post. You can find “Related Resources” in the <a href="https://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&amp;displaylang=en">network monitor download page</a> .&#160; </li>    <li>A good practice is to capture with no filters, and save “All captured frames” to avoid missing anything useful in the trace, unless you know clearly that you are interested in a specific part of the trace only. </li>    <li>If VPN is involved in the interested traffic, make sure “WAN Miniport” is included in step 3 above; </li> </ul>  <p>You can also check out some other useful network sniffers like <a href="www.fiddler2.com/fiddler2/">Fiddler</a> and <a href="www.wireshark.org/download.html">WireShark</a>. </p>]]></content:encoded>
    </item>
  </channel>
</rss>