|
|
Front Page News
-
|
|
18-Month Evaluation Period Ends: The VisualAPL beta and RC programs have ended as of 06/01/2007, so that the complimentary access to the VisualAPL product available over the last 18 months has come to a close. Opening a VisualAPL solution or project with...
|
-
|
|
When you install the VSTO 2005 one of the pre-requisites is Microsoft Office 2003 SP1.
There are several templates that allow you to create different kind of projects, from add-ins to document-level customizations.
If you are targeting...
|
-
|
|
NOTES:
(1) In this blog-representation of my script, text like <apl_char> is used because some APL characters are not properly represented by the fonts included in the blog software.
(2) Using VSTO2005...
|
-
|
|
If you need help making a decision of which Visual Studio is rigth for you, on this page you can compare the different versions of Visual Studio 2005: http://msdn2.microsoft.com/en-us/vstudio/aa700921.aspx
Basically, when you get the VSTO 2005 you get...
|
-
|
|
Original broadcast date: March 14th, 2007
Controlling Excel using VSTO
With the Visual Studio Tools for Office Visual Studio Add-in, you can control all aspects of any and all applications in the Microsoft Office Suite of products.
This Screencast...
|
-
|
|
Original broadcast date: Feb 28th, 2007
Technologies presented in this screencast:
The general use, creation, and management of the CieloSession project.
Choose which loaded CieloSesison project in your Solution to use as the active...
|
-
|
|
Original broadcast date: Feb 28th, 2007
How to create and use script files in the active CieloSession project from the Cielo Explorer in Visual Studio.
How to use the CieloSession project: Create, Modify
This screencast is a subset...
|
-
|
|
Original broadcast date: Feb 28th, 2007
Technologies presented in this screencast:
The session in Visual APL is tightly integrated with Visual Studio, making the process of prototyping and testing code only a keystroke away with the Cielo Explorer. ...
|
-
|
|
Examples presented in this screencast:
Most .Net languages only allow the importing of .Net assemblies at build time. This means that you can only use the classes, methods, properties, events, etc, of assemblies which exist, on your computer,...
|
-
|
|
Examples presented in this screencast:
The using statment has an entirely seperate functionallity from the using directive, but has a somewhat similar syntax. Here is an example showing the difference between the using directive and using...
|
-
|
|
Examples presented in this screencast:
Most .Net languages only allow the importing of .Net assemblies at build time. This means that you can only use the classes, methods, properties, events, etc, of assemblies which exist, on your computer,...
|
-
|
|
Examples presented in this screencast:
How to remap the "Alt+" keyboard shortcut key sequence for any APL character. Via the Visual Studio Options form, you can change the keyboard shortcut for any Visual Studio command....
|
-
|
|
Examples presented in this screencast:
This screencast shows an example of using the Visual Studio Forms Designer to create a simple form, and assign event handlers to events on the form via the designer interface.
This screencast is a subset of Screencast:...
|
-
|
|
Examples presented in this screencast:
Using []WI in a Visual APL class. This segment shows the active debugging of the class as it is creating objects and handling events, and also how to use the more advanced...
|
-
|
|
Examples presented in this screencast:
Using []WI in the Visual APL session to create a simple Form, several controls, and set events through []WI. Also shown is how to access the .Net objects created with []WI and set properties and events directly...
|
-
|
|
Examples presented in this screencast:
Using []WI in the Visual APL session to create a simple Form, several controls, and set events through []WI. Also shown is how to access the .Net objects created with []WI and set properties and events directly...
|
-
|
|
Examples presented in this screencast:
Native .Net replacements for common legacy APL utilities. These include date processing (using System.DateTime), and accessing file system information (Last access time, directory path manipulation,...
|
-
|
|
Examples presented in this screencast:
Dynamic creation and execution of APL code in Visual APL.
This screencast is a subset of Screencast: Using System.
WatchFormat: wmvDuration: 43:39
To view this webcast directly in Windows Media Player,...
|
-
|
|
Examples presented in this screencast:
The start to finish creation of a simple Visual APL console application which can send SMTP email messages, done using the System.Net.Mail namespace.
WatchFormat: wmvDuration: 23:46
To view this webcast directly...
|
-
|
|
Examples presented in this screencast:
Dynamic creation and execution of APL code in Visual APL.
Native .Net Replacements for common legacy APL utilities. These include date processing (using System.DateTime), and accessing file...
|
-
|
|
The introduction for each weekly Visual APL WebCast is now available for viewing in the Multimedia blog section.
The Concluded WebCast Introductions blog can be found at this link:http://www.aplnext.com/community/blogs/intros/default.aspx...
|
-
|
|
Visual Studio Command System
In Visual Studio, all capturing of keyboard shortcut events is done through what is called the Visual Studio Commands interface, or just Commands for short.
When you press a shortcut key sequence, no function...
|
-
|
|
This documentation describes the supported feature set of the legacy []fmt system function.
[]fmt in Visual APL provides support for all of the .Net formatting modifiers across arrays.
[]fmt feature set:
[]fmt - legacy formatter which returns...
|
-
|
|
This documentation describes the currently supported legacy feature set of []WI.
Visual APL []wi plugin
Related quads:
Legacy:[]wself[]warg[]wres[]wevent
New:[]wsender - contains the object control, this can be used to access all of the members on...
|
-
|
|
This screencast shows the use of the Windows Control Library project template. This Visual Studio project type allows you to create a complete, self contained Windows control which can be used on any .Net form, from any .Net language. ...
|
|
|