Do you have anything in your VS solution that automatically copies all dlls from your solution to your website? In that case an old referenced businesslogic.dll (v4.0.0) could be copied to your website and ovenwritten the 4.0.1.

Hi Niels,

Thanks for getting back to me so quickly. I'm still having this issue, so let me run the situation past you. I have a WebGarden.Utilities class library which is still in development, so it's getting compiled and recompiled as I develop my site. The website has a reference to it that I update through VS after each re-compile.

I also have a User Controls web application project for the site, which uses post-build events:

[code]
xcopy /Y /S /F "$(TargetPath)" "C:\Webroot\ProjectName\bin"

xcopy /Y /S /F "C:\Projects\ProjectName\UserControls*.ascx"
"C:\Webroot\Project_Name\usercontrols\"
[/code]

So it's copying across the compiled dll for the user controls, plus the .ascx files required.

So: what's the solution here? The up-to-date dlls are in the website /bin folder. And I copied the new dlls into my other projects and re-compiled everything. However, I'm still getting the Umbraco 4.0.0 upgrade wizard!

Am I missing something?

Thanks,

David

Ok that solved it - your suggestion was correct, Niels. I had created my own little dll hell!

I copied the latest versions of the dlls into the /bin folder of the website.

I updated the references for businesslogic, cms and umbraco in my utilities class library to point to these new files in the website /bin folder and recompiled the project.

I copied the latest versions of the dlls into the /bin folder of my usercontrols web application and recompiled that.

Now all three projects are using the same versions of the dlls as expected and the "upgrade" wizard is happy (web.config reads 4.0.1).

Been there, done that!

A tip for anyone using post build actions:

To avoid this issue, make sure your custom dlls etc start with a common prefix and be more specific with the xcopy command, something like this:

[code]
xcopy /Y /S /F "$(TargetPath)[prefix]." "C:\Webroot\Project_Name\bin"
[/code]

If your code references other custom dlls that do not start with this prefix you will have to add those as separate xcopy commands. Anything to avoid overwriting the core umbraco stuff!

Thanks daniell - thing is, when I run the post-build event:

[code]
xcopy /Y /S /F "$(TargetPath)" "C:\Webroot\ProjectName\bin"
[/code]

only one file gets copied, my UserControls.dll (as expected).

The problem in this case was my class library referencing the old versions of the dlls. Then my website referenced my class library. Every time I updated the reference (right-click on the reference in Visual Studio and choose 'update reference') that was when the problems started again (because the class library was referencing older dlls).

I suppose I'll need to have a different version of my class library for different Umbraco versions, where each version references the correct dlls.

Ahh, OK I see, it was not exactly the same problem we have experienced then. I missunderstood.

is working on a reply...