Sign In
Windows Forms Documentation Updates
We're the Windows Forms User Education team at Microsoft. We use this space to update folks on developments with Windows Forms docs, publishing doc updates before they're published. Feel free to ask us questions about WinForms, and we'll do our best to an
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
About
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
Application Settings
ClickOnce
Container Controls and Layout
Crossbow
Data Binding
DataGridView
ElementHost
Form and Application Classes
Pages
ToolStrip Control
WebBrowser, HTML, Networking
Windows Forms Globalization and Localization
WindowsFormsHost
WPF
XML, XSL & RSS
Archive
Archives
May 2008
(1)
January 2008
(1)
December 2007
(5)
September 2007
(1)
June 2007
(1)
May 2007
(4)
April 2007
(3)
February 2007
(1)
November 2006
(1)
October 2006
(2)
August 2006
(3)
July 2006
(5)
June 2006
(7)
May 2006
(4)
April 2006
(10)
March 2006
(10)
February 2006
(6)
January 2006
(5)
Conflict Between ClickOnce and Kensington Mouseworks Causes ClickOnce Applications to Crash
MSDN Blogs
>
Windows Forms Documentation Updates
>
Conflict Between ClickOnce and Kensington Mouseworks Causes ClickOnce Applications to Crash
Conflict Between ClickOnce and Kensington Mouseworks Causes ClickOnce Applications to Crash
Jay A. Allen
22 May 2006 4:25 PM
Comments
1
The ClickOnce development team has just alerted us that the current versions of Kensington Mouseworks software have a bad problem in one of their driver DLLs that crashes all ClickOnce applications. The bug occurs in a DLL that is loaded with every Windows process,and crashes that process if the executable path is longer than 128 characters. Since the ClickOnce store uses directory obfuscation when storing an application's files, this bug afflicts all ClickOnce app.
The only current workaround is to go into Add/Remove Programs and uninstall Kensington Mouseworks. The uninstall will require a reboot to retore the minimal drivers Windows needs for mouse input; after the reboot, any advanced functionality provided by the Kensington hardware will not work.
The issue has been reported to Kensington. We'll update you when they issue a fix.
1 Comments
ClickOnce
Blog - Comment List MSDN TechNet
Comments
Loading...