Re: Issue 59 in cassia: Better exception message when trying to access a property of a session that no longer exists

[cas...@googlecode.com]

Updates:
Summary: Better exception message when trying to access a property of a
session that no longer exists
Status: Accepted
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low

Comment #2 on issue 59 by danports: Better exception message when trying to
access a property of a session that no longer exists
http://code.google.com/p/cassia/issues/detail?id=59

You'll most often see this exception when you're attempting to access a
property of a session that no longer exists. Given that you're running some
logic on session logoff (based on your stack trace), this result is not
uncommon. The solution would be for you to catch the Win32Exception that is
thrown and handle it appropriately.

It would be better if the library threw an exception with a more specific
error message though.

[cas...@googlecode.com]

Comment #3 on issue 59 by danports: Better exception message when trying to

access a property of a session that no longer exists
http://code.google.com/p/cassia/issues/detail?id=59

Issue 68 has been merged into this issue.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings