Developer forum

Hi Harald

Obviously you have package references that are not updated.

You have to ensure you updated Dynamicweb.Admin and all its dependencies.

In your visual studio solution open the package manager, how does it look like on the update tab?

In nuget You can run an update-package -reinstall on the admin package in the console and see if that will help. Alternatively uninstall the admin package and install it again.

Sorry about the inconvenience.

BR Nicolai

Hi Nicolai,

Thanks for you resonse.
I already installed all possible updates from the Dynamicweb Myget repository. In VisualStudio the package manager looks like this:

Just to be sure I ran a reinstall (Update-Package Dynamicweb.Admin -Reinstall) of the Admin. But the problem is still the same. I attached my packages.config.

Well - somewhere in you /Bin you have old dll's. Did you remember to do a clean and rebuild? Updating the package references will just update the package cache - you need to rebuild and maybe clean for the new dlls to get copied into your /bin folder.

From MyGet the admin package, you can see the required version - see dump.

Check the dll in your /bin if that is this version after the rebuild - if not, you need to figure out why - you have to check your output window in VS to see if it give pointers.

BR Nicolai

Hi Nicolai,

I cleaned the project and did a new build. Then I checked the bin folder for the version of the dll. This is the latest version, but still the problem persists.

Greetings Harald

I need to see your IIS setup - is /Admin a virtual directory?

Can you provide a dump of your website in IIS (the website expanded in the tree) and your folder structure

This is my current IIS setup, the admin is not a virtual directory. I tested changing it to a virtual directory but that made no difference.

It seems that your /Admin is not 9.5

So somehow your /admin is not updated

Hi Nicolai,

I did some further testing and to start I started a new VisualStudio Project and did a clean install of the Dynamicweb.Admin package. Then I compared the bin folder of the new installation with the bin folder of the upgraded solution. And there were a lot of differences:

I compared the Admin directory of the fresh nuget install with the Downloadable version on the website and there were 237 files missing in the nuget version of the Admin. So I copied those to my own project Admin

And I copy the bin folder of the clean install to my own project, now the error dissapears,

On a rebuild all the. xml files in the bin which were initially installed are removed. But that proves no problems as far as I can see.

The question which remains is, why is the upgrade via nuget failing, while copying the files of a clean nuget installation does work. And why are there so much differences between the downloadable version of the Dw core and the NuGet version.

Greetings Harald

Hi Harald

It is the same files in both. I looked a little closer - what happened here is that the Dynamicweb.Admin package has a dependency for Dynamicweb.UI.Controls 1.9 as I showed you in the first thread. If you look at the version you had in your bin, you have version 2.0.1 - which is a new major - which apperently is not compatible with 9.5.1 version of the admin package. So when you upgraded you admin package, you took newest versions of all dependencies, and that caused this to happen.

So that is the explanation - the UI.Controls should have been backwards compatible from our side - that is why you see the exception(s).

I will have the Dynamicweb.UI.Controls fixed again.

Sorry about the inconvenience.

BR Nicolai

Hi Nicolai,

I disagree that the Admin's (the downloadable version and the NuGet version) are the same. For examle the Dictionary files are missing from the nuget version and also several javascript files, for example:

And about the Dynamicweb.UI.Controls version. In an earlier stage I tried downgrading the Dynamicweb.UI.Controls to version 1.9.0 to test if that would solve the problem. But that was not the case at that time. So there might be more going on.

Greetings Harald

Hi Harald

It is the same dll version/build at least with the same references.

I will have the build team look into if they can conclude the same missing files and find out why.

BR Nicolai

Thanks - will take look at that. But basically this seems to be caused by the solution not being able to talk to our license service.

Hi Harald,

I've bugged it as TFS #55200 with a high priority.

BR

Martin