With the announcement of Google Music and of course having multiple Android Phones I wanted to keep my music in one location.  With the help of some Google searches I found some steps on the Amazon Kindle forums that worked perfectly, modified slightly for what I needed to do in order to get it working.

1. SideLoad: GoogleServicesFramework.apk and Books.apk
2. Reboot the Kindle Fire
3. Start the book Application and set it up to sync with your google account.
4. Once the sync is complete, Reboot the Kindle Fire again
5. Side Load Music.apk
6. Start music application and it should sync
7. (optional) uninstall books, I left it, never know if Google will get something good and it is small enough anyways

So far in my experience after the initial sync it does not appear to auto sync.  If you experience this also, you can go into settings and force a re-sync.

Silverlight5Demo

Please visit Silverlight.net to get a full list of what’s new. (my demo only scratches the surface.

Silverlight Show web site is also a great resource.

What do you need to accomplish this?

A .NET project

Download the ODAC xcopy version (as of this article the latest was 11.2.0.2.1)

• Oracle Data Access Components (ODAC) Downloads

Copy the following dll’s from the ODAC folder to either the bin (if web) or location of the exe file

• oci.dll (Client Code Library)
• ociw32.dll
• Oracle.DataAccess.dll
• orannzsbb11.dll (Security Library)
• oraocci11.dll (OCCI Library)
• oraociei11.dll (OCI Instant Client Data shared Library)
• OraOps11w.dll

You can create your tsanames.ora from either code or in web.config

string Connstring = "Data Source=(DESCRIPTION=" +
   "(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)" +
   "(HOST=serverName)" +
   "(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)" +
   "(SERVICE_NAME=DatabaseName)));" +
   "User Id=UserName;Password=UserPassword;";

Then just create your open connection like normal

Here is an example solution.

OracleTest.zip

What would happen, if you would place the form into edit mode, then execute the filter method you will get an error that filter cannot be done while in AddNew or Edit mode.

To solve this you can detect if the collection is in one of those modes and either confirm or cancel the changes.

if (MyCollection is IEditableCollectionView)
{
    var MyCollectView = MyCollection.View as IEditableCollectionView;

    if (MyCollectView.IsAddingNew)
    {
        MyCollectView.CommitNew();
    }
    if (MyCollectView.IsEditingItem)
    {
        MyCollectView.CommitEdit();
    }
}

Sometimes debugging web applications with service calls can be … well… fun when you want to see what happens to your app when the service is unreachable.

For web applications Console.Writeline() is not an option, and while System.Diagnostics.Debug.WriteLine() works. I typically still get an exception in the service request and I am not 100% sure that the end user will not see the same thing.

Here’s what I did.

Create a static class and name it something simple like Log.cs

Add a static method like so

public static void Logs(this object obj)
        {
            HtmlWindow window = HtmlPage.Window;
            var isConsoleAvailable = (bool)window.Eval("typeof(console)" +
                    " != 'undefined' && typeof(console.log) != 'undefined'");
            if (isConsoleAvailable)
            {
                var console = window.Eval("console.log") as ScriptObject;
                if (console != null)
                {
                    console.InvokeSelf(obj);
                }
            }
        }

Now anywhere in your application you can call .Logs() like so

if(debugCheck)
    {
        "ClientPingCompleted".Logs();
        var error = "return error : " + e.Error;
        error.Logs();
    }

In the browser console you will see this.

I regularly get an error when I take my notebook from home to work. For some reason Live Mesh chokes on network settings when I switch from a network (work) with a proxy server and home where I have no proxy server.

With the help of some searching on the windows live help sight I was able to put together a PowerShell script that will reset the services that deal with Live Mesh and restart the application.

cls
netsh winhttp import proxy source=ie

Write-Host "Restarting Windows Live ID Sign-in Assistant"
Restart-Service wlidsvc -Verbose
$srvName = "wlidsvc"
$servicePrior = Get-Service $srvName
$srvName + " is now " + $servicePrior.status

Start-Sleep -Seconds 2

Write-Host "WinHTTP Web Proxy Auto-Discovery Service"
Restart-Service -DisplayName "WinHTTP Web Proxy Auto-Discovery Service" -Verbose
$srvName = "WinHTTP Web Proxy Auto-Discovery Service"
$servicePrior = Get-Service -DisplayName $srvName
$srvName + " is now " + $servicePrior.status

Write-Host "Starting LiveMesh"
Invoke-Item "C:\Program Files (x86)\Windows Live\Mesh\WLSync.exe"

Install the Lync 2010 x64 client to your Windows 7 machine. You can download a trial version here. However I would recommend that you get it from your local administrator, and double check to make sure they will not kill you doing this to a company machine.

Once install add the following to the registry otherwise you will get a versioning check error:

Note: Notice that we are still using DWORD on x64 instead of QWORD. At the time of this Article you have to use DWORD.

Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator
Name:  DisableServerCheck
Type: DWORD
Value: 1 (00000001)

Once done, start Lync 2010 and you should be good to go.

http://www-01.ibm.com/support/docview.wss?uid=swg24028317

http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14552668

_______________________________________________________________________

So I ran into this error this week on our Server 2008 R2. So after a few days of troubleshooting I did find where the issue was. It appears that on 64 bit OS’s during installation of the DB2 32 bit client calls machine.config incorrectly.

So to fix this, you need to update machine.config manually.

1. Open machine.config in a text editor (notepad ++) as administrator

For .NET 2.0 to 3.5 
• C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config

For .NET 4.0 
• C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config

2. Add the following lines to <DbProviderFactories> of course correct for the version you are using. For this example I am using IBM DB2 .NET Data Provider 9.7.0

<add name="IBM DB2 .NET Data Provider" invariant="IBM.Data.DB2" description="IBM DB2 Data Provider for .NET Framework 2.0" type="IBM.Data.DB2.DB2Factory, IBM.Data.DB2, Version=9.0.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208" />
<add name="IBM Informix .NET Data Provider" invariant="IBM.Data.Informix" description="IBM Informix Data Provider for .NET Framework 2.0" type="IBM.Data.Informix.IfxFactory, IBM.Data.Informix, Version=9.0.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208" />
<add name="IBM DB2 .NET Data Provider 9.7.0" invariant="IBM.Data.DB2.9.7.0" description="IBM DB2 Data Provider 9.7.0 for .NET Framework 2.0" type="IBM.Data.DB2.DB2Factory, IBM.Data.DB2.9.7.0, Version=9.7.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208" />
<add name="IBM Informix .NET Data Provider 9.7.0" invariant="IBM.Data.Informix.9.7.0" description="IBM Informix Data Provider 9.7.0 for .NET Framework 2.0" type="IBM.Data.Informix.IfxFactory, IBM.Data.Informix.9.7.0, Version=9.7.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208" />

3. Verify that you have IBM.Data.DB2 listed in <runtime> if not add the following. Again modify to the version you are installing

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="IBM.Data.DB2" publicKeyToken="7c307b91aa13d208" culture="" />
        <bindingRedirect oldVersion="8.1.2.0" newVersion="9.0.0.2" />
        <bindingRedirect oldVersion="8.1.2.1" newVersion="9.0.0.2" />
        <bindingRedirect oldVersion="9.0.0.1" newVersion="9.0.0.2" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="IBM.Data.Informix" publicKeyToken="7c307b91aa13d208" culture="" />
        <bindingRedirect oldVersion="3.0.0.2" newVersion="9.0.0.2" />
        <bindingRedirect oldVersion="2.81.0.0" newVersion="9.0.0.2" />
        <bindingRedirect oldVersion="9.0.0.1" newVersion="9.0.0.2" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="IBM.Data.DB2.9.7.0" publicKeyToken="7c307b91aa13d208" culture="" />
        <bindingRedirect oldVersion="9.7.0.1" newVersion="9.7.0.2" />
        <codeBase version="9.7.0.2" href="C:\Program Files\IBM\SQLLIB\bin\netf20\specific\IBM.Data.DB2.9.7.0.dll" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="IBM.Data.Informix.9.7.0" publicKeyToken="7c307b91aa13d208" culture="" />
        <codeBase version="9.7.0.2" href="C:\Program Files\IBM\SQLLIB\bin\netf20\specific\IBM.Data.Informix.9.7.0.dll" />
      </dependentAssembly>
    </assemblyBinding>
</runtime>

4. After that save, reboot and things should start working.

Using Visual Studio Build Solution:

1. Open Visual Studio  (I am using VS 2010)

2. Right your project
3. Highlight Add
4. Select New Item

5.Select Application Manifest File
6. Change the name to match the name of the exe.

• Example someProgram.exe.manifest

7. Click ‘Add’
8. Open the manifest file and look for the line requestedExecutionLevel

• Default line will probably look like this:
        <requestedExecutionLevel level="asInvoker" uiAccess="false" />

9.Replace this line with:
      <requestedExecutionLevel  level="requireAdministrator" uiAccess="false" />

10. Save the changes
11. Open the project properties
12. Under Application locate the Manifest drop down

13. Your manifest may already be selected. if not click the arrow and select.
14. Save your changes
15. Rebuild your solution.

Your application should now launch the Yellow UAC box requesting admin privileges.  If you want to get rid of the yellow box you will need to code sign the exe.

Using Windows SDK MT.exe:

By default if the Windows SDK is installed (if not install it) the MT.exe is located in C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin

1. First thing you need to do is create the manifest file.  It is a simple XML file that looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <assemblyIdentity version="1.0.0.0"  name="someProgram.EXE" type="win32"/>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="requireAdministrator"/>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

2. Set the name to be the name of the exe file, in this example it is someProgram.exe
3. Verify that you have the tag:
      <requestedExecutionLevel level="requireAdministrator"/>
4. Save your changes
5. Bring up cmd.exe as Administrator
6. run the following command (this is one line, to make it easier to read I broke it down to two lines):

7. It should return that it was successful and you should not have an exe that will launch using the UAC.

Few things to note about this process:

• mt.exe can be copied out of the sdk and moved to a different folder
• I have successfully written a PowerShell script that will look for all exe files, check a different folder that stores the manifest files. If it exist it runs this command.

Here is what you do: (this also works if you forget your admin account password)

1. Boot into Single user mode by holding down Command-S (apple-S).
2. Issue the following commands
   

   • mount -uaw
   • cd /var/db
   • rm .applesetupdone

   Note: The hidden file you are deleting is what OSX uses to record if the initial setup was done. By deleting this file you are in essence telling OSX that the setup process was not done and to do it again.

3. Reboot by typing reboot
4. Listen to the warm and fuzzy music and register a new temporary user account.
5. You should now be able to log in and backup your files under the new account.