|
There can be a number of situations where you may experience some difficulty in compiling or running an application. There are numerous causes for this and we describe some of these situations below.
A. Do you have the .NET framework installed? Our .NET components will not install if you do not have the .NET framework already installed. However, the ActiveX components can be installed without the .NET framework being present, but naturally, the .NET sample applications will not run in this case.
B. If you experience any errors of this type: C:\Program Files\Windale Technologies\NET\TransformNET\Demo Applications\NET1.1\VS2003\VB\TransformDemo\licenses.licx Could not transform licenses file 'licenses.licx' into a binary resource. Version 2.0 is not a compatible version.
C:\Program Files\Windale Technologies\NET\TransformNET\Demo Applications\NET1.1\VS2003\VB\TransformDemo\Form1.vb(293): Type 'Windale.Transform.DoneEventArgs' is not defined.
C:\Program Files\Windale Technologies\NET\TransformNET\Demo Applications\NET1.1\VS2003\VB\TransformDemo\Form1.vb(80): Type 'Windale.Transform.TransformNET' is not defined.
C:\Program Files\Windale Technologies\NET\TransformNET\Demo Applications\NET1.1\VS2003\VB\TransformDemo\Form1.vb(88): Type 'Windale.Transform.TransformNET' is not defined.
when opening or trying to compile our sample
applications, please follow the steps below:
-
In the first instance, close the project and remove the licenses.licx file.
- Reopen the project and expand the References in the Solutions Explorer.
- You should see a yellow warning notice regarding the missing licenses.licx file.
Delete this reference.
- Recompile the application. It should now function normally.
If further problems persist, it may be necessary to delete the references to the
object, eg TransformNET in the project and the References tab. Close the project and
remove the initial reference to instantiate the object in the Form1.cs or Form1.vb file etc.
Then reopen the project and drag the component on to the main Form,
eg Form1 and then recompile. This last stage is not usually required, but it may be
necessary in some cases.
C. For ActiveX components, if you receive some error messages indicating missing files, or the sample application does not start, it means you are probably missing some Microsoft support files. Some of our sample applications require MSFlexGrid and MSChart controls. These are distributed with Visual Studio Enterprise 6 and Visual Studio Professional 6 editions. Since many users have these files already, we do not distribute them by default. If you do not have Visual Studio, then the sample applications may not operate.
D. In some cases, there can be problems if you have installed a component multiple times and not uninstalled it after each installation and before the next installation. To overcome this problem, before installing a new version of any of our components, we recommend that you:
- Quit all relevant applications that can cause a DLL to not be removed. This includes Visual Studio, Excel, MS Access and Delphi.
- Uninstall the old version of the product.
- Install the new version.
E. If you have problems with running an application from a project you have created, there can be issues relating to the use of different versions of a component. This can result in, for example, a 429 error or other problems in the case of ActiveX controls. The simplest way to overcome this type of problem is to:
- Make a note of the name and properties used for the problem ActiveX control.
- Remove the ActiveX control from the form
- Close down Visual Studio or whichever IDE you are using.
- Restart Visual Studio
- Locate the correct ActiveX control reference and ensure it is in the Toolbox.
- With the relevant form open, double click the ActiveX control to place a new instance of it on the form.
- Change the name and set any properties to what is was previously. Try compiling and running the application again.
F. Are you sure the sample application is not working? If it displays a dialog box, then it is probably working. Note that in some cases, the source code is the place to examine how a particular component works. The demo application simply sits there and doesn't do anything fancy. But if you open the project in an IDE and set a breakpoint after the specific component method call, then examine the data, you will see how it has processed the data. Please bear in mind, some demos are only very simple, designed to show how to implement the a particular component method, so they may not appear to do much when in fact they are intended to be this way.
G. If you install a runtime ActiveX DLL and register it in the registry, this will stop the design-time ActiveX DLL from working. Hence you will not be able to open up and use a design project until you register the design-time ActiveX DLL. The simplest solution to this is to reinstall the software. We do recommend that you do not deploy your target solutions on your development machine or else this problem will occur.
H. In rare instances, there may be an out of date license, due for example to an old trial being installed on your machine. Please contact us with the full error message received in this case.
If you experience any other problems, please do contact us.
|
Home
Print this page
Email this page
Post a comment