.comment-link {margin-left:.6em;}


.. Hello Earthling .. \o/ :)

Building Rotor 1.0 with Whidbey Beta 2
Friday, September 30, 2005

I recently built rotor 1.0 with visual studio .net 2005 (whidbey) beta 2. Thanks to Barry and Lorenzo for helping me out do this. You can read the posts on discuss.develop. I created a little patch which you can just paste over your sscli directory and than build again and than everything should be working fine. The build is done on Windows 2000 pro sp4. The things that I tested are C# compiler, clix, few samples, ilasm, ildasm, and cordbg. I have to do some more work on the patch cuz it contains a lot of redundant files. When it'll be done I'll let everyone know at rotor newsgroup at discuss.develop. If you need it earlier than that and dont have any problem with working with the rough version of the patch you can just email me and I'll send you the zip file containing the necessary things. Its around 700k. I'm used to building sscli piece-by-piece ie: building pal, than build.exe, than binplace, than resourcecompiler, than palrt, than \clr\src .... and so on. I think u'll have to do the same or I may include a batch file to do so. But instructions will be easy to follow.

Treo is now Powered by Windows :-)
Monday, September 26, 2005

Palm to release there latest Treo 700w based on Windows operating system. Thats the way to go Palm !

I cant do "this.Cursor" !!!
Monday, September 12, 2005

Yea I know. In .net compact framework you cant do a this.Cursor to set a cursor for your window. Instead its hidden in System.Windows.Form.Cursor (static style !!!!!):

System.Windows.Forms.Cursor.Current = Cursors.WaitCursor;
System.Windows.Forms.Cursor.Current = Cursors.Default ;

Oh btw, just a little tip for using whidbey beta2 IDE: you can access "Surround" feature through keyboard by Ctrl+K+S, and "Insert Snippet" by Ctrl+K+X. Makes writing code pretty fast.

Generating Guids on a Pocket PC
Friday, September 09, 2005

In the .net compact framework 1.0 if you want to generate a GUID, there is no class/struct that can help you do that. So you have to come up with your own ways. One good example can be found in this article on msdn. Now in the latest .net cf version 2.0, the System.Guid struct has been added which works just like its desktop counterpart.

Now why would u want to generate guids while programming for pocket pc? Thats a long (actually short) story that I'll blog about some time in the future.

WinFS Beta 1 released
Thursday, September 08, 2005

Read again its not WinFX, it WinFS: The file system/platform. Its located here. This is the blog site. But only available for msdn subscribers :(.

Pocket PC Emulator; Sharing files on desktop, and ActiveSync connectivity
Monday, September 05, 2005

(All following information is valid for viusal studio.net 2005 beta 2)
Accessing Desktop files on Pocket PC Emulator: While developing the pocket pc apps on emulator you may want to manually copy files to the emulator's memory if for some reason you cant do it through activesync. Its really simple. While pocket pc emulator is running, through the File menu, click "configure". On the first "General" tab you'll see a "Shared folder" text box. Simply give the path where you want to share files. This path actually becomes your storage card on emulator. Now the files that you place in the shared folder can be accessed through the pocket pc "File Explorer"'s "storage card" icon at the bottom of file explorer.

Emulator's Connectivity with ActiveSync: As I looked for this information, the community is using ActiveSync 4.0 for emulator's connectivity. This link is important for all these downloads. As the page suggests, you need to download ActiveSync 4 and the DMA update patch. What the patch does is carries out all the emulator, vs.net, and active sync communications through DMA instead of doing it with tcp/ip. Microsoft says its a more efficient way of communications which utilizes COM. And if you are also facing this problem of not being able to debug your apps on vs.net, this dma download should fix this problem (btw the dma download is like 80+ mb!) Now all communications settings should be using DMA. In vsnet 2k5, goto Tools->Options. Select "Device tools" and select "Devices". Select your device/emulator from the "Devices" listbox and click properties. "Trasposrt" drop down should be set to DMA. If you now click "Emulator Options" button on the same dialog, goto "network" tab and on my network tab nothing is checked, so I recommend that you also uncheck all the checkboxes if any is selected. Click all the Ok buttons! Now in your activesync File menu: click the "connection settings". The drop down that mentions "allow connections to one of the following", should have DMA selected. I think now everything is done in case i've not missed any detail. Restart your emulator (maybe soft resetting it, you wont lose any settings or data, or just close and open again). After restarting your emulator goto vsnet's Tools->"Device Emulator Manager". In the Available emulators you'll see the one you are using and a play icon with it. Means its running. Now right-click it and click on "Cradle". This will emulate as if you have placed your device on the cradle, just like you will do with a physical device. Now the activesync should be active and in few seconds connected to your emulator. If you are not connected, try restarting things, it should work.


MSDN Blogs
Joel Pobar
Don Syme

Muhammad Ali
Lahore Food Blog

Tech Blog



June 2004   July 2004   August 2004   September 2004   October 2004   November 2004   December 2004   February 2005   April 2005   June 2005   July 2005   September 2005   October 2005   November 2005   June 2007   December 2007   January 2008   March 2008   April 2008   June 2008   October 2008   February 2009   May 2009   June 2009   July 2009   August 2009   March 2011   June 2011   July 2011   September 2011   October 2011   November 2011   December 2012   May 2013   October 2013   May 2014   March 2015   July 2015   August 2015   December 2015   March 2016   July 2016   October 2016   November 2016  

This page is powered by Blogger. Isn't yours?