Yes, but see the question above regarding ASP applications. Although it's possible to use WSpell, we recommend Wintertree Spelling Server for ASP.NET applications. For desktop VB.NET and C# applications, we recommend our Sentry Windows SDK product.

Yes. However, WSpell was designed for use in desktop applications, where concurrency (multiple applications or threads accessing WSpell at the same time) is low. Wintertree Spelling Server is a much better choice for ASP applications.

WSpell can spell check text strings, standard text boxes (TextBox and CEdit), standard rich-text boxes (RichTextBox and CRichEdit), and TX Text Control. The most common application involves checking the contents of a text box on a form. Usually, your application will set WSpell's TextControlHWnd property with the window-handle property of the text box (usually called the handle or hWnd property), then call WSpell's Start method. WSpell will check the words in the text box.

WSpell can check text entered in text areas on Web pages viewed with Internet Explorer running on a Windows platform. (Unfortunately, Netscape does not directly support ActiveX controls.) See Add a spelling checker to your Web applications for other web-based spelling checker solutions offered by Wintertree Software.

The answer for all of these examples is the same, you can use the classes and methods in System.Diagnostics.Process to accomplish these tasks and more. Example 1. Running a command line application, without concern for the results: Private Sub Button1_Click(ByVal sender As System.Object, _ Example 2. Retrieving the results and waiting until the process stops (running the process synchronously): Private Sub Button2_Click(ByVal sender As Object, _ Example 3.

Very fast! On a modest system, WSpell can spell check over 150,000 words per second! Click here to find out how we measured this.

This section is work in progress, but see the front page for info about CSBrowse. The control works fine from .NET apps, but the control is regarded as unmanaged code. If you're looking for a cross-platform solution, then some day, the GTK browser widget may be a better fit That is if the Mono crew consider doing their own thing instead of aping MS at every step, and produce a viable GTK# with a component for browsing.

The .NET Framework SDK is free and includes command-line compilers for C++, C#, and VB.NET and various other utilities to aid development. Microsoft Visual Studio Express editions are cut-down versions of Visual Studio, for hobbyist or novice developers.There are different versions for C#, VB, web development etc. Originally the plan was to charge $49, but MS has decided to offer them as free downloads instead, at least until November 2006.

Yes. COM components are accessed from the .NET runtime via a Runtime Callable Wrapper (RCW). This wrapper turns the COM interfaces exposed by the COM component into .NET-compatible interfaces. For oleautomation interfaces, the RCW can be generated automatically from a type library. For non-oleautomation interfaces, it may be necessary to develop a custom RCW which manually maps the types exposed by the COM interface to .NET-compatible types. Here's a simple example for those familiar with ATL.

Yes. .NET components are accessed from COM via a COM Callable Wrapper (CCW). This is similar to a RCW (see previous question), but works in the opposite direction. Again, if the wrapper cannot be automatically generated by the .NET development tools, or if the automatic behaviour is not desirable, a custom CCW can be developed. Also, for COM to 'see' the .NET component, the .NET component must be registered in the registry. Here's a simple example. Create a C# file called testcomserver.

I just can not belive Ghost has droped the ball on this and is still requiring people to use floppies. The directions are clear, straight-forward and accurate. This is the most well-put-together doumentation I've EVER found relating to Ghost. I've worked with (read: struggled with) the program on and off for years, and have never found any documentation anywhere near this caliber. This is the guide I was looking for since Symantec are so incopetent to write it for us.

You can port any type of .NET Web or server applications such as ASP.NET applications, ASP.NET Web services, remoting servers, tcp/ip servers, class libraries, and console applications. You cannot port desktop applications using Windows.Forms.

Yes, provided you have the the third party's .NET source code. Without the source code, you will need to find a Java EE-equivalent third party that provides similar functionality and then adapt your code to invoke the third-party Java component using the Mainsoft for Java EE Add Java Reference feature. The complexity of the port will depend on which Windows, .NET technologies, and third party applications your application uses, and whether Mainsoft supports these technologies on Java.

This is one of the QuickStart Samples that ships with Visual Studion .NET. Contributed from George Shepherd's Windows Forms FAQ

present we are finalising development of a fully automated .NET wrapping system but in the meantime, if you require this format file to be wrapped, please contact your Softwrap representative.

Yes. There are two different categories of PhysioToolkit code, and the rules for using them are slightly different. The WFDB library is free under the GNU Lesser General Public License (LGPL). The LGPL permits you to use (or sell, or give away) the library with your own code. The only significant restriction is that you must make the sources for the library itself freely available. You do not need to disclose the sources for your own code simply because you have used the WFDB library with it.

No, but we encourage you to use the form. It will help you submit a complete and accurate application.

Yes, of course! However, while Dapper is in beta, there is no gaurantee that the service will remain available at all times nor any promise that new features and changes to the software won't break your software. That said, we'll make every effort to prevent disruption.

The core spell check engine in WSpell has been around since 1992. It formed part of a commercial stand-alone spell checker product. We released our spell check engine as a separate product in 1993. WSpell, which contains our spell check engine, was released in late 1997. Since then, we have issued 15 releases to add new features and keep pace with changing technology.