When you install Spread for WinForms and you have used previous versions of the product, you might need to update Microsoft Visual Studio .NET and your existing projects. See the section "To upgrade your existing VS.NET projects" below for details

To update the Toolbox in Visual Studio .NET

For new projects, you might need to remove the existing Spread component from your Toolbox and add the new Spread component. To do so, follow these instructions:

1. Right-click on the Toolbox, and choose the Choose Items option.
2. In the Customize Toolbox dialog, choose the .NET Framework Components tab.
3. In the list of Components, clear the check box in front of FpSpread where the assembly name indicates the old version, and select the check box in front of FpSpread where the assembly name indicates the current version.
4. Click OK to close the dialog and place the updated FpSpread in your Toolbox.

To upgrade your existing VS.NET projects

For existing projects, make sure the reference path is correct, and add the new FpSpread assemblies. To do so, follow these instructions:

1. Open the project in VS.NET and close all the open forms.
2. In VS.NET in your project, open the Solution Explorer (Ctrl+Alt+L).
3. Right-click the Project and choose Properties.
4. From the Project's Property Pages, select Reference Path and modify the Reference Path so it points to the location where you installed the latest assemblies. Then click OK.
5. Click OK to close the Add Reference dialog and add these assemblies to your project.

Verify that the version number in the licenses.licx file is correct. For example:

Change:

FarPoint.Win.Spread.FpSpread, FarPoint.Win.Spread, Version=8.35.20143.0, Culture=neutral, PublicKeyToken=327c3516b1b18457

To:

FarPoint.Win.Spread.FpSpread, FarPoint.Win.Spread, Version=15.0.20211.0, Culture=neutral, PublicKeyToken=327c3516b1b18457

Spread for WinForms:

You may also want to replace any obsolete classes or interfaces along with the properties or methods that are no longer recommended to be used in this version. See the following page for a list of all such items: Obsolete API.

For users of Visual Studio .NET 2008 and Spread for WinForms who are upgrading projects

If you have made changes to a Spread control on a form at design time that required writing objects to the RESX file for the form or implemented binary serialization and you are using Microsoft Visual Studio .NET 2008, follow the procedure for Setting a Binding Redirect or copy the policy DLLs (located in C:\Program Files\Mescius\Spread Studio 10\Windows Forms\v10.x\Bin) to the global assembly cache (GAC).

Remember to make a backup of all your projects before upgrading. Once you have followed these instructions and upgraded the projects, and changed the Reference Path and loaded and saved the project, you will not be able to open the project in the old version. Once you have saved it in the new version, you cannot go back and open it in the old version. This restriction applies only to files that have a control on a form that had changes at design time that required writing objects to the RESX file.

For users of Visual Studio .NET 2005 and Spread for WinForms who are upgrading projects

If you have made changes to a Spread control on a form at design time that required writing objects to the RESX file for the form or implemented binary serialization and you are using Microsoft Visual Studio .NET 2005, follow the procedure for Setting a Binding Redirect or copy the policy DLLs (located in C:\Program Files\Mescius\Spread.NET 10\Windows Forms\v10.x\Bin) to the global assembly cache (GAC).

Remember to make a backup of all your projects before upgrading. Once you have followed these instructions and upgraded the projects, and changed the Reference Path and loaded and saved the project, you will not be able to open the project in the old version. Once you have saved it in the new version, you cannot go back and open it in the old version. This restriction applies only to files that have a control on a form that had changes at design time that required writing objects to the RESX file.

 

Return to the ReadMe.