Microsoft.Ink.dll and CLR that ships in VS.NET 2005 Part 2
We've finally got a repackaged SDK that has the updated Microsoft.Ink.dll in it that is compatible with CLR 2.0.
http://download.microsoft.com/download/7/7/5/77577462-db2a-41c1-8630-26b611eaf1d7/setup.exe is the download URL. Note that this is different from the previous SDK download URL, and also may not be available from search in MSDN. Please click this URL to get to it for sure.
There's fine print to the update behavior using this SDK, which you may need elaboration on.
The new Microsoft.Ink.dll is being updated based on an in-place strategy (increment the file version, but keep the assembly version the same so that applications do not need to be recompiled). If an existing Microsoft.Ink.dll version 1.7.x.x is on the desktop PC, the new Microsoft.Ink.dll will not install unless CLR2.0 is on the system (to be more specific, unless CLR1.1 and above is on the system - this is because CLR added in-place update support at CLR1.1).
If an existing Microsoft.Ink.dll version 1.7.x.x is not on the desktop PC, the new Microsoft.Ink.dll will install regardless of CLR version.
<What this means - you will need to have this FAQ ready if you are an ISV>
What this means is that for the case where CLR1.1 and above is not installed, and Microsoft.Ink.dll version 1.7.x.x is on the desktop PC, managed ink applications will work fine.
Then, an application setup that has the new Microsoft.Ink.dll in it is installed on top, but due to the existence of Microsoft.Ink.dll version 1.7.x.x it did not install the new Microsoft.Ink.dll (due to lack of CLR1.1 and above).
Then CLR2.0 got installed on the desktop PC by some means - your application may not function properly at this point.
The recovery method here will be to reinstall the application setup that had the new Microsoft.Ink.dll in it.
Koji Kato - Platform Lead Program Manager - Tablet PC
