This project is read-only.

DotRas v1.1

Rating:        Based on 3 ratings
Reviewed:  3 reviews
Downloads: 5110
Change Set: 42020
Released: Sep 1, 2009
Updated: Jan 28, 2012 by jeff_winn
Dev status: Stable Help Icon

Recommended Download

Application DotRas v1.1 SDK - September
application, 1494K, uploaded Sep 1, 2009 - 5110 downloads

Release Notes

This release includes compiled (and signed) versions of the binaries, PDBs, CHM help documentation, along with both C# and VB.NET examples, and the complete source code.

Supported Runtime: v2.0.50727
Build ID: 3530

Revision ID:
40234: WIN2K
40257: WINXP
40280: WINXPSP2
40303: WIN2K8

Reviews are not the proper location to ask questions, please use the discussions board instead.

Known Issues
  • There is a problem with the RasPhoneBook class when creating new phone books where the directory does not exist that's causing the component to throw an exception. To fix this problem, simply ensure the directory where the phone book will reside exists prior to opening the phone book. Issue #8818
  • There is a problem with the RasDialer when a connection is terminated by an external source throwing an unhandled exception. Issue #10094
  • There are a couple problems with RasPhoneBook and alternate entries used by dial-up connections. Issue #10356 Issue #10357
  • There is a problem adding broadband entries to a phone book. To fix this problem, set the PhoneNumber property on the RasEntry to a string with a space " ". Issue #10622
  • The CreateAndDialVpnEntry C# example has a problem when compiling. To fix this issue, remove line 3 from Program.cs in the project.
  • Added support for generating LUID structures.
  • Support for the RasGetCountryInfo API has been added.
  • RasDevice.GetDeviceByName no longer requires callers to disable exact matching, it is turned off by default.
  • RasDevice.Create has been publicly exposed so devices can be created manually.
  • RasEntryNameValidator has been added to assist with verifying entry names for a phonebook.
  • RasAutoDialManager has been completely redesigned to make the component easier to work with.
  • Stored credentials used by RasDialer are now forcably destroyed rather than waiting for the garbage collector.
  • Marked all objects that can be serialized with the Serializable attribute to allow for serialization.
  • Added the connection handle to the UserState property when dialing connections with RasDialer.
  • RasEntry and RasSubEntry now both implement the ICloneable interface.
Bug Fixes
  • Fixed a bug with the RasPhoneBook component not loading the Options property on RasEntry.
  • Fixed a bug with the RasDialer component DialAsync method causing timeouts when it shouldn't.
  • Fixed an issue with the RasDialer component not being reusable when dialing synchronously.
  • Fixed an issue with RasConnection.HangUp allowing the application to exit before the operation has completed.
Breaking Changes
  • The RasDialer component must have the PhoneBookPath property set to prevent a non-descriptive error when attempting to use stored credentials.
  • Renamed the PhoneBookPath property name on RasConnection to comply with project naming guidelines.
  • Added new example projects.
  • Created setup project for deployment rather than continuing to use multiple zip files.
  • Made many updates to the code documentation for the project.
  • Any entry points missing from rasapi32.dll will now throw NotSupportedExceptions, this is to prevent non-descriptive exceptions being thrown if a build from another platform is used on an earlier platform.

Reviews for this release

Used this excellent library for a .NET app that required RAS functionality. It's amazing, it's really stable, documentation and support from the developer are both second-to-none. Everything you could possibly want related to RAS functionality is included. There's no need to curse Micro$oft for not including RAS libraries in .NET, its all here. Highly recommended
by rwb2000 on Apr 16, 2010 at 5:04 PM
Wraps a huge amount of functionality related to RAS. I've been using this library since RC1 and haven't noticed any problems. Nice piece of code.
by yntelo on Nov 28, 2009 at 4:54 PM
I have used this release a couple of weeks now and I haven't found any major bugs so far. Good functionality and a nice implementation.
by thomas_agback on Nov 10, 2009 at 11:12 AM