General .NET Instruments
|
|
Question:
|
What programming languages are supported by GMSI.NET components?
|
|
Answer:
|
Any .NET compliant language is compatible with the GMSI.NET components (i.e. C#, Visual Basic .NET, Java .NET).
|
|
Question:
|
What versions of Visual Studio do you support? Will the components work in older versions of C++, or Visual Basic?
|
|
Answer:
|
The GMSI.NET components work with all versions of Visual Studio .NET, as early as version 1.0. They will, however, work only in a .NET compliant environment and, therefore, are not supported by older versions of C++, or Visual Basic.
Note: It is recommended that if you are using Visual Studio 2003, you should use the .Net Instruments v1.1. If you are using Visual Studio 2005, you should use the .NET Instruments v2.0. If you would like a copy of our v1.1 components, please contact our support staff.
|
|
Question:
|
What are the advantages of .NET components?
|
|
Answer:
|
GMSI.NET components were created for the Microsoft Visual Studio .NET development environment. .NET is an exciting six-year jump from ActiveX technology. The main advantage of developing in the Visual Studio .NET environment is the flexibility of the three modern programming languages it supports. Applications created in one language can be programmed against and debugged in any of the other languages supported by Visual Studio .NET.
|
.NET Distribution Ideas
|
|
Question:
|
What are the distribution fees associated with .NET?
|
|
Answer:
|
Unless otherwise noted, Global Majic Software charges per development seat. This means that you can distribute almost any application royalty free. Exceptions to this rule are:
- You are creating a container*.
- You are using aggregating or deriving GMSI.NET component(s) and are distributing the aggregated/derived component(s).
Note*: A container is a design environment (like Visual Studio) which allows developers or end users to drop third-party .NET components into it. Direct questions or comments to our sales department.
|
|
Question:
|
Which .NET files can I distribute with my applications?
|
|
Answer:
|
Your applications will only need the GMSI.Instruments.Common.dll file and the .dll file(s) for the .NET component(s) your application uses (i.e. an application that uses the Angular Gauge component would need the GMSI.Instruments.Common.dll file and the GMSI.Instruments.AGauge.dll file).
When you create a Setup Project, put the GMSI.Instruments.Common.dll file and the components .dll file in the bin directory and the GMSI.Instruments.Common.dll file in the Global Assembly Cache (GAC).
|
|
Question:
|
Are there other support files .NET needs to run on the target machine?
|
|
Answer:
|
The only support files needed are the GMSI.Instruments.Common.dll file, the .dll file for the particular component(s) used in your application, and the .NET Framework. No other files are necessary. For more information on the .NET Framework, see the following link to Microsofts MSDN .NET Framework website: http://msdn.microsoft.com/netframework/.
|
Configuring GMSI.NET Components
|
|
Question:
|
How do I add a GMSI.NET component to the Visual Studio Toolbox?
|
|
Answer:
|
Right-click the Visual Studio Toolbox and select Choose Items.... Click the .NET Framework Components tab. Mark the checkbox(s) next to the name of the desired component(s).
|
|
Question:
|
How do I add a GMSI.NET component to a Windows form?
|
|
Answer:
|
Click the appropriate tab in the Toolbox to display the GMSI.NET components. There are two ways to can add a .NET component to your form. You can click a .NET component button then click on the form, or you can simply double-click the button.
|
|
Question:
|
How do I access the properties of the GMSI.NET components?
|
|
Answer:
|
You can access its properties using the Properties window of the Visual Studio .NET environment or, in the case of all Global Majic Software controls, through a set of custom property pages. These pages may be opened by right-clicking the control and selecting Advanced Configuration.
Note: All changes are in real time and can be seen by left-clicking the Advanced Configuration window and dragging it off of the control.
|
|
Question:
|
How do I add my derived control to a Windows form to test it?
|
|
Answer:
|
- Open a Visual Studio .Net Windows Application project. See Using GMSI.NET controls in Visual Studio .Net.
- In the Visual Studio Toolbox click the General tab. Right-click within the General list and select Choose Items...
- Within the Customize Toolbox window, select the .NET Framework Components tab.
- Click the Browse button, and browse your computers files for the derived control on which you have been working.
- Select your projects folder and click Open, then open the bin folder, then the Debug folder. From here, select your projects .dll file (YourProjectName.dll) and click Open, then OK in the Customize Toolbox window.
- This will add a new button to the General list for your derived control. You can add it to the Windows form by clicking the button then the form or simply double-clicking the button.
- Once youve added it to the Windows form, you will be able to test its functionality as well as change any properties you exposed when you created the control. (To learn how to expose properties, see the Derived Controls Properties Tutorials.) If you decide you no longer want your derived control in the Toolbox or need to replace it with an updated version, simply right-click the button and select Delete.
|
|
Question:
|
How do I resize the Odometer control?
|
|
Answer:
|
Unlike the other GMSI.NET components, the Odometer cannot be resized by dragging the bottom right corner of the control. To resize it, find the Appearance section in the Odometer property browser (if the property browser is not already open, right click on the control and select Properties). Change the Font size either by clicking the More button to the right of the current font type and size in the Font field or by clicking the Expander to the left of Font and changing value in the Size field.
|
General .NET Support
|
|
Question:
|
Is source code for the .NET components available for purchase?
|
|
Answer:
|
Yes, source code is available for purchase for the individual components or the library as a whole. Prices vary by component, ranging from $999 to $8,999. For more information contact our sales department.
|
|
Question:
|
Are upgrades available for ActiveX users?
|
|
Answer:
|
We ar no longer offering discounted upgrades from our ActiveX components to our .NET components.
|
|
Question:
|
Can I load my copy of GMSI.NET onto more than one machine?
|
|
Answer:
|
A single purchase only licenses one machine. However, if you require the software on several computers, contact our sales department for information on site licenses.
|
.NET Technical Support
|
|
Question:
|
How do I report a bug?
|
|
Answer:
|
Although we take great strides to ensure the highest-quality, bug-free, products, occasionally we do find bugs. Please report any bugs that you find to our support staff.
|
|
Question:
|
What kind of support is available for GMSI.NET components?
|
|
Answer:
|
Free technical support is available for 90 days after the delivery date of your GMSI.NET software. Contact our support staff with any questions, problems, or concerns.
|
Ecommerce Solutions by Mountain Media