Here is a list of resource available online on Internet for Duet.

Duet official Website: http://www.Duet.com

Duet Home Page on MICROSOFT.COM: http://www.microsoft.com/Duet

Duet on TechNet: http://technet.microsoft.com/office/bb267348.aspx

See online Duet Demo: Duet online Demo

Some Duet blogs:

• Blog by Duet Team
• http://msftduet.spaces.live.com/
• Patrick's Blog
• Eran Kampf's Blog

Some of our duet customers are facing problem while installing Duet Request Handler. So I thought of writing the installation procedure to help them out.

Here is the first screen that come up when you run the Setup file and Click Next

In the designated account text box you have to enter the user name in the form of domain\user. This domain account will be used to send the mail messages from the exchange server.

Enter the domain user's password in the Password text box and the name of the exchange server in the Exchange server text box.

Note : If your exchange server is serving webdav at some other port than 80 please specify port number with the exchange server. Exchange server name should be exactly the same where your mailbox is residing.

e.g.

Exchange Server:
exchangerServer:8081

Setup validates the domain account in the active directory and attempts to send webdav request to the exchange server. If any of these steps fails it will not allow the user to continue.

You can specify the Port number where you want request handler to be running in the next screen. (Note: setup only creates the virtual directory. You should create a different website yourself if you dont want the request handler to run in the default website)

If everything goes fine you are ready to install. Click next and you are done.

Troubleshooting: If it throws a message saying "Designated account credentials could not be authenticated" you should:

• Make sure you entered the correct username and password.
• Check if the user exist in the AD and exchange server.
• Make sure machine is connected and added to the appropriate domain and you have access to the exchange server machine.
• Make sure your are logged on to the machine using the domain credential not (local machine credentials).
• Make sure username and password doesn't contain space characters in the start and the end.
• Check if user has access to Global catalog (GC).
• Check if webdav service is enabled on the exchange server. Try to access http://exchangeserver:port/exchange/user using the credential you specified in the setup screen. If you can't access it, that means you probably have some issue with exchange server configuratuin and contact your admin to configure exchange server for the necessary setup and permissions.
• Make sure windows authentication is enabled on the exchange server.
• Forms based authentication is not supported in this version of the request handler.

It’s a great feature that I’m trying to test from within Word 2007. Now I don’t need to go to the blogging portal or use some other blogging tool. I can just write/edit in the word and click publish. Wow Cool product. You can write your blog post from Word. What else do a blogger need?

Kudos to Word team they have done a nice job. It has a cool look some big icons I’m not familiar with(but they looks good).

If I could publish this post successfully I’m not gonna use any other tool for blogging and I’m sure you won’t either.

One of the very few example where you just can't search MSDN or Google or MSN and hope to find the answer. For me it was the following exception when calling

Assembly.Load(aseemblyName, evidence);

System.IO.FileLoadException occurred
 Message="Could not load file or assembly AssemblyName, Version=1.1.0.0' or one of its dependencies. Cannot specify assembly evidence under MultiDomain after non-GAC assemblies with default evidence have been loaded in appdomain. (Exception from HRESULT: 0x8013101D)"
Source="mscorlib"
FileName="AssemblyName, Version=1.1.0.0"
FusionLog=""
StackTrace:
       at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
       at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
       at System.Reflection.Assembly.Load(AssemblyName assemblyRef, Evidence assemblySecurity)
       at Microsoft.InformationBridge.Framework.ExecutionEngine.Utility.LoadAssembly(AssemblyName assemblyName)

Now after spending lots of time with installting uninstalling several things with no result. I decided to go into the details. After reading the exception message once again it was all clear. Clearly some Non-Gac assembly was loaded in my host application (in my case it was outlook) with the default evidences. So all I need to do was to look for such assemblies not loading from gac. Fortuanately it was only one for me and I knew it was some addin which was quite useful for us. With a little hope I disabled it and restart outlook. Wow it worked now with no exception.

Lesson: If you encounter above exception just check which idiot extensions are enabled which are preventing you from loading your assemblies (.Net ones) and disable them.(Of course this is just a workaround but if you dont have any other way till then....)

If you find out the solution to this problem please let me know.

MSDN subscribers will now be able to download and install any one of the retail versions of the Visual Studio family of products from the MSDN subscription site. Also available are .NET framework and .NET Framewrok SDK from Microsoft download center.
So dont wait and start using VS 2005 ............. :)

If you are not able to see AERO glass theme on your Windows Vista beta because you have an Intel Graphics card not a nVidia one. Here is small trick for you. Just make some modification in registry and thats it.... Enjoy

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DWM]
"EnableMachineCheck"=dword:00000000
"Animations"=dword:00000000
"Blur"=dword:00000001


Recently I came across a problem with Outlook PIAs. I used the Outlook library to access the Outlook Object Model. If the outlook is already running then there is no problem. But if this is not the case trying to access Application object creates a new process that's fine but when I release my objects, process is still running. At first tried tried releasing all the objects using Marshal.ReleaseComObject() but process is still there.

Code snippet is posted below

Outlook.MAPIFolder inboxFolder = mapiNamespace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderInbox);
Outlook.Items items = inboxFolder.Items;
foreach (Outlook.MailItem mailItem in items)
{
    if (mailItem.Subject == SubjectName) 
      { //do something                     
     }
    Marshal.ReleaseComObject(mailItem);
}
Marshal.ReleaseComObject(items);
Marshal.ReleaseComObject(inboxFolder);

So basically I released all the objects that i thought I was adding a reference to. But process is still there. Then I found the glitch. foreach loop is generating some intermediate reference so ref count to the com object is not decreased as it should therefor outlook process is still there even no one actually is using this.

 Here is the modified code to correct the error

Outlook.MailItem item = null;
Outlook.Items items = mailFolder.Items;
for (item = (Outlook.MailItem)items.GetFirst(); item != null; item = (Outlook.MailItem)items.GetNext())
{
    if (item.Subject == SubjectName) { //do something; }
   Marshal.ReleaseComObject(item);
}
 Marshal.ReleaseComObject(items);

It should work fine at least working at my Desktop :)

Microsoft Codename MAX is available for download at following link.

http://www.microsoft.com/max/ Built upon WinFX technology this is just a demo of the power Avalon provides to the user and developer.

So be ready for the future.

Hi,

This is my first post at MSDN blogs. I'm a part of Mendocino development team. This project is a joint partnership of SAP and Microsoft.

Just went through the Cool Client Stuff. Cool feature provided by Whidbey. More beautiful and more powerful.

Enough for Today.

More technical stuff another day.

;-)Just found a bug at this blog ( Low priority ), but I don't know where to report it. If anybody knows please post a comment...........