GrapeCity Forums

Hello

I went through the upgrading process as documented in the 5.0 ReadMe file and things seemed to run pretty much as expected.I have a project with around 25 Spread 4.0 controls, each with lots of customization. I tried to add a 5.0 control to test how that went. Even though I made sure that I used the 5.0 Toolbox control, the system keeps creating a 4.0 control.

I have the following questions:

1 - Is this a bug or a feature/restriction?

2 - Can a VB project have both 4.0 and 5.0 controls running in parallel in the same project but on different forms? if so how.

2 - If not, is there some conversion utility to upgrade controls from 4.0 to 5.0?

Thanks for your help.

Ray

 

Hi Ray,

Have you updated the references in the project to use the new v5 assemblies?  A quick way to do this is to set a reference path in the project which refers to the bin folder containing the installed v5 assemblies (reference paths are set in the project properties under References).  If you prefer not to use reference paths, then you can delete the v4 references from the project in the Solution Explorer (click "Show All Files" at the top if you do not see the node for References there) and add the v5 references (right-click the References node and choose Add Reference, then go to the Browse tab and navigate to the bin folder where the v5 assemblies are installed and select them).

It is not possible to use both v4 and v5 assemblies in the same project, as the namespaces would collide and result in ambiguous references.

An upgrade utility should not be needed; just changing the references should be sufficient, and all your v4 code should work in v5.  There are a few deprecated APIs which might cause a warning if you are using them in your code, but they are still supported in v5, and it should be 100% backwards compatible with your v4 code and files.

---

seanl
Product Manager, FarPoint Spread for Windows Forms (.NET), FarPoint Spread COM
GrapeCity FarPoint

Thanks a lot Sean.

In a test project where I had only one Spread 4.0 control, I removed all FarPoint references and added all references from FarPoint 5.0. I now get an "Invalid FarPoint License" messageBox with the message "Unable to find an appropriate license fot this component. License has expired. The component, "FarPoint.Win.Spread.FpSpread" will not be created.". Why is that? The license is not expired. I ran it just before removing the reference and it ran fine. What's up?

 

Hi Ray,

I'm sorry, my last post was missing one other step that might be needed: updating the .licx file for the project.  You also need to change the type reference for the Spread control to reference the 5.0 version you are using:

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

---

seanl
Product Manager, FarPoint Spread for Windows Forms (.NET), FarPoint Spread COM
GrapeCity FarPoint

I hate to ask a dumb question but where do I put this string in my VB project?

Hi Ray,

It goes in the .licx file, which is usually in the Properties folder in the Solution Explorer window.  You should see the type reference for the v4 control there; that is what need to be updated to reference the v5 assembly.

---

seanl
Product Manager, FarPoint Spread for Windows Forms (.NET), FarPoint Spread COM
GrapeCity FarPoint

Thank you very much Sean. I really appreciate your quick help.

It's all good now.

Ray