Versions prior to 3.5 deleted from Nuget

[dgosbell]

Can the versions prior to 3.5 (specifically 3.3) please be restored back to the nuget feed?

I have some issue with Avalon Dock in 3.5 that I'm still trying to figure out (none of my anchorable windows are showing their views, just the name of their ViewModel) But now I can't build anything as when I tried to rollback my changes to use v3.3 of WPFToolkit it can no longer be dowloaded from nuget and it's not available on the GitHub releases either.

Please help as I'm trying to do some bug fixes on the current release for my project, but I can no longer build these due to version 3.3 being missing in nuget.

[Dirkster99]

Hi,

the nugets are not deleted but only removed from listing. For debugging, you can still go back in time to version 3.3 or 3.4 by compiling the libraries from source instead of using NuGet.

For AvalonDock 3.5, please check my branch as it seems to have solved most critical problems 3.5.

[dgosbell]

Yes, sorry it appears to have been some intermittent issue. I've tried again and nuget does return the 3.3 release even though it's not listed. And I've also figured out my issue with 3.5. It appears that the following line was changed

wpftoolkit/ExtendedWPFToolkitSolution/Src/Xceed.Wpf.AvalonDock/Themes/generic.xaml

Line 959 in aa93c69

Content="{Binding LayoutItem.View.Content, RelativeSource={RelativeSource TemplatedParent}}" />

Which used to look like this (without the .Content on the Binding path)

Content="{Binding LayoutItem.View, RelativeSource={RelativeSource TemplatedParent}}" />

I'm using Caliburn.Micro as an MVVM framework and I've worked around this issue by adding the old theme back via a style in my project.

[Dirkster99]

Yes, I remember that one. Please be aware that you will run into more such problems as you use the open source version of AvalonDock 3.5. The list of issues we've found and fixed so far can be seen here

• Your issue was fixed at version 3.5.2 see 'Fixed Issue about PanesTemplateSelector being ignored'

I would strongly suggest to use the nuget from my branch unless you want to run into each of the problems listed and fix them on your own in your private branch...

[dgosbell]

Thanks @Dirkster99 I've switched my project over to use your branch which has let me delete that extra style that I don't really need. I really only need AvalonDock so this will also trim down my dependencies a bit.

PS. Thanks for publishing your articles on how you implemented AvalonDock in EDI it was really helpful to me in getting it to work with my project DAX Studio I'm just browsing through some of your other projects as I would like to implement a dark them option and it looks like some of your stuff might be useful there.

[Dirkster99]

Thats great to know - your DB app looks really cool :-) just spread the word and be sure to assign a ⭐️ where it helps you so others find these projects more easily...

[Dirkster99]

This project should be the most useful starting point if you look at theming (because you will find out that Dark themes will also make Light Highlighting definitions look aweful):
https://github.com/Dirkster99/AvalonEditHighlightingThemes

Therefore, I've extended the normal HighlightingManager in AvaloneEdit, implemented a ThemeableHighlightingManager and connected it with ThemesManager I am using for WPF. Now, all all aspected of colorization can be setup to work consistently.