Hi,

I would be interested to hear how others update existing applications with newer versions of the Planner.NET.

My exisiting application has gone belly up with errors referencing the older version even though I have updated the references.

I am getting errors including designer license issues?

I have created a new app and copied that lic file over to no avail.

I am at the stage where I am looking at numerous errors in the form.vb[design] module which I shouldn't have to??

I have logged the team but thought I would ask here too.

Thanks

Hi

I'm having a problem after upgrading to version 4.3 also...

I followed the steps posted by Meppy but am getting the following error when I try to run my project:

An error occurred creating the form. See Exception.InnerException for details.  The error is: Could not load file or assembly 'Calendar, Version=4.2.1.19730, Culture=neutral, PublicKeyToken=9bbcdceda2685d38' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040).

I looked at licenses.licx and it contains this line of text:

MindFusion.Scheduling.WinForms.Calendar, Calendar, Version=4.2.1.19730, Culture=neutral, PublicKeyToken=null

So somehow my project is trying to reference the old version, which is no longer installed...

The references I have include:

Calendar (4.3.0.24470)
Common (1.0.2826.18027)
StandardForms (4.3.0.24471)

I'm not really sure how to proceed from here and I don't really have any experience troubleshooting such issues, so any help would be greatly appreciated as always

Thanks,

Brian

No...The Specific Version property is set to false for all of the dll's...

Because of strong-naming, you must rebuild your project with the new version of dlls. Just copying the dlls in the run folder and starting the .exe will not work.

If you have rebuilt the project, check whether the "Copy local" property of the references is set to true. If it isn't, the executable will excpect the new version of the dll, but it will find the old ones in the run folder.

Stoyan

To make this clear, which suggestion from that article has helped - removing the licx file from source control, or deleting it and adding the control again?

Stoyan

Sorry have been tied up with other things and just got back to this.

Well this was a very painful upgrade to say the least!

I uninstalled the 4.2 version and installed the 4.3.

When opening the project in the VS.NET IDE I got loads of errors as in my original opening post.

As with dimmer the project was still referring to the 4.2 even though I had removed all the references and replaced with the new.

I resolved the problem when finally the project displayed my form, less the calendar controls as they were not refreshed during the referencing process.

I then had to manually add the new calendar control to my form, open a backup copy of the project and manually enter all the properties etc so that I did not have to redesign it all from scratch.

So now I have my project working using the new 4.3 control.

Now I think this is a cool control but the upgrade is less than great.

The licx file was involved as with dimmer.

I am happy I have it all working again, however it was a painful experience which I hope wont happen with future updates.

On a lighter note this does not distract me from the fact that this is a truely excellent control and fits our needs perfectly!

On another note I get this very very annoying thing happening when adding the dll files to new projects.

I choose the source file of where the dll files are.

I then choose the dll files and they appear in the list.

If I try to do anything with the planner control etc I get errors like Appointment not defined.

So I go to references and see that I need to tick the entries for Mindfusion in the list at the bottom of the display.

I start to do this and get an error saying it is already defined in the project and VS.NET crashes.

I reopen and go to references and click all the Mindfusion entries and all works fine.

This ONLY happens when I first reference the planner.net controls in a new project.

Any ideas, is this a bug?

Not sure which problem your advice refers to but yes I did what you said whislt trying to resolve the licx issue and the new calendar worked ok etc but did not help with the exixting app using a previous version of the calendar.