I downloaded the installer for 6.9.24

Should I uninstall my current version 6.9.23.1 first and then install 6.9.24 ?
or
Should I just start the 6.9.24 installer ?

Do I need to do move the data after installation ?

Simply install 6.9.24. Nothing else is required.

Note that 6.9.24 doesn't save the Streaming data provider choice so you have to change it manually after launch :(

Thanks. It worked. The authentication failure issue disappeared.

I installed 6.9.24.1 and recompiled my strategies dll.
I have two issues:
1- Setting Streaming Data to IQFeed doesn't stick. I have to re-do every time I start wl6.
2- I get this error:
Could not load file or assembly Microsoft.CodeAnalysis... (see attached image)

Would you please leave WB6 alone for now until we figure out whether to use wb7 or not. I have many blocking bugs in wb7 which makes it not useful to me for now.

System.IO.FileLoadException: Could not load file or assembly 'Microsoft.CodeAnalysis, Version=1.3.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Microsoft.CodeAnalysis, Version=1.3.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at WealthLabPro.Editor..ctor(ChartForm chartWindow)
at WealthLabPro.ChartForm.set_Strategy(Strategy value)
at WealthLabPro.MainForm.OpenStrategyWindow(Strategy s, Boolean executeOnSelectedSymbol, Boolean useAdvancedSettings)
at WealthLabPro.MainForm.OpenStrategyWindow(Strategy s, Boolean executeOnSelectedSymbol)
at WealthLabPro.MainForm.OpenStrategyWindow(Strategy s)
at WealthLabPro.MainForm.OpenStrategyExplorer()
at WealthLabPro.MainForm.b0(Object A_0, EventArgs A_1)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

QUOTE:
1- Setting Streaming Data to IQFeed doesn't stick. I have to re-do every time I start wl6.

That's highlighted in my post #2 above. We don't have access to the WL6 code and cannot fix the bug which was among the live bugs Fidelity introduced in 6.9.24 and/or won't fix.

QUOTE:
Could not load file or assembly Microsoft.CodeAnalysis... (see attached image)

If you recompile your strategy DLL, make sure to not overwrite any DLLs with the references you may have from the older version / in external folder. Since nobody else has complained this is the most likely cause.

At any rate, I recommend you do a full uninstall / reinstall. If recompilation breaks it you'll know your setup needs adjustment.

QUOTE:
I have many blocking bugs in wb7 which makes it not useful to me for now.

We'll probably get some of those you reported fixed (if not already) by Build 4 or by a future build.

What's the purpos of releasing 6.9.24?
Fixing particular issue?
Any breaking change?

QUOTE:
Note that 6.9.24 doesn't save the Streaming data provider choice so you have to change it manually after launch :(

QUOTE:
We don't have access to the WL6 code and cannot fix the bug which was among the live bugs Fidelity introduced in 6.9.24 and/or won't fix.

Is the Streaming data provider issue a new issue introduced in 6.9.24 by Fidelity?

I'm currently running 6.9.23.1 and it's working fine. Any problem for staying with 6.9.23.1 if I want to avoid the Streaming data provider issue?

Any workaround for the Streaming data provider issue? How about removing all Streaming data provider except IQFeed so that IQFeed is going to be the only Streaming data provider and streaming works with IQFeed data?

As I mentioned before, I have to stick with 6.9 for the time being until migrating to 7.0.

QUOTE:
I'm currently running 6.9.23.1 and it's working fine. Any problem for staying with 6.9.23.1 if I want to avoid the Streaming data provider issue?

Your (updated) 6.9.23 build supports authentication at our upgraded website so there's no need for you to upgrade to the later released 6.9.24 which is downloadable now.

QUOTE:
Is the Streaming data provider issue a new issue introduced in 6.9.24 by Fidelity?

Yes.

Hopefully Fidelity will fix the Streaming data provider issue before the next mandatory update.
In the mean time, I will stick with 6.9.23.1.

6.9.24 is the final build of WL6. Fidelity no longer invests any effort or funds into development of the product.

QUOTE:
Your (updated) 6.9.23 build supports authentication at our upgraded website so there's no need for you to upgrade to the later released 6.9.24 which is downloadable now.

There is a post on WL7 forum in which reporting an authentication issue with 6.9.23.1 and the suggestion is to update to 6.9.24.
I'm currently running with 6.9.23.1 and not having the authentication issue.

Why some people get the authentication issue with 6.9.23.1 and they have to update to 6.9.24 while the other people like me not getting the problem with 6.9.23.1?

I'm worrying if I will get the problem eventually and forced to update to 6.9.24 for only running into the Streaming data provider issue.

QUOTE:
I'm currently running with 6.9.23.1 and not having the authentication issue.
Why some people get the authentication issue with 6.9.23.1 and they have to update to 6.9.24 while the other people like me not getting the problem with 6.9.23.1?

There are two different 6.9.23.1 releases. The second 6.9.23.1 release came immediately after the website upgrade, which broke the authentication of the first release. Apparently, you (and I) updated then, and we are okay.

Then, later that day, there was a 6.9.24 release which supports .NET 4.8 (instead of 4.6.2), but .NET 4.8 broke some I/O things. So I consider 6.9.24 to be more broken than 6.9.23.1 unless you need the .NET 4.8 framework.

I wish they would have fixed the red squiggly-line problem with the WL6 editor, but my understanding is that this is still broken--unfortunately.

At any rate, there's isn't any financial incentive for them to continue work on WL6. And there are loads of feature requests for WL7. So if you were them, which one would you be focusing on improving?

QUOTE:
There are two different 6.9.23.1 releases.

They should have bumped the second version to 6.9.23.2.

QUOTE:
Then, later that day, there was an 6.9.24 release which supports .NET 4.8 (instead of 4.6.2), but .NET 4.8 broke some things. So I consider 6.9.24 to be more broken than 6.9.23.1 unless you need the .NET 4.8 framework.

If they have no plan releasing new update anymore, they should have not released such a major change in the final release.

QUOTE:
And there are loads of feature requests for WL7. So if you were them, which one would you be focusing on improving?

Definitely, WL7. My only wish was not to mess the working WL6.

QUOTE:
They should have bumped the second version to 6.9.23.2.

It was simply impossible for our company to do.

QUOTE:
I'm currently running 6.9.23.1 and it's working fine. Any problem for staying with 6.9.23.1 if I want to avoid the Streaming data provider issue?

"Strategy Download" ceased to function in versions prior to .24 due to website update. The final build .24 includes a patch for this.

QUOTE:
"Strategy Download" ceased to function in versions prior to .24 due to website update. The final build .24 includes a patch for this.

I have 6.9.24 1 and this doesn't work. Returns " ... failed with empty response"

Just double checked and "Download public strategies" still works for me in 6.9.24.

Not here

Try to uninstall completely and then remove the folder under Program Files, then reinstall.

Still the same.

If you hapen to fix the strategy download issue and release 6.9.25 or whatever new version, please consider fixing the Streaming data provider issue as well.

There will be no fixes to WLD 6.9 ever. Not only because WL6 is taken off market but also due to Fidelity not having transfered the WL6 source code to our company.

Fortunately, we were able to come up with a patch for the strategy download issue (which is fixed) because that did not require source code access.