|
| | |||||||
| Tablet PC Developers Show off your work while discussing with others how to create ink enabled applications. |
| | LinkBack | Thread Tools |
| |||
| Assembly Microsoft.Ink: Strong name validation failed. Hi, since today (today, I noticed it) I get FileLoadException from assembly Microsoft.Ink, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35. Errormessage: Strong name validation failed. HRESULT: 0x8013141A In the last time I have updated VS2005 to SP1 and installed VS2008 90 day trail. Maybe anyone can help me? Regards, Stefan |
| |||
| RE: Assembly Microsoft.Ink: Strong name validation failed. Hi Stefan, Could you please provide more details on: 1. Hardware you are running on - Tablet vs. Desktop, 2. OS - VISTA RTM or SP1 3. If it is a Tablet, can you still ink in other applications like Journal? 4. Is this happenning with both VS2005 SP1 and VS2008? 5. Did you rebuild all the dependencies? 6. Do you direcly reference Microsoft.Ink.dll in your project? 7. Do any of the managed Tablet SDK using Microsoft.Ink samples work? 8. Did VS2008 90 day trial version expire by any chance? You can temporarily disable strong name verification for Microsoft.Ink by running as a local admin from the command prompt: For a 32-bit computers: "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" For a 64-bit computers, run: "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" This is not a long term solution or in any way acceptable solution, just to unblock your development for now. Thank you. Lidia "Stefan Wilhelm" wrote: > Hi, > since today (today, I noticed it) I get FileLoadException from assembly > Microsoft.Ink, Version=6.0.0.0, Culture=neutral, > PublicKeyToken=31bf3856ad364e35. > Errormessage: Strong name validation failed. HRESULT: 0x8013141A > > In the last time I have updated VS2005 to SP1 and installed VS2008 90 day > trail. > > Maybe anyone can help me? > > Regards, Stefan |
| |||
| RE: Assembly Microsoft.Ink: Strong name validation failed. Hi Lidia, 1. Desktop 2. XP SP2 3. No Tablet 4. Yes, tested my own app + InkAnalysisScannedPaperForm sample 5. Yes 6. I am using "Add reference..." -> .Net Tab -> Microsoft Tablet PC API 6a. I my componentlist are 3x Microsoft Tablet PC API. Version A: V 1.7.260, Runtime 1.0.3705, c:\Program Files\Reference Assemblies\Microsoft\Tablet PC\v1.7\Microsoft.ink.dll Version B: V 6.0.0.0, Runtime 2.0.50727, c:\Program Files\Reference Assemblies\Microsoft\Tablet PC\v6.0\Microsoft.ink.dll Version C: V 1.7.260, Runtime 1.0.3705, c:\Program Files\Microsoft Tablet PC Platform SDK\Include\Microsoft.ink.dll 6b. I'm using Version B 7. Tested at the moment "InkAnalysisScannedPaperForm" - same Exception - this worked for me in the past. Same exception in VS2008 with this sample. 8. VS2008 is not expired, it is working fine since 1 week. Using Microsoft Tablet PC API Version A (1.0.3705) solves the problem - but I think, this is for .Net 1.0, isn't it? Are there any changes between this versions (A<->B)? Thank you for support! -Stefan "Lidia Schwarz" wrote: > Hi Stefan, > > Could you please provide more details on: > 1. Hardware you are running on - Tablet vs. Desktop, > 2. OS - VISTA RTM or SP1 > 3. If it is a Tablet, can you still ink in other applications like Journal? > 4. Is this happenning with both VS2005 SP1 and VS2008? > 5. Did you rebuild all the dependencies? > 6. Do you direcly reference Microsoft.Ink.dll in your project? > 7. Do any of the managed Tablet SDK using Microsoft.Ink samples work? > 8. Did VS2008 90 day trial version expire by any chance? > > You can temporarily disable strong name verification for Microsoft.Ink by > running as a local admin from the command prompt: > For a 32-bit computers: > "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr > "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" > For a 64-bit computers, run: > "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr > "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" > > This is not a long term solution or in any way acceptable solution, just to > unblock your development for now. > > Thank you. Lidia > > "Stefan Wilhelm" wrote: > > > Hi, > > since today (today, I noticed it) I get FileLoadException from assembly > > Microsoft.Ink, Version=6.0.0.0, Culture=neutral, > > PublicKeyToken=31bf3856ad364e35. > > Errormessage: Strong name validation failed. HRESULT: 0x8013141A > > > > In the last time I have updated VS2005 to SP1 and installed VS2008 90 day > > trail. > > > > Maybe anyone can help me? > > > > Regards, Stefan |
| |||
| RE: Assembly Microsoft.Ink: Strong name validation failed. Hi Linda, done one more test - copying Microsoft.ink.dll from other desktop pc and referenced to this file solved the problem. This means, the signed dll must be overwritten with VS2005 SP1 or VS2008 Trail (all german versions). Regards, Stefan "Lidia Schwarz" wrote: > Hi Stefan, > > Could you please provide more details on: > 1. Hardware you are running on - Tablet vs. Desktop, > 2. OS - VISTA RTM or SP1 > 3. If it is a Tablet, can you still ink in other applications like Journal? > 4. Is this happenning with both VS2005 SP1 and VS2008? > 5. Did you rebuild all the dependencies? > 6. Do you direcly reference Microsoft.Ink.dll in your project? > 7. Do any of the managed Tablet SDK using Microsoft.Ink samples work? > 8. Did VS2008 90 day trial version expire by any chance? > > You can temporarily disable strong name verification for Microsoft.Ink by > running as a local admin from the command prompt: > For a 32-bit computers: > "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr > "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" > For a 64-bit computers, run: > "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr > "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" > > This is not a long term solution or in any way acceptable solution, just to > unblock your development for now. > > Thank you. Lidia > > "Stefan Wilhelm" wrote: > > > Hi, > > since today (today, I noticed it) I get FileLoadException from assembly > > Microsoft.Ink, Version=6.0.0.0, Culture=neutral, > > PublicKeyToken=31bf3856ad364e35. > > Errormessage: Strong name validation failed. HRESULT: 0x8013141A > > > > In the last time I have updated VS2005 to SP1 and installed VS2008 90 day > > trail. > > > > Maybe anyone can help me? > > > > Regards, Stefan |
| |||
| RE: Assembly Microsoft.Ink: Strong name validation failed. Thank you, Stefan, for all your answers and further investigation. I think you are right about the DLL being overwritten with another installation. I am glad it is working now. I just wanted to mention that Microsoft.Ink.dll 6.0 is a Windows VISTA version. Please take a look at this MSDN topic for details on what version to use when: http://msdn2.microsoft.com/en-us/lib...59(VS.85).aspx Applications developed with 1.7.260 should work on VISTA as well. Which version to use really depends on what platforms you are developing your Ink applications for. I hope that helps. Thank you. Lidia "Stefan Wilhelm" wrote: > Hi Linda, > done one more test - copying Microsoft.ink.dll from other desktop pc and > referenced to this file solved the problem. This means, the signed dll must > be overwritten with VS2005 SP1 or VS2008 Trail (all german versions). > > Regards, Stefan > > "Lidia Schwarz" wrote: > > > Hi Stefan, > > > > Could you please provide more details on: > > 1. Hardware you are running on - Tablet vs. Desktop, > > 2. OS - VISTA RTM or SP1 > > 3. If it is a Tablet, can you still ink in other applications like Journal? > > 4. Is this happenning with both VS2005 SP1 and VS2008? > > 5. Did you rebuild all the dependencies? > > 6. Do you direcly reference Microsoft.Ink.dll in your project? > > 7. Do any of the managed Tablet SDK using Microsoft.Ink samples work? > > 8. Did VS2008 90 day trial version expire by any chance? > > > > You can temporarily disable strong name verification for Microsoft.Ink by > > running as a local admin from the command prompt: > > For a 32-bit computers: > > "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr > > "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" > > For a 64-bit computers, run: > > "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr > > "%ProgramFiles%\Common Files\Microsoft Shared\Ink\Microsoft.Ink.dll" > > > > This is not a long term solution or in any way acceptable solution, just to > > unblock your development for now. > > > > Thank you. Lidia > > > > "Stefan Wilhelm" wrote: > > > > > Hi, > > > since today (today, I noticed it) I get FileLoadException from assembly > > > Microsoft.Ink, Version=6.0.0.0, Culture=neutral, > > > PublicKeyToken=31bf3856ad364e35. > > > Errormessage: Strong name validation failed. HRESULT: 0x8013141A > > > > > > In the last time I have updated VS2005 to SP1 and installed VS2008 90 day > > > trail. > > > > > > Maybe anyone can help me? > > > > > > Regards, Stefan |
| Bookmarks |
| Thread Tools | |
| |
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| New Vista user, failed validation, can't access control panel | Kevin | Windows Vista | 4 | 01-05-2008 09:48 PM |
| Office Genuine Advantage Validation failed - support doesn't work | sachin | Microsoft Office | 0 | 08-25-2007 04:50 AM |
| Failed validation on newly purchased software | Cadwan | Microsoft Office | 5 | 04-27-2007 07:45 PM |
| Microsoft has strong quarter | Loren | Tablet PC Bloggers | 0 | 04-27-2007 11:10 AM |
| RE: office xp failed validation | CurtB | Microsoft Office | 2 | 04-06-2007 05:31 PM |
| New To Technology Questions? | Do You Need Help with Your Computer or Device? | Do You Need Help with this site? |